canonical: https://jentic.com/apis/cobrat.com.br/cobrat-com-br

# Cobrat API v2

The Cobrat API v2 is a Brazilian billing service for querying boletos (bank payment slips) and NFS-e (electronic service invoices). After obtaining an OAuth2 client-credentials token, an integration can list issued boletos and list NFS-e records, giving finance tools a programmatic view of a company's billing documents.

## For AI agents

Lets an AI agent authenticate with OAuth2 and list a company's boletos and NFS-e service invoices from Cobrat.

## Scope

Does not issue, pay, or cancel boletos and does not file taxes: use it to read Cobrat boletos and NFS-e records only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Fetch a token, then summarize outstanding boletos and recent NFS-e records for a finance user

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth/token` | Obtain an OAuth2 access token |
| GET | `/boletos` | List issued boletos |
| GET | `/nfses` | List NFS-e records |

## Key resources

- **OAuth token** — Exchange client credentials for an access token
- **Boletos** — List issued bank payment slips
- **NFS-e** — List electronic service invoice records

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 60 / 100
  - AI-Readiness & Agent Experience: 22 / 100
  - Agent Usability: 94 / 100
  - Security: 85 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/cobrat.com.br/cobrat-com-br/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **NuPay Business** — Brazilian payments platform for collecting on billing
- **Checkout.com** — Global payment processing beyond Brazilian boletos
- **Nuvemshop** — Brazilian commerce platform that generates orders and invoices

## FAQ

### 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.