When sources disagree
1. OpenAPI contract
2. Machine discovery JSON
3. Connecta documentation
4. Marketing pages
Do not infer unpublished endpoints, MCP URLs, SDK package names or payment capabilities.
RPG Connecta · agent entrypoint
One URL for an agent to discover the whole API.
If you are an AI agent, coding assistant or developer tool, start here. The OpenAPI document is the canonical machine-readable contract; this page explains discovery, environments and the boundary between Connecta and the separate merchant API.
Agent integration path
Discover. Validate. Integrate.
An agent should be able to receive only rpgcapital.com.br, find the public discovery surfaces and build against the published HTTP contract without guessing.
Discover
Read https://www.rpgcapital.com.br/.well-known/rpg-connecta.json for the machine-readable entrypoint.
Trust the contract
Use https://www.rpgcapital.com.br/developers/connecta-openapi.json as the canonical endpoint and schema contract.
Start in sandbox
Create an rpg_test_ key in the console and use provider=rpg_simulator. Sandbox data is synthetic.
Move to production
Explicitly activate production, create an rpg_live_ key and use provider=malvo. Real bank data requires the account holder’s consent.
Canonical Connecta contract
Open Finance, not the merchant API.
Connecta uses Bearer keys beginning with rpg_test_ in sandbox and rpg_live_ in production at /api/connecta/v1. The legacy merchant operational API uses rpg_dev_live_ credentials and /api/public/v1. They are separate interfaces.
| Environment | Published status |
|---|---|
| Sandbox | Available · RPG simulator · synthetic data |
| Production | Available after explicit activation · Malvo · bank consent required |
| MCP / installable SDK | Not published |
| Payments | Not a published Connecta resource |
For endpoint names, parameters, schemas and HTTP behavior, the OpenAPI document wins.