New revenue channel
AI agents already pay for API services. Is yours callable?
An AI agent does not fill forms or create accounts. It calls an API, pays per call, moves on. The x402 protocol makes that payment possible, Google adopted it in its agent payment protocol (AP2), and the x402scan registry already lists hundreds of services. We make your product callable and payable by these agents, in 2 to 4 weeks.
The proof: we run it on our own products
No theory. Two of our SaaS products are agent-callable in production, with real USDC payments on Base.
ExpertsIA · growth teardown
Paid endpoint in production: agents pay $4.90 in USDC on Base (x402 protocol), full audit in 11 seconds.
ChargeGuard · chargeback-risk teardown
Same architecture on our second product: $9.90 per call, public openapi.json spec, reference MCP servers free to use.
Public specifications: trychargeguard.com/openapi.json and expertsia.dev/openapi.json
What this delivery includes, verifiable in one click
- ✓4 paid x402 endpoints in production (2 full teardowns, 2 entry snapshots) : 402 verifiable here
- ✓Two streamable HTTP MCP servers (4 reason-code and deadline tools on ChargeGuard)
- ✓A public npm CLI : npmjs.com/package/chargeguard
- ✓A public read-only API with no account required (reason codes, deadlines), 24h cache
- ✓Full security review: 50+ vulnerabilities closed, SSRF protection, constant-time key comparison, rate limiting
- ✓The pattern guide, open with no email gate : read the guide
ChargeGuard is our own product, not a client engagement: we show what we would apply to your product, with the same security and documentation standards.
Step 1: Agent-ready audit
€490 excl. VAT
Report delivered in 48 h
- ✓ Mapping of your existing API: what is already callable, what is missing
- ✓ Per-call payment model (x402, USDC on Base) and recommended price
- ✓ MCP server plan: which tools to expose, with which permissions
- ✓ WebMCP actions to declare on your critical forms (signup, checkout, booking)
- ✓ openapi.json to produce and registries to list on (x402scan, MCP registries)
- ✓ Report delivered in 48 h. Credited against the transformation if you proceed.
Step 2: Agent-callable transformation
from €2,000 excl. VAT
Delivery in 2 to 4 weeks depending on your infrastructure
- ✓ Paid x402 endpoint: USDC on Base payments, no account, no API key
- ✓ Streamable HTTP MCP server for Claude, ChatGPT and every MCP client
- ✓ Declarative WebMCP tags on your critical forms
- ✓ openapi.json with payment metadata, readable by registries
- ✓ Agent-facing documentation: llms.txt, developers page, call guide
- ✓ Registry submissions and tracking of your first paid calls
- ✓ Security review: SSRF guards, constant-time key comparison, rate limiting
Frequently asked questions
What is x402, concretely?
An open protocol backed by Coinbase and adopted by Google in its agent payment protocol (AP2). An agent calls your API, gets a 402 response with the price, pays in USDC on Base, and retries with proof of payment. No account, no card, no API key: the whole commercial relationship fits in three HTTP requests.
How long and how much before it is live?
The audit takes 48 h. Delivery takes 2 to 4 weeks depending on your infrastructure. Expect from €2,000 excl. VAT for a product with a clean API, more if the API has to be built or authentication reworked.
What about my human customers?
They see no change. The agent-callable endpoint adds to your existing product, it does not replace it. Our own sites keep their classic interfaces: the agent layer is an additional sales channel.
Why you rather than a generalist integrator?
Because we run it on our own products, in production, with real payments. Both endpoints above are ours. The pattern is proven: we reproduce it for you in 2 to 4 weeks, security included.
Let’s talk about your product
Send us the link to your API or your site. We answer within 24 h with our honest read: either the agent channel makes sense for you, or we tell you straight.
Request the €490 auditcyril@expertsia.dev · remote, worldwide