Revolut just launched an AI assistant. You can launch yours this week.

Revolut just launched an AI assistant. You can launch yours this week.

Headshot of Robbie Tilleard, a male blog author, smiling at the camera wearing a dark blazer and white shirt.

Robbie Tilleard

|

|

0 Mins

On April 9, 2026, Revolut launched AIR - an AI financial assistant embedded directly in their app. Customers swipe down and ask "freeze my physical card" or "how much did I spend on subscriptions last month?" Three weeks earlier, Starling Bank shipped what it called the UK's first agentic AI financial assistant. HSBC, Barclays, and NatWest are all signing deals with AI labs to build their own.

You can ship the same thing in days using Lorikeet's SDK.

Not a chatbot. Not FAQ search. A fully embedded AI agent that takes real actions inside your product - freezing cards, setting up transfers, checking insurance - the exact capability the biggest fintechs in the world just made headlines for.

What they actually built

Strip away the press release and AIR is a straightforward architecture. A conversational interface sits inside the app. A customer types a request. The system pulls their data, reasons about it, and takes an action.

Chatbots summarise help articles. Agents do things. That distinction is what makes these launches significant, and it's what every fintech customer is about to expect as standard.

Revolut first teased this at their "Revolutionaries" event in November 2024. Starling describes theirs as the culmination of eight years of AI development. Both are UK-only, with other markets "coming soon."

How Lorikeet's SDK works

Lorikeet's SDK is a REST API that lets you embed a fully capable AI agent inside your product. Your engineering team builds the interface - a chat bubble, a swipe gesture, whatever fits. The SDK handles everything else: natural language understanding, action execution, compliance guardrails, multi-turn conversations, streaming responses.

Your product, your experience, your brand. The AI is invisible infrastructure. Exactly the architecture Revolut built for AIR - except you plug in rather than build from scratch.

The question most fintechs ask next is: how do you actually get the agent to do useful things? Connect to your systems, follow your policies, handle your edge cases?

That's where Coach comes in. Coach is Lorikeet's AI-powered setup assistant. Describe what you want your agent to handle - "when a customer asks to freeze their card, verify their identity, freeze it, and offer a replacement" - and Coach generates the workflow, the API connections to your backend, the compliance guardrails, and the test scenarios to validate it all works. What used to take weeks of configuration is now a conversation.

You don't need to worry about compliance

Lorikeet is SOC 2 and ISO certified. The patterns for financial services - data handling, PII protection, audit trails, escalation rules - are built into the platform and tested in production.

Fintechs like Airwallex, Self, Taptap Send, and Step already run Lorikeet agents across their customer support operations. They handle real financial queries with real compliance requirements every day. The platform works for fintech because it's been shaped by fintech.

You don't need to solve compliance from scratch. You configure it for your specific policies, and Coach helps you do that too.

The compounding advantage of going first

Revolut is UK-only. Starling is UK-only. The traditional banks are still in partnership announcement territory. If you're operating in the US, Europe, or APAC, your customers haven't seen this yet.

You have a window. Ship now and by the time the big players roll into your market, your agent has months of real conversations behind it. Months of edge cases handled, workflows refined, escalation paths tested. That compound advantage is hard to replicate once someone else has it.

Of course, speed alone isn't enough. Klarna learned that the hard way - their AI assistant handled 2.3 million conversations in its first month, but quality collapsed and they ended up re-hiring human agents by mid-2025. The conversational interface is the easy part. Getting the agent to reliably resolve problems across thousands of scenarios is the hard part, and it's the part you shouldn't be building from scratch.

Revolut spent a year. You don't have to.

Embed a capable agent into your existing product. Connect it to your systems. Let Coach build the workflows. Deploy in days.

Your customers don't know or care what's under the hood. They care that it works.

Book a call

See what Lorikeet is capable of

Share this article

Related posts

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.