Design access and payments around your MCP tools.
Separate caller identity, permission and payment requirements. Review the supported payment integration path and the broader products in Private Beta.
Where each Credia product fits.
- Live. Get started with Credia Payments.
Credia Payments
Payment workflows and controls for AI agents.
- Private Beta. Available to selected teams. Request access to discuss your integration.
Credia Auth
Define how an agent authenticates and what authority it can use.
- Private Beta. Available to selected teams. Request access to discuss your integration.
Credia Identity
Establish an agent's identity and its connection to an operator.
Use the payment recipes that exist today.
Paid tools return a 402 challenge until the call is paid; x402-aware clients pay and retry automatically. The MCP integration guide covers setup, pricing models and webhook handling.
Check the caller, not just the payment.
A payment says value moved; it does not say who is calling or what they may do. Credia Auth, in Private Beta, adds caller checks for tools that need them.
Treat receipts as records, not delivery proof.
Store the payment.received event with the tool call it unlocked. A receipt shows payment, not that the tool returned a useful result.
Decide your failure and retry boundaries.
Choose how long a paid window lasts, what happens when a client pays and disconnects, and how retries reuse an idempotency key so a call is never charged twice.
Paid MCP tools in practice
What operators ask before turning on paid tools.
Does my MCP server need to be hosted on AgentCredia?
No. Your MCP server runs wherever it normally would. The middleware wraps your tool handlers; it needs outbound HTTPS to api.agentcredia.com and a URL you control for inbound webhooks. AgentCredia hosts the payment surface, not your server.
What happens when a client does not understand x402?
The 402 challenge includes an error code, the amount and a hosted URL to pay at. Chat clients that surface tool errors show the user the link; clients that ignore the error simply get no result, which is correct because the call was not paid. x402-aware clients pay and retry automatically.
How long does a paid window last?
You decide, because you own the paid-state. A 60-second TTL is a common choice: it absorbs retries without letting one payment cover a whole session. Make it longer for subscription-style pricing, or zero for expensive per-call tools.
Can I run paid and free tools on the same server?
Yes. Add the paid-state check only to paid tools and leave free tools as plain handlers. Many operators keep cheap tools free to drive adoption and charge for inference, generation and long-context work.
How do I see which clients paid and how much?
Every payment appears in the dashboard with the payer address, time and amount, and arrives on your payment.received webhook. Log the tool called and every 402 you return in your handler, then join them for per-payer and per-tool revenue.
Discuss this workflow.
Tell us what you are building and we will confirm which products and integrations fit.