# RPG for Developers — public sandbox guide

Version: demo-1. Updated: 2026-10-30.
Official website: https://www.rpgcapital.com.br/integracoes
Human guide: https://www.rpgcapital.com.br/developers/ai

## Availability
- Available: public synthetic financial-data sandbox, no account, no card and no API key.
- Available separately: Google Developer login, applications, scoped keys and merchant-authorized operational API.
- Not yet available as Connecta developer products: real-bank production onboarding, prepaid billing, published SDK packages or operational MCP endpoint. Do not invent installation commands, MCP URLs or production pricing.
- This is a guide, not an installable skill or a published SDK.

## First request
GET https://www.rpgcapital.com.br/developers/sandbox/data?scenario=retail
Other accepted scenarios: restaurant, personal. Default: retail.
No credentials. Response: application/json. Read-only and deterministic.
Invalid scenarios return HTTP 400 with error.code invalid_scenario.

## Response schema
meta: environment=sandbox, synthetic=true, schema_version=demo-1, scenario, updated_at, note.
account: id, name, currency.
summary: opening_balance_minor, income_minor, expenses_minor, closing_balance_minor.
transactions[]: id, date, description, amount_minor, currency, direction, category {id,name}, tags[].
amount_minor: nonnegative integer, in BRL centavos. direction: credit or debit. Use direction to calculate signed values. Divide by 100 only for display.
closing_balance_minor = opening_balance_minor + income_minor - expenses_minor.
Dates and data are fixed fixtures, not current financial information. The whole small fixture is returned; this demo has no pagination, mutations or bank consent.
Categories and tags are demo values, not the production provider taxonomy.

## Build a first dashboard
1. Fetch a scenario and check the HTTP status.
2. Display the synthetic-data label visibly.
3. Show income, expenses, closing balance and transaction rows.
4. Handle network errors and allow retry; never present a failed request as successful.
5. Test all three scenarios and one invalid scenario.
6. Do not infer production bank availability from these fixtures.

## Existing merchant operational API (separate)
Docs: https://www.rpgcapital.com.br/developers/docs
OpenAPI: https://www.rpgcapital.com.br/openapi.json
Login: https://www.rpgcapital.com.br/developers/login
Base: https://www.rpgcapital.com.br/api/public/v1
Authentication: Authorization: Bearer <RPG_API_KEY> and X-RPG-Connection-Id.
A Developer key alone never grants access to a merchant. Effective permission is the intersection of key scopes and merchant grant scopes. Keep secrets server-side. Do not paste them into chat.
The existing OpenAPI describes the merchant API, not this synthetic sandbox.

## Machine-readable discovery
https://www.rpgcapital.com.br/llms.txt
https://www.rpgcapital.com.br/llms-full.txt
https://www.rpgcapital.com.br/integracoes.md
https://www.rpgcapital.com.br/developers/ai/guide.md

## Português
O RPG Connecta tem uma demonstração pública de dados financeiros fictícios. Teste sem conta, cartão ou chave. Selecione retail, restaurant ou personal. Valores são inteiros em centavos de real; direction informa entrada ou saída. A API de lojas RPG é um produto separado e exige autorização. Open Finance Connecta em produção, cobrança, MCP operacional e SDKs estão em preparação.