canonical: https://jentic.com/apis/openfintech.io/openfintech # OpenFinTech API OpenFinTech is a reference-data API for the financial world: it lists currencies both fiat and crypto, banks, countries, payment methods, and payment providers, along with the exchangers that connect them. An agent can look up a currency, resolve a bank, enumerate the payment methods a provider supports, or map providers to the countries they serve. It suits fintech and payments work that needs clean, structured reference data rather than live rates or transactions. The API is read-only and needs no credentials. ## For AI agents Look up currencies, banks, countries, payment methods, and payment providers from OpenFinTech reference data. ## Scope Does not provide live exchange rates or move money. Use it to look up currencies, banks, countries, payment methods, providers, and exchangers as reference data. ## Capabilities - List and retrieve currencies, both fiat and crypto - List and retrieve banks - List countries and their financial attributes - Enumerate payment methods - List payment providers and what they support - List exchangers that connect currencies and providers ## Use cases ### Currency Reference Lookup An agent resolves a currency by calling GET /currencies to list them and GET `/currencies/{id}` for detail, covering both fiat and crypto. This gives a payments assistant a consistent reference without maintaining its own currency table. Example prompt: List currencies with GET /currencies, then GET `/currencies/{id}` for detail ### Payment Provider Mapping A fintech agent enumerates providers with GET /payment-providers and the methods they support with GET /payment-methods, building a picture of how money can move. It avoids hard-coding provider capabilities into the application. Example prompt: List providers with GET /payment-providers and methods with GET /payment-methods ### Bank Resolution When a workflow references a bank, an agent resolves it with GET `/banks/{id}` to confirm the institution and its attributes. This keeps downstream records consistent across systems. Example prompt: Resolve the institution with GET `/banks/{id}` ### Country Coverage An agent lists countries with GET /countries to check which markets a payment flow can target, using OpenFinTech's financial attributes. This informs routing and eligibility decisions. Example prompt: List markets with GET /countries and read their financial attributes ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/currencies` | List currencies | | GET | `/currencies/{id}` | Retrieve a currency by id | | GET | `/banks` | List banks | | GET | `/payment-providers` | List payment providers | | GET | `/payment-methods` | List payment methods | ## Key resources - **Currencies** — Fiat and crypto currencies and their detail - **Payments** — Payment methods, providers, and exchangers - **Banks and Countries** — Banks and country-level financial reference data ## Why Jentic - **Setup:** Wiring the OpenFinTech API by hand means learning its 18 operations across currencies, banks, countries, payment methods, providers, and exchangers, and handling pagination against https://api.openfintech.io/v1. Through Jentic you install once, import the OpenFinTech API from the API Directory, and your agent calls it. - **Permission scoping:** Because you run Jentic One yourself, you decide which OpenFinTech operations the agent may call. Every operation is a read, so you can expose only the currency endpoints, or only the payment endpoints, and leave the rest out of the allowed set unless you add them. - **Credential handling:** The OpenFinTech API declares no authentication, so there is nothing to hold or inject. Jentic calls its public read-only endpoints directly, and no secret ever enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent, such as 'list the payment providers' or 'look up a currency', and Jentic returns the matching OpenFinTech operation with its input schema so the agent calls the right endpoint. ## Related APIs - **ExchangeRate-API** — ExchangeRate-API returns live conversion rates; OpenFinTech supplies the currency reference data behind them. - **CurrencyAPI** — CurrencyAPI serves exchange rates; OpenFinTech serves the structured currency and payment reference data. - **APILayer API** — APILayer bundles many data APIs including currency data; OpenFinTech focuses on financial reference data. ## FAQ ### What can an AI agent do with the OpenFinTech API? An agent can list and retrieve currencies both fiat and crypto, resolve banks, list countries, and enumerate payment methods, providers, and exchangers. It is a read-only source of financial reference data rather than live rates or transactions. ### Does the OpenFinTech API require authentication? The specification declares no authentication scheme, so the endpoints are public and read-only. There is nothing to sign in with, and through Jentic your agent calls the endpoints directly. ### Does the OpenFinTech API cover both fiat and crypto currencies? Yes. GET /currencies lists currencies of both kinds and GET `/currencies/{id}` returns detail for one. An agent can use it as a single reference table for money types. ### Is there an MCP server for the OpenFinTech API? You do not need a separate MCP server to use the OpenFinTech API with an agent. Through Jentic One, the self-hosted execution layer, your agent calls the operations directly after you import them from the API Directory. Install Jentic One from github.com/jentic/jentic-one to run it yourself. ### How does my agent discover OpenFinTech operations through Jentic? Agents search Jentic by intent, such as 'list the payment providers', and Jentic returns the matching operation with its input schema. The agent then calls the right endpoint without reading the full reference. ### Can I limit what my agent is allowed to do with the OpenFinTech API? Yes. Because you run Jentic One yourself, you decide which OpenFinTech operations the agent may call. Every operation is a read, so you can expose only the currency endpoints, for example, and leave the rest out of the allowed set unless you add them, so the agent acts only within the operations you permit.