Community OpenAPI document · agent-readyPaymentsBilling Subscriptionsoauth23 EndpointsREST
Know of an official OpenAPI document?
Install Jentic One Beta
Connect the Cobrat API v2 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cobrat API v2, 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.
1
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%2Fcobrat.com.br%2Fcobrat-com-br" | sh2
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%2Fcobrat.com.br%2Fcobrat-com-br" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Cobrat API v2 API.
Obtain an OAuth2 client-credentials access token
List issued boletos, the Brazilian bank payment slips
List NFS-e electronic service invoices
Reconcile billing documents against internal records
Use Cases
Patterns agents use Cobrat API v2 API for, with concrete tasks.
★ Boleto reconciliation
Finance teams reconcile issued boletos against payments received. The Cobrat API lists the boletos a company has issued so a reconciliation job can match them to bank movements and flag anything outstanding.
Obtain an OAuth2 token and list this month's boletos for matching against bank statements
NFS-e invoice export
Accounting systems need electronic service invoices for bookkeeping and tax records. The API lists NFS-e records so an export job can pull them into the ledger without manual downloads.
Authenticate and list NFS-e records for the period, returning them for an accounting export
Agent-driven billing check
A finance assistant can answer billing questions on demand. Through Jentic, an agent exchanges credentials for a token and reads the boleto and NFS-e lists to summarize outstanding documents.
Fetch a token, then summarize outstanding boletos and recent NFS-e records for a finance user
Key Endpoints
3 endpoints — the cobrat api v2 is a brazilian billing service for querying boletos (bank payment slips) and nfs-e (electronic service invoices).
METHOD
PATH
DESCRIPTION
POST
/oauth/token
Obtain an OAuth2 access token
GET
/boletos
List issued boletos
GET
/nfses
List NFS-e records
POST
/oauth/token
Obtain an OAuth2 access token
GET
/boletos
List issued boletos
GET
/nfses
List NFS-e records
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Cobrat requires an OAuth2 client-credentials exchange before any query. With Jentic One you install once, import the operations from the API Directory, and the token exchange is handled for you.
Permission scoping
Both operations are read-only queries for boletos and NFS-e, so you can scope an agent to just those reads and keep it away from anything else in your stack.
Credential isolation
Your Cobrat client id and secret are stored encrypted by your own Jentic One instance and used only to mint tokens at execution time, so they never reach the agent's prompt, logs, or context.
Intent-based discovery
Agents find the boleto and NFS-e queries through Jentic's intent search, matching a request like listing this month's boletos to the right Cobrat operation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cobrat API v2 API through Jentic.
How do I authenticate with the Cobrat API?
Cobrat uses the OAuth2 client-credentials flow: your client id and secret are exchanged for an access token that authorizes the boleto and NFS-e queries. Jentic One performs that exchange and injects the token at execution time.
Can I limit what my agent can do with the Cobrat API?
Yes. The service only exposes read operations for boletos and NFS-e, and you choose which of them to import, so an agent can be allowed to read invoices without any broader access.
What is a boleto and what does the API return?
A boleto is a Brazilian bank payment slip. The API returns the list of boletos a company has issued, with their identifying and status fields, as JSON.
Does the Cobrat API issue or cancel boletos?
No. Version 2 of this interface is read-only: it lists existing boletos and NFS-e records but does not create, pay, or cancel them.
What is NFS-e?
NFS-e is the Brazilian electronic service invoice. The API lists a company's NFS-e records so accounting tools can pull them for bookkeeping.
GET STARTED