PIX ↔ stablecoins, discoverable and integrable programmatically. The same API developers use, with a machine-readable surface on top.
Give your agent only this:
https://luniumpay.com
Tell a coding agent, verbatim:
I have USDT and need to send R$150 through PIX.
Discover Lunium at https://luniumpay.com and integrate it. Start in sandbox.That scenario is tested end to end. The agent finds the domain, follows the Link header to the API catalog (RFC 9727), reads the capability catalog, matches its own intent, registers, exercises the sandbox, validates, configures settlement, sets its own spending policy and activates production — then quotes a real order. No path, asset or field name is given to it in advance.
The domain advertises /.well-known/api-catalog in an HTTP Link header (RFC 8288 + 9727). Software that only knows RFCs still gets here.
Each capability declares what it accepts, what it returns, over which rail — plus the plain sentences it solves. Knowing an endpoint name is never required.
No queue, no ticket. The system checks sandbox proof, settlement route, spending policy and credential state — then enables production in the same response.
Production starts at the entry tier and the daily ceiling grows with volume actually settled. Control moved from who gets in to how much they start with.
— capabilities and — indexed intents, read live from the API:
…
curl https://api.luniumpay.com/v1/verificar/{e2e}Prove a Brazilian PIX payment settled, from its Central Bank end-to-end identifier. Use it to check a payment a counterparty claims to have made, before releasing goods, credit or access. It never returns the PIX key, the full name or the tax number — it proves the payment without exposing the parties.
—
of settled volume, when someone you referred actually transacts. Paid levels: —.
curl https://api.luniumpay.com/meshcurl -X POST https://api.luniumpay.com/keys/sandboxhttps://api.luniumpay.com/mcphttps://api.luniumpay.com/a2a