Install Jentic One Beta

Connect the Lunium — crypto ⇄ PIX settlement (Brazil) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lunium — crypto ⇄ PIX settlement (Brazil), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fluniumpay.com%2Fluniumpay" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fluniumpay.com%2Fluniumpay" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Lunium — crypto ⇄ PIX settlement (Brazil) API.

Generate a PIX charge with amount_cents and payer_tax_number that credits BRL custody (destino saldo) or delivers crypto (destino cripto) via POST /cashin/charge

Send a PIX payout from the available BRL balance to a pix_key through POST /payouts, up to R$ 6.000,00 per PIX

Quote, accept, and track an external crypto-to-PIX cash-out with POST /cash-outs, POST /cash-outs/{cashout_id}/accept, and GET /cash-outs/{cashout_id}

Withdraw BRL custody balance as crypto to a self-custodial payout_address via POST /saldo/sacar-cripto

GET STARTED

Start building with Lunium — crypto ⇄ PIX settlement (Brazil) API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Lunium — crypto ⇄ PIX settlement (Brazil) API for, with concrete tasks.

★ Payments agent through Jentic

A billing agent collects BRL from a Brazilian customer. It searches Jentic for 'generate a PIX charge', receives POST /cashin/charge with its amount_cents, payer_tax_number, and destino fields, and creates a charge that credits custody. Because a paid PIX does not mean credit is complete, it then checks GET /cashin/{cashin_id}/status and the balance statement before marking the invoice settled.

Call POST /cashin/charge with amount_cents 15000, payer_tax_number of the payer, destino saldo, and a stable external_id, then poll GET /cashin/{cashin_id}/status until settlement is reported

Crypto to PIX cash-out

Pay a Brazilian supplier in BRL from stablecoins. POST /cash-outs quotes an asset and network listed by GET /catalog against a pix_key or a full br_code, POST /cash-outs/{cashout_id}/accept returns the deposit address, and GET /cash-outs/{cashout_id} tracks the order until the PIX is delivered.

Call GET /catalog, then POST /cash-outs with asset USDT, a supported network, brl_amount '500.00', and the supplier's pix_key, accept it with POST /cash-outs/{cashout_id}/accept, and report the deposit address

Marketplace subaccount payouts

A platform holds funds for its own clients as subaccounts identified by customer_ref. GET /saldo/clientes pages through subaccount balances, POST /saldo/transferir moves funds between a subaccount and the house without PIX, and POST /payouts sends a PIX from a subaccount's available balance to the client's key.

Call GET /saldo with customer_ref 'seller-42', and if the balance covers it, POST /payouts with amount_cents 20000, the seller's pix_key, pix_key_type cpf, customer_ref 'seller-42', and a stable external_id

Sandbox integration testing

Exercise every money flow without moving money. POST /keys/sandbox returns a lun_test_ key from an email address, charges create non-payable QR codes that POST /sandbox/cashin/{cashin_id}/pay confirms, sandbox_scenario forces outcomes such as held, expired, or settlement_failed, and POST /sandbox/reset clears the fictitious state.

Call POST /keys/sandbox with the tester's email, create a charge with POST /cashin/charge using sandbox_scenario held, then confirm it with POST /sandbox/cashin/{cashin_id}/pay and inspect GET /sandbox/events

Key Endpoints

66 endpoints — the lunium api settles between crypto and pix in brazil: it generates pix charges that either credit a brl custody balance or deliver crypto to a wallet, sends pix payouts from that balance, and converts external crypto into a pix payment through a three-step quote, accept, and track flow.

METHOD

PATH

DESCRIPTION

POST

/cashin/charge

Generate a PIX charge for BRL custody or crypto delivery

GET

/cashin/{cashin_id}/status

State of a PIX charge

POST

/payouts

Send a PIX from the BRL balance

POST

/cash-outs

Quote a crypto-to-PIX cash-out

POST

/cash-outs/{cashout_id}/accept

Accept a cash-out and get the deposit address

GET

/saldo

BRL balance, holds, and next releases

GET

/v1/verificar/{e2e}

Verify a PIX happened, no key needed

POST

/keys/sandbox

Get a sandbox API key

POST

/cashin/charge

Generate a PIX charge for BRL custody or crypto delivery

GET

/cashin/{cashin_id}/status

State of a PIX charge

POST

/payouts

Send a PIX from the BRL balance

POST

/cash-outs

Quote a crypto-to-PIX cash-out

POST

/cash-outs/{cashout_id}/accept

Accept a cash-out and get the deposit address

GET

/saldo

BRL balance, holds, and next releases

GET

/v1/verificar/{e2e}

Verify a PIX happened, no key needed

POST

/keys/sandbox

Get a sandbox API key

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Lunium by hand means juggling lun_test_ and lun_ keys in the X-API-Key header, following the three-step cash-out flow, keeping external_id stable across retries, and treating paid, settled, and available as separate states. Through Jentic you install once, import Lunium from the API Directory, store the key once, and your agent calls it.

