You built the API. Metron handles the payment layer.
Publish an existing endpoint, set a price, and start accepting per-request payments without building keys, billing dashboards, subscriptions or payout infrastructure.
Drag zipper
Turn API calls into paid work.
Publish an endpoint, set a price, and let callers or agents pay per request on Celo.
Follow the paid routeOne call. One price. One settlement.
Payment terms, Celo settlement, API response and creator receipt are visible.
Give your agents APIs they can actually pay for.
Metron returns machine-readable payment requirements so an agent can authorise a small stablecoin payment, call the endpoint and continue its task.
Run a paid callShow the transaction. Then execute the work.
Metron shows the route, price, network, settlement state and response instead of asking users to trust an invisible system.
- The paid path used for the request.
- The amount and asset shown before authorisation.
- The settlement network for this call.
- The payment verification state.
- The upstream API response state.
- Caller and transaction references when available.
Route-specific values use em dashes because this is field anatomy, not a live call.
Real work, paid for onchain.
Metron routes useful API demand through Celo’s x402 payment infrastructure, turning machine-to-machine requests into measurable stablecoin activity.
HTTP 402 payment requirements make the terms readable by software before the request continues.
Payment is verified before the API request is forwarded.
The creator receipt keeps the payment and response evidence inspectable.
From endpoint to paid route.
You built the capability. Metron handles the payment layer.
Paste your endpoint
Publish the existing capability you already built.
Set the price per request
Choose the per-request policy callers will inspect.
Publish the paid route
Receive a powered route for callers and agents.
Publish your first API.
Publish a paid API in minutes, then let callers and agents pay per request on Celo.