Skip to main content
The API is pay-per-use, drawn from the balance of the account that owns the credential. Balance is in coins (1 coin = R$ 1.00).

​
Flat fee + pass-through

Every call has up to two cost components:
1

Flat platform fee

A small amount per request, drawn from the account. Only API-key calls pay it — session-JWT calls (the app) don’t.
2

Pass-through (when applicable)

If the call triggers an external provider (transcription, AI, YouTube), its real cost is also drawn — from the owner of the resource. Plain reads serve from the database and have no pass-through.

​
Flat fee per route

The fee is drawn after the response, best-effort — a billing failure never drops your call. Prices may change as the platform evolves.

​
Insufficient balance

Before processing an API-key call, the API checks the balance. Zero or negative → the call is rejected up front:
A long-running job can also fail mid-flight with 402 if a pass-through provider call would overdraw the resource owner.

​
Top up via Pix

Coins are bought with Pix (1 coin = R$ 1.00):
1

Create the charge

POST /v1/accounts/me/deposit/pix with { amount_coins, cpf } → returns the QR Code (base64) and the copy-and-paste code. Minimum 5 coins.
2

Pay

Pay the Pix from your bank app. (InfinitePay is also available, fee-free, via POST /v1/accounts/me/deposit/infinitepay, which returns a checkout link.)
3

Automatic credit

On confirmation, the provider notifies the API and the coins are credited — you get a deposit_credited event in real time.

​
Track usage & withdraw

  • Balance: GET /v1/accounts/me.
  • Ledger: GET /v1/accounts/me/transactions (filter by kind, ref_type).
  • Withdraw the deposited pool back to BRL: POST /v1/accounts/me/withdraw (bonus credit isn’t withdrawable).