Install Jentic One Beta

Connect the Echeq to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Echeq, 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.

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%2Fbancocredicoop.coop%2Fbancocredicoop" | sh

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%2Fbancocredicoop.coop%2Fbancocredicoop" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Echeq API.

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

GET STARTED

Start building with Echeq API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Echeq API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

8 endpoints — the echeq api issues and tracks argentine electronic checks (echeqs) through banco credicoop.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Echeq API through Jentic.

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.

Bancocredicoop Coop Echeq

AI ReadinessFoundational (C-)51/100

See full scorecard

Community OpenAPI document · agent-readyFinanceBankingoauth28 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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

Use for: Issue an Echeq to a supplier, I want to check whether an Echeq was issued, List the echeqs on an account, Register a new beneficiary

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

88%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

25%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

88%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Echeq to your agent

Capabilities

Start building with Echeq API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Bancocredicoop Coop Echeq

Jentic AI Readiness Score

Echeq

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness