Build what agents
will pay for.
Turn your data, compute, or service into something agents can buy. Join our developer program to build paid APIs with USDC and help shape the tools.
Use Cases
If your API saves an agent
time or tokens, it has value.
An agent can burn thousands of compute units solving a problem from scratch — or call your API for a fraction of the cost. If you've built something useful, agents will pay you instead of reinventing it.
Ideas for what you could build
Video Transcription
Agent sends a URL, gets a timestamped transcript. The payment is the authentication — no signup, no API key.
Voice Generation
Text in, natural speech out. Pay per batch — scales from a single sentence to a full audiobook.
Specialized Knowledge
Medical literature, legal codes, engineering specs — your curated dataset, monetized per query. Agents pay for knowledge you already have.
Live Data Feeds
Market prices, weather, sports, flights. Agent buys a time window and polls as fast as it needs. You define the access window and rate limits.
Model Inference
Fine-tuned models, custom embeddings, specialized classifiers. Sell compute by the token — agents pay for exactly what they consume.
Your API here
If agents need it, they'll pay for it.
Why Now
Agents are arriving.
Most APIs aren't ready.
Agents can't swipe a card
No credit cards. No billing addresses. No KYC forms. AI agents need payment rails built for machines — wallets, stablecoins, and programmatic pricing.
Built on HTTP 402
The web reserved a status code for "Payment Required" in 1997. We built a protocol on top of it — purpose-built for machine-to-machine payments. Your API already speaks HTTP.
First movers become defaults
As agents start discovering services programmatically, the APIs that accept agent payments first will be the ones agents return to. The window to be early is now.
Integration
A preview of
the integration.
The example below shows the intended Express integration. The SDK is in early access and not yet published, so package access, supported features, and the API may change.
import express from "express";
import { ticket } from "@botwallet/merchant";
const app = express();
app.use(ticket({
payTo: "7xYZabc...",
routes: {
"POST /transcribe": { price: "$0.10", calls: 1 },
"POST /query": { price: "$2.00", calls: 50 },
"GET /prices/*": { price: "$0.25", minutes: 60 },
"POST /inference": { price: "$5.00", units: 100000 },
}
}));Flexible pricing, built in.
Four pricing models — mix and match per route.
Agent prepays for a batch of requests. Predictable revenue for you, predictable cost for the agent. Best for queries, lookups, and bounded tasks.
Unlimited calls for a set duration. Agents pay once, then hit your API as hard as they want. Ideal for streams, polling, and session-based work.
Meter by tokens, bytes, or custom units. Your revenue scales linearly with consumption. Built for inference and compute-heavy endpoints.
One payment, permanent access. Revenue up front, zero ongoing management. Best for premium APIs and standalone tools.
The Stack
Two tools.
One SDK. One dashboard.
An SDK to accept agent payments and a dashboard to track every transaction. Both are in early access: the SDK is not published yet, and the dashboard is planned.
Private preview
One package will turn your Express app into a paid API. Agents discover your pricing, pay on-chain, and get access — no billing code, no webhook handlers, no payment tables in your database. It is not on npm yet; join early access for availability and setup instructions.
See every sale in real time
Planned: revenue charts, top buyers by wallet, and route-level analytics, with pricing changes from the UI and no redeployment.
USDC straight to your wallet
No intermediary holds your money. When an agent pays, USDC transfers directly to your Solana wallet. On-chain, verifiable, yours in under a second — not net-30.
Read how agents pay
The merchant SDK is not published yet. The Agent CLI, MCP server, and signing app that agents and owners use are open source under Apache-2.0, so you can read how payments reach your API.
The Flow
What happens when
an agent hits your API.
No API keys to provision. No billing dashboard to build. No invoices to chase. The agent pays, your middleware verifies, and you serve the request.
Agent calls your endpoint — no ticket
Middleware intercepts, returns 402 Payment Required with your pricing options. The agent sees what's available and what it costs.
Agent pays — USDC goes to your wallet
The agent selects a plan, signs a USDC transfer on Solana. No intermediary. Your middleware verifies the payment and issues a signed ticket.
Reuse paid access with a ticket
The proposed flow validates subsequent requests against the ticket policy while the ticket remains valid.
Renew access within the agent’s spending rules
When access expires, the agent can request another ticket. Any new payment must follow the rules set by its owner.
FAQ
Common questions.
How do I get paid?
When an agent calls your API, it pays in USDC — a dollar-backed stablecoin on Solana. Funds transfer directly to your wallet. Your wallet receives the payment once it settles on the network.
What is the developer program building?
We are developing middleware that presents your pricing, verifies payment, and grants access to your API. The integration preview below shows the intended developer experience. Join early access for current availability and setup instructions.
Do I need crypto or blockchain experience?
You should be comfortable building and deploying an HTTP API. The program is designed to help you add agent payments without building your own payment infrastructure.
Are agents actually paying for APIs today?
Botwallet agents can pay for supported APIs through x402. The developer program helps builders explore how to make their own services available to agents.
Is there a fee?
No fees are deducted from your payments. The 1% transaction fee is paid by the sender (the agent). You receive the full amount every time.
Can I change pricing after launch?
You choose the prices for your API. Pricing controls and deployment requirements will depend on the integration available through early access.
What frameworks does the SDK support?
The integration preview uses Express. Tell us which framework your API uses when you apply, so we can discuss the available integration options.
Build with us.
Help shape payments for the APIs agents will use. Tell us what you're building and which framework you use.
We'll review your submission and follow up by email with the next steps.