Revolut APIs for AI Agents
PaymentsPayment ProcessingStorefrontMixed ProvenanceAPI keyBearer tokenSSL, apiKeyAgent Ready
Revolut API Catalog
4 APIs across 2 product groups.
Payments3
Which Revolut API should I use?
| I want to... | Use | Why |
|---|---|---|
| Read a customer's account balances and transactions with their consent | Open Banking API | The Open Banking API uses account access consents to read accounts, balances, beneficiaries, and direct debits for third-party providers. |
| Automate your own business accounts, cards, and counterparty payments | Business API | The Business API manages your Revolut Business accounts, issues and controls cards, validates counterparties, and runs currency exchanges. |
| Accept and manage online payments for e-commerce checkout | Merchant API | The Merchant API creates, captures, cancels, and refunds payment orders and tracks payouts and disputes. |
| Let users buy crypto with fiat inside your product | Crypto Ramp API | The Crypto Ramp API returns quotes, buy redirect URLs, and order status for embedding fiat-to-crypto purchases. |
Install Jentic One Beta
Connect the Revolut APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Revolut APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Each Revolut API has its own host, auth scheme, and signing requirements to wire up by hand. Through Jentic you install once, add the Open Banking, Business, Merchant, or Crypto Ramp API from the Jentic directory, store each credential once, and your agent calls any of them.
Permission scoping
Your own rules in your Jentic One instance decide which Revolut operations and credentials an agent may use. You can pin an agent to read-only account access on Open Banking while blocking money-moving Business or Merchant operations like creating cards or refunding orders unless you add them.
Credential isolation
Each Revolut credential, the Open Banking and Crypto Ramp API keys, the Business bearer token, and the Merchant API key, is stored encrypted by your own Jentic One instance and injected at execution time. None of them enter the agent's prompt, logs, or context.
FAQs
Specific to using Revolut APIs through Jentic.
What can an AI agent do across Revolut's APIs?
An agent can read consumer account data with open banking consents, manage Revolut Business accounts and cards, create and settle online payment orders, and quote fiat-to-crypto purchases. It can chain these, such as validating a payee before a payment or reconciling a merchant order against a business account balance.
Do I need separate credentials for each Revolut API?
Yes. The Open Banking, Business, Merchant, and Crypto Ramp APIs each use their own credential and auth scheme. Through Jentic, each credential is stored encrypted in your own Jentic One instance and injected only when the relevant API is called.
Which Revolut API handles online e-commerce payments versus business banking?
Use the Merchant API to accept and manage online payment orders for e-commerce checkout, and the Business API to automate your own Revolut Business accounts, cards, and counterparty payments. The Open Banking API is for regulated access to a customer's own account data.
Can an agent move money between these APIs automatically?
Each API operates on its own product surface, so there is no single money-movement call spanning all four. An agent can coordinate a flow across them, for example capturing a Merchant order and then reading the settlement on a Business account, but each step calls its own API.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
