Build what agents
will pay for.
AI agents need APIs — for data, compute, and services. They can't swipe a card or fill out a signup form. You build the API, set your price, and agents pay instantly in dollars. No billing code. No invoices. No API keys.
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. Real-time, no 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
One import.
One middleware.
Add @botwallet/merchant to your Express app, define your prices inline, and you're live. Every payment shows up on your developer dashboard in real time.
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 open-source SDK to accept agent payments and a dashboard to track every transaction. That's the entire product.
npm install @botwallet/merchant
One package turns 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.
See every sale in real time
Revenue charts, top buyers by wallet, route-level analytics. Change pricing from the UI — no redeployment. Your API keeps running, config updates instantly.
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.
Inspect it, fork it, self-host it
The SDK is MIT-licensed. Use it standalone or connect to the dashboard for analytics and remote config. No lock-in — if you outgrow us, take your code and go.
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.
Every call after that is instant — zero blockchain overhead
The agent caches the ticket. Subsequent requests validate locally against the ticket policy. No on-chain calls. Sub-millisecond.
Ticket runs out — agent buys another automatically
No manual renewal. The agent handles repurchasing on its own. You keep serving requests and collecting revenue.
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. No intermediary, no escrow. Settlement takes under a second.
What does the SDK actually do?
The @botwallet/merchant package is an Express middleware. It intercepts requests, returns a 402 Payment Required with your pricing, verifies payment on-chain, and issues a signed ticket so subsequent calls skip the blockchain entirely.
Do I need crypto or blockchain experience?
No. You add one npm package, configure your routes with prices, and deploy. The SDK handles all blockchain interactions. You never write Solana code, manage wallets, or think about gas fees.
Are agents actually paying for APIs today?
AI agents already spend on compute, data retrieval, and API calls — but most developers can't accept those payments because there's no infrastructure for it. Botwallet is that infrastructure. Early developers are positioning their APIs now, before the wave hits.
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?
Yes. From the developer dashboard you can update pricing without redeploying. Config updates propagate instantly to your running middleware.
What frameworks does the SDK support?
The SDK ships as Express middleware today. Support for Fastify, Hono, and other Node.js frameworks is on the roadmap. If your server can handle HTTP, we can make it work.
Build with us.
We're selecting 20 founding developers to shape the SDK and launch alongside us. Tell us about your API — no commitment, just a conversation.
We respond to every submission within 24 hours. Not the right fit yet? We'll keep you posted for public launch.