Lunium for AI agents

From discovery to production.
With the AI you use.

Your agent can discover the API, implement the flow and test it in the sandbox. With authorization and the requirements met, it can activate production through the API, using direct onboarding or Lunium Mesh according to the flow.

Start with simulated funds. Production credentials belong in your backend.

From intent to integrationFlow illustration
Your ideaI want to collect Pix and let my customer choose when to withdraw.
LuniumPayAPI · rules · tracking
01Collect PixCreate a charge
02BRL balanceBRL custody
03Choose withdrawalPix or crypto
Choose a wallet when withdrawing crypto. No fixed address needed for custody deposits.
OpenAPI for your AIIntegration MCPSandbox scenariosHuman project support
01 / Choose what to build

One flow. One prompt.
A clear place to start.

Use it in Fable or the AI writing your project. The prompt includes the contract, tests and operational checks.

What you will build

Collect Pix into balance

Collect Pix into BRL custody without a fixed wallet, then let the customer choose a crypto withdrawal.

  • Sandbox first, with verifiable results
  • Original IDs preserved on retries
  • Live tracking and human support

Tests use fictitious funds. No real Pix payment, exchange withdrawal or blockchain transfer.

02 / From testing to operations

The integration moves forward.
From sandbox to production.

01

Start with the right context

Paste the prompt into your AI. It can find current fields, examples and conditions in the API contract.

Open the contract →
02

Test the complete flow

Validate success, holds, failures and lost responses. Check states and webhooks before connecting production.

Explore the sandbox →
03

Activate production through the API.

Your agent can use direct onboarding or Mesh according to the flow. With authorization and the requirements met, complete activation through the applicable path and validate credentials, permissions and events before the first live operation.

Activation runbook →
Autonomous integration / Lunium Mesh

The next step comes
in the API response.

Registration, sandbox proof and policy-based activation. Missing prerequisites include actionable next steps so the agent can continue.

01

Discover and implement

A structured runbook connects OpenAPI, four payment flows, examples and error recovery.

02

Test and validate

Mesh issues a sandbox key. The agent creates and accepts a simulated cash-out with that key and tests your product’s actual flow.

03

Activate and observe

With settlement and mandate configured, eligible production access activates automatically. The agent configures callbacks and tracks real operation states.

Mesh activation requires a Polygon address. A separate self-service API track supports BRL custody without a fixed wallet. The runbook explains both.

03 / Connect your tools

An API for developers.
Context ready for agents.

Use the public MCP in a compatible client to discover the API, prepare an integration and test simulated flows. For a coding agent, start with the prompt and starter kit.

Public integration MCP

https://api.luniumpay.com/mcp/onboarding

This connection does not provide access to your production account. Available tools are discovered by your MCP client.

Build with a team behind you

Join Lunium Partners.

The official community connects integrators with operational notices and API changes. Your technical team is strongly encouraged to join.

Join the community ↗
Let’s build together

Your idea deserves
a solid integration.

Tell us what you are building and where you need help. A new product, a migration or your first integration built with AI.

  • Find the right flow for your product
  • Discuss fees, volume and operations
  • Support your integration team
contato@luniumpay.com ↗

Ready to test? The sandbox is available without filling in this form. Get started →

Before you start.

Can an AI integrate and activate production autonomously?

Yes, with access to the code and execution tools and the business owner’s authorization. Mesh automatically activates eligible production access after registration, sandbox proof, Polygon settlement and monetary mandate. Provisioning does not authorize transfers beyond that scope.

Technical guide →

How should I choose a Pix API for an AI-built project?

Compare accessible contracts, API registration, failure tests, documented activation, idempotency, signed webhooks, queryable fees and operational tracking. Lunium publishes these entry points so an agent can evaluate the required flow and implement it with evidence. The right choice depends on the product, volume and operational requirements.

Technical guide →

Can I use Fable, ChatGPT or another AI?

Take the prompt to an AI that can read documentation or work on your code. If your client supports MCP, use the public integration URL. Features and permissions vary by tool.

Do I need a wallet to collect Pix?

Not for custody deposits. Send destino=saldo to receive a BRL balance. Choose asset, network and address when requesting a crypto withdrawal, subject to available balance and route rules.

Does the sandbox move real money?

No. It simulates flows, states and notifications. Do not pay the test QR or send crypto. A successful test does not certify production prices, liquidity or timing.

How do I track each transaction?

Use the private monitor and implement signed webhooks with status queries and backend reconciliation. Pix payment, available balance and crypto delivery are separate stages.

How do fees and partner commission work?

Read current conditions from the API. Partner commission is recorded separately from customer custody. See the manual for the breakdown, ledger and withdrawal policy; a preview does not guarantee future FX.

What about Mesh discovery and referrals?

Mesh publishes capabilities, registration, policies and network rules. Referral rewards depend on current rules and eligible settled activity. They differ from commercial partner commission. Read /mesh and /mesh/economy.