canonical: https://jentic.com/apis/mercantilbanco.com/mercantilbanco # Mercantilbanco Búsqueda de Transferencias The Mercantil Banco Transfer Search API retrieves the inbound transfers received by a client account so a team can confirm and reconcile incoming payments. A single search operation accepts the lookup criteria and returns the matching received-transfer records. It is a read-only view over received transfers at Mercantil Banco, built for quick confirmation rather than payment initiation. ## For AI agents Search the transfers a Mercantil Banco client has received and return the matching records, so an agent can confirm and reconcile incoming payments. Read-only over received transfers. ## Scope Does not initiate transfers, open accounts, or issue cards. Use for searching the transfers a client account has received only. ## Capabilities - Search the transfers received by a client account - Confirm whether a specific incoming payment has arrived - Reconcile received transfers against expected payments ## Use cases ### Agent payment reconciliation An AI agent closing the books confirms which expected payments have actually landed. The Mercantil Banco Transfer Search API returns the received transfers matching the search criteria, so the agent can tick off incoming payments against invoices. Through Jentic the search operation is discovered by intent and the client credential is injected at call time. Example prompt: Search for a received transfer matching an expected payment and confirm it has arrived ### Incoming payment confirmation Finance teams waiting on a customer transfer need a fast way to check it has been received. The Mercantil Banco Transfer Search API runs a search over received transfers and returns the matching records, so an agent can poll for a specific payment and report back the moment it appears. Example prompt: Search received transfers for a given customer payment and report whether it has been received ### Received-transfer monitoring A back-office workflow reviews the day's incoming transfers. The Mercantil Banco Transfer Search API returns the received transfers that match the supplied criteria, so an agent can pull the day's inbound payments for a client account and hand them to a downstream ledger. Example prompt: Search the received transfers for a client account over a given period and return the matching records ## Key resources - **Received Transfers** — Search the inbound transfers received by a client account and return the matching 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:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 76 / 100 - AI-Readiness & Agent Experience: 20 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/mercantilbanco.com/mercantilbanco/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 ``` ## Why Jentic - **Setup:** Wiring this API by hand means obtaining a client id for the bank's API gateway, sending it in the X-IBM-Client-Id header, and parsing the received-transfer records yourself. Through Jentic you install once, import it from the API Directory, store the client id once, and your agent searches received transfers through it. - **Permission scoping:** The API exposes only a transfer-search operation that carries its criteria in the request body, so a rule can allow that single read operation and nothing else. You choose the operation set, so the agent reaches no other operation unless the bank adds one and you include it. - **Credential handling:** Your Mercantil Banco client id is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search received bank transfers', and Jentic returns the matching Mercantil Banco operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Plaid** — Plaid reads bank account and transaction data across many institutions. - **Stripe** — Stripe processes payments and reports balances and transfers for online businesses. - **Adyen Transfer Service** — Adyen's transfer service moves and reconciles funds across balance accounts. ## FAQ ### What authentication does the Mercantil Banco Transfer Search API use? The API expects an api key in the X-IBM-Client-Id header, per its OpenAPI spec, issued through Mercantil Banco's API gateway. Through Jentic the client id is stored once and injected at call time, so it never enters the agent's prompt, logs, or context. ### Can I confirm a specific received payment with the Mercantil Banco Transfer Search API? Yes. The single search operation accepts your lookup criteria and returns the received transfers that match, so an agent can search for an expected payment and confirm whether it has arrived. It reads received transfers only and does not move money. ### What are the rate limits for the Mercantil Banco Transfer Search API? The OpenAPI spec does not define numeric rate limits; limits are set by the bank's API gateway for your client id. Have your agent back off when it receives an HTTP 429 response and contact Mercantil Banco for the current limits. ### Is there a Mercantil Banco MCP server? You don't need an MCP server to give your agent the Mercantil Banco Transfer Search API. Jentic connects it directly from the API Directory: import it, store your client id once, and your agent searches received transfers through it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context. ### Can I limit what my agent is allowed to do with the Mercantil Banco Transfer Search API? Yes. The API exposes only a transfer-search operation, and it carries its criteria in the request body, so a rule can allow that single read operation and nothing else. The agent can look up received transfers but cannot reach any other operation, and every call it makes is logged. ### How do I search received transfers through Jentic? Search Jentic for an intent such as 'search received bank transfers' and it returns the matching search operation with its input schema, so your agent passes the lookup criteria and reads back the matching records. To run it on your own infrastructure, install Jentic One from its GitHub repo.