Skip to content
FluxRoute
Solana-native infrastructure

One connection.
Every service.

Route AI agents to paid microservices through a single MCP endpoint. Pay per call in SOL or USDC-SPL - no API-key sprawl, no billing fragmentation.

Start buildingRead docs

Implemented product surface

MCP gatewayx402 negotiationSOL and USDC-SPLProvider proxy
mcp_config.json
{
  "mcpServers": {
    "FluxRoute": {
      "command": "npx",
      "args": ["-y", "@fluxroute/mcp"],
      "env": {
        "FLUXROUTE_API_KEY": "fr_live_..."
      }
    }
  }
}
Minimal MCP config
AI AgentMCP clientFluxRouteImageTextDataCompute

0

Supported payment assets

0

Core API modules

0%

Provider platform fee

0

Minute payment window

The problem

AI agents need paid APIs.
The current way is broken.

Every service demands separate keys, billing, and docs. Your agents burn cycles on plumbing instead of solving problems.

Without FluxRoute
With FluxRoute

Separate API key, billing, and integration for each service

One MCP-facing route into registered services

Generic payment middleware not designed around Solana assets

Solana-native settlement in SOL or USDC-SPL

APIs scattered across docs with no unified registry

Registry API with pricing and discovery

Manual payment flows, credit cards, pre-funding

Per-call Solana payment verification

No spending controls - agents can overspend freely

Budget configuration API for account-level controls

How it works

Four steps. Zero config management.

  1. 01

    Connect

    Add FluxRoute to your agent's MCP config. One JSON entry - five lines.

  2. 02

    Call

    Your agent discovers and calls any registered service through one unified interface.

  3. 03

    Pay

    The x402 protocol settles payment automatically in SOL or USDC-SPL, on-chain in ~400ms.

  4. 04

    Receive

    Payment verified on-chain, request fulfilled, response returned. Your agent continues.

Core features

Infrastructure that gets out of your way

Solana payment rail

Negotiate SOL or USDC-SPL payment requirements and verify submitted transactions on-chain.

Validated API contracts

Shared Zod schemas validate registry, payment, endpoint, and budget configuration inputs.

Wallet-aware calls

Payment records bind each call to a transaction signature, recipient, amount, and memo.

Service registry API

Providers can register HTTP services with pricing, categories, endpoints, and wallet addresses.

Provider SDK

TypeScript helpers generate x402-style payment requirements for provider applications.

Ledger records

Successful executions write spend and earnings rows for downstream reporting.

Service registry

A registry for paid services. One endpoint.

Browse, discover, and call services across every category, each priced transparently and settled on Solana.

Text0Data0Finance0Search0Compute0Code0Image0Audio0

No public provider services are listed yet.

The production registry is connected to the live API. New provider services will appear here after authenticated providers publish real endpoints through the dashboard or API.

TextImageDataFinanceSearchComputeCodeAudioTextImageDataFinanceSearchComputeCodeAudio
Open dashboard
Developer experience

Built for developers who ship

TypeScript-first SDKs, comprehensive docs, and a CLI that makes publishing and consuming services trivial - whether you build agents or sell APIs.

  • TypeScript-first

    Fully typed SDKs with autocompletion for every service.

  • One-command CLI

    Scaffold, test, and publish services from your terminal.

  • Framework agnostic

    Drop into Express, Hono, Next.js, or any Node runtime.

import { FluxRouteMCP } from "@fluxroute/mcp";

const agent = new FluxRouteMCP({
  apiKey: process.env.FLUXROUTE_API_KEY,
  walletMode: "managed",
});

// Call any service - payment handled automatically
const result = await agent.call("openai-whisper", "/transcribe", {
  audio_url: "https://example.com/audio.mp3",
  language: "en",
});
Pricing

Pay only for what you use

No subscriptions. No minimum commitments. Per-call micropayments settled on Solana.

Consumer fee

0%

You pay the service price - nothing extra.

Platform fee

2%

Deducted from provider earnings only.

Network fee

Network

Standard Solana transaction costs paid by the caller.

Provider settlement

Providers receive payment to the wallet configured on each registered service.

Caller wallet

Callers submit their own Solana transaction and pass the signature back for verification.

Start routing in minutes

Connect an agent to the API, register provider services, and verify Solana payments per call.

Open dashboardRead documentation

Free to start. Pay only when your agents make calls.