canonical: https://jentic.com/apis/bancocredicoop.coop/bancocredicoop

# Bancocredicoop Coop Echeq

The Echeq API issues and tracks Argentine electronic checks (echeqs) through Banco Credicoop. It issues individual or batch echeqs, supports a co-signature flow for checks that require a second authorization, and queries the issuance status of a check. Additional operations list echeqs, run management actions on them, and register or look up the beneficiaries a check can be issued to.

## For AI agents

Issue and track Argentine Echeq electronic checks: emit individual, batch, or co-signed echeqs, query issuance status, list and manage echeqs, and register beneficiaries.

## Scope

Does not handle card payments, wire transfers, or account statements. Use for issuing and tracking Echeq electronic checks only.

## Capabilities

- Issue an individual or batch Echeq electronic check
- Issue an Echeq that requires a co-signature through the ConFirma flow
- Query the issuance status of an Echeq
- List echeqs and run management actions on them through the gestion operations
- Register beneficiaries and look one up by its adherent number

## Use cases

### AI Agent Echeq Issuance

An AI agent issues supplier payments as Argentine electronic checks without a developer hand-wiring the bank's OAuth flow. Through Jentic the agent imports the Echeq API, issues an echeq, and reads its issuance status, while the OAuth client credentials stay on the developer's own machine.

Example prompt: Issue an echeq to a registered beneficiary and query the issuance status until it confirms

### Echeq Status Reconciliation

Finance teams need to know which issued echeqs went through. The Echeq API returns the issuance status of a check and lists echeqs, so a workflow can reconcile which supplier checks were issued and flag any that did not complete.

Example prompt: List recent echeqs and return any whose issuance status is not confirmed

### Beneficiary Onboarding

Before issuing an echeq a payer must have the beneficiary on file. The Echeq API registers a new beneficiary and looks one up by its adherent number, so an agent can confirm a counterparty exists before issuing a check to them.

Example prompt: Look up a beneficiary by its adherent number and register it if the lookup returns no match

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/emision` | Issue an Echeq |
| GET | `/emision` | Query Echeq issuance status |
| POST | `/lista-cheques` | List echeqs |
| POST | `/gestion` | Run management actions on echeqs |
| POST | `/ConFirma/emision` | Issue an Echeq with a co-signature |
| GET | `/beneficiario/{numeroAdherente}` | Look up a beneficiary |
| POST | `/beneficiario` | Register a beneficiary |

## Key resources

- **Emision** — Issue individual or batch echeqs and query their issuance status
- **ConFirma** — Issue and manage echeqs that require a co-signature
- **Lista** — List the echeqs associated with an account
- **Gestion** — Run management actions on existing echeqs
- **Beneficiario** — Register beneficiaries and look one up by adherent number

## 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:** 51 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 59 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 29 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/bancocredicoop.coop/bancocredicoop/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:** Wiring the Echeq API by hand means implementing its OAuth 2.0 client credentials exchange, handling the ConFirma co-signature flow, and matching beneficiaries before issuance. Through Jentic you install once, import Echeq from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Access runs through one OAuth client, so a rule bounds the agent to the operations it needs, such as querying and issuing echeqs. You choose which operations it may call, so beneficiary changes and management actions are not included unless you add them.
- **Credential handling:** Your Echeq OAuth client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'issue an Echeq' or 'check issuance status', and Jentic returns the matching Echeq operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Stripe processes card and online payments rather than issuing bank-rail electronic checks.
- **Adyen Payments** — Adyen processes card and local payment methods through a global gateway.
- **Plaid** — Plaid verifies bank accounts and reads account and transaction data.

## FAQ

### Is there an Echeq MCP server?

You don't need an MCP server to give your agent the Echeq API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so nothing extra loads into the agent's context.

### Can I limit what my agent is allowed to do with the Echeq API?

Yes. Write a rule that allows only the echeq query and issuance operations, so the agent can issue checks and read their status but cannot register beneficiaries or run management actions, and every call is logged.

### What authentication does the Echeq API use?

The Echeq API authenticates with OAuth 2.0, using the client credentials flow declared in its OpenAPI spec to obtain an access token. Through Jentic the client credentials are stored encrypted by your own Jentic One instance and exchanged for a token at call time, so they never reach the agent's prompt or logs.

### Can I issue a co-signed Echeq with the Echeq API?

Yes. The ConFirma emission operation issues an echeq that requires a second authorization, and the matching ConFirma management operation handles the follow-up actions on those co-signed checks.

### How do I issue an Echeq through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Echeq API from the Jentic API Directory and store your OAuth client credentials. Your agent searches for 'issue an Echeq' and Jentic returns the issuance operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### What are the rate limits for the Echeq API?

The Echeq OpenAPI spec does not define rate limits. Banco Credicoop governs throughput through its API onboarding, so confirm the limits that apply to your institution before high-volume issuance.