Permission scoping

Rules filter by method and path, so you can bound the agent to the operations a task needs, such as creating charges and reading status. Cash-out ids sit in the path (/cash-outs/{cashout_id}), so tracking can be pinned to one order. Money-moving operations like payouts, crypto withdrawals, and subaccount transfers are not included unless you add them.

Credential isolation

Your Lunium API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'generate a PIX charge' or 'cash out USDT to PIX', and Jentic returns the matching Lunium operation with its input schema, including enums like destino and pix_key_type, so the agent calls the right endpoint without reading the Portuguese-language docs.

FAQs

Specific to using Lunium — crypto ⇄ PIX settlement (Brazil) API through Jentic.

What authentication does the Lunium API use?

Per its OpenAPI spec, the Lunium API uses an apiKey in the X-API-Key header. Keys starting lun_test_ are sandbox keys that move nothing, and lun_ keys are production; a sandbox key comes from POST /keys/sandbox. Some routes, such as GET /v1/verificar/{e2e}, GET /ping, and the public Mesh directory reads, need no key. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time.

Does a paid PIX charge mean the funds are credited?

No. The spec separates payment completion, settlement, and available balance. A charge from POST /cashin/charge can be paid while settlement is still pending or the funds are on hold, so follow settlement_status on GET /cashin/{cashin_id}/status and the statement at GET /saldo/extrato before treating money as available.

What are the limits for the Lunium API?

The OpenAPI spec states that a payout through POST /payouts is capped at R$ 6.000,00 per PIX, subject to lower account limits, and that limits, fees, and holds are dynamic. Read current per-key limits and daily usage from GET /keys/me and payer limits from GET /cashin/limits, and see https://docs.luniumpay.com/manual for details.

How do I send a PIX payout with Lunium through Jentic?

Install Jentic One, add the Lunium API from the Jentic directory, and store your X-API-Key. Your agent searches for 'send a PIX payout', receives POST /payouts with its amount_cents, pix_key, and pix_key_type schema, and sends it with a stable external_id so a retry after a timeout does not pay twice. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I verify a PIX payment someone says they made?

Yes. GET /v1/verificar/{e2e} confirms a PIX by its E2E identifier without an account or key, and does not return the PIX key, full name, or tax document. If it finds nothing, the response says the PIX may have been made at another institution, so absence is not proof it never happened.

Is there a Lunium MCP server?

Yes - Lunium's spec lists an MCP endpoint at api.luniumpay.com/mcp. You can also connect the Lunium API directly through Jentic: your agent gets the full 66-endpoint surface from the spec without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the Lunium API?

Yes. For a collections agent, allow only POST /cashin/charge, GET /cashin/{cashin_id}/status, and GET /saldo, so it can bill customers and watch settlement but cannot send payouts, withdraw crypto, or move funds between subaccounts. The agent's calls are logged for review.

Luniumpay Lunium — crypto ⇄ PIX settlement (Brazil)

AI ReadinessFoundational (C)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayouts TransfersapiKey (X-API-Key header; lun_test_ sandbox keys, lun_ production keys)66 EndpointsREST

For Agents

Create PIX charges that credit BRL custody or deliver crypto, send PIX payouts, quote and execute crypto-to-PIX cash-outs, and check balances in Lunium. Uses an X-API-Key; a free sandbox key simulates every flow.

Use for: Generate a PIX charge of R$ 150 that credits my BRL balance, Send a PIX payout to this CPF key from my balance, Quote converting 100 USDT on Tron into a PIX payment, Check my available BRL balance and upcoming releases

Not supported: Does not process card payments, issue invoices, or trade crypto on an exchange order book. Use for PIX collection, BRL custody, PIX payouts, and crypto-to-PIX settlement in Brazil only.

The Lunium API settles between crypto and PIX in Brazil: it generates PIX charges that either credit a BRL custody balance or deliver crypto to a wallet, sends PIX payouts from that balance, and converts external crypto into a PIX payment through a three-step quote, accept, and track flow. It also withdraws BRL balance as crypto to a self-custodial wallet, moves funds between customer subaccounts, runs a USDT wallet that can pay a Pix, and verifies that a PIX happened by its E2E identifier without a key. A sandbox simulates cash-in, custody, payouts, crypto withdrawals, transfers, and cash-out with fictitious funds, and production and sandbox are told apart by lun_ and lun_test_ keys sent in the X-API-Key header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

55%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

55%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

67%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

92%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Lunium — crypto ⇄ PIX settlement (Brazil) to your agent

Capabilities

Start building with Lunium — crypto ⇄ PIX settlement (Brazil) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Luniumpay Lunium — crypto ⇄ PIX settlement (Brazil)

Jentic AI Readiness Score

Lunium — crypto ⇄ PIX settlement (Brazil)

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness