Keelie gives your API its own plans and prices, makes it findable by AI agents, and lets people fund a balance that their agents spend. The money goes straight to your Stripe.
A free plan at launch. No card, no call.
› POST /v1/clips 200 OK
−12 credits · access renews in 14:52
› POST /v1/clips 200 OK
−12 credits · balance 4,176
Ana pays. Ana’s agent calls.
Your API and MCP server came after your app, and they’re still sold as part of it. How fast agents change that is anyone’s guess, ours included. Today, they can’t get in.
Use Acme to cut this into a 30-second clip.
I can’t find a way to use Acme’s API. You’d need to open the Acme app.
✕ no way in
It has no price of its own. Your API comes free with the subscription, so a company that wants it inside its own software has to buy your app. Or go without.
Agents can't find it. There's no AI catalog on your domain to tell an agent what your API does. And the Claude and ChatGPT directories check for a secure sign-in, which fewer than 1 in 10 MCP servers have.
Agents can't sign up. An agent can't fill in your signup form or copy a key from your dashboard. And paying by use with no limit ends in surprise bills.
If you’ve used OpenAI’s or Anthropic’s platform, you know the shape: sign up, pick a plan, add a balance, set a cap, and point your agents at it. Keelie gives your API the same shape, beside the app you already sell.
Use Acme to cut this into a 30-second clip.
Found Acme’s API. It needs your approval, once.
✓ approved on Acme’s consent screen
Done. Your clip is ready.
Ana’s balance: 4,200 → 4,188 credits
Its own plans and prices. Pay-as-you-go plans for your API and MCP server, beside your subscription. Your app's pricing doesn't change.
Findable by agents. Keelie publishes your AI Catalog on your domain, in step with your plans. It also gives you the sign-in the Claude and ChatGPT directories check (you still apply, and they decide), and the Keelie Registry will let agents search for you.
A way in that agents can use. A person signs up, adds a balance, sets their own cap and approves their agent once. Access lasts minutes and renews only while the balance lasts, so nobody gets a bill they didn't expect.
People pay. Agents call. Access and money never drift apart.




Keelie is in early access. There’s no list of Keelie customers to show you, and pretending otherwise would be a poor start.
Apiable already runs dynamic client registration in production: software registering itself, with no signup form involved.
Sign-in is OAuth 2.1. Claude and ChatGPT connectors sign in with OAuth too. Discovery follows the AI Catalog and ARD formats.
Payments go straight into your own Stripe account. We never hold funds.
They find you. People find your API’s page. Agents can read the AI Catalog on your domain, and the Keelie Registry will let them search for you.
Both change when your plans do.
A person opens an account. On your API’s page, they pick a plan, add a balance and set a spending cap.
They approve their agent, once. Your consent screen shows what the agent can do on their plan. One click, and the agent is connected.
The agent calls your API. Every top-up pays into your Stripe. Every call draws the balance down. When the balance runs out, Keelie stops issuing access, and it ends within minutes. There’s never an invoice to chase.
Access renews while the balance lasts.
Want this for your API? Get early access →
Why not just wire it to Stripe?
You’d send the same usage events. Stripe turns them into invoice lines to reconcile. Keelie draws down a prepaid balance and stops renewing access when it’s empty, which Stripe can’t do in real time.
Nothing until your API earns. Then 3% of what your customers pay you, plus Stripe's standard fees.
You still set the prices and talk to your first customers. Keelie meters the use and stops access when a balance runs out.
Nobody knows when agents will matter to API revenue, us included. We're betting they will. You don't have to: people can buy your API on its own from the start, agent or not. Either way, you've opened a second way to sell it.
Keelie is a headless API monetization engine. It gives your API and MCP server their own usage-based plans and prices, a sign-in that people and AI agents can use, and a prepaid balance whose payments go straight to your Stripe. You build the pages. Keelie runs the sign-in, the balance and the metering.
No. Keep it. Keelie is a second way in, for the people and companies who want your API without your app, and for the agents they send. They may not be the same people as your app's users.
No, and nobody can promise that. But Keelie lays the foundations their directories check: the secure sign-in and the consent screen. You still apply, and they decide.
Not today, and that's by design. People fund the balance and their agents spend it, the way an OpenAI or Anthropic account works. If agents start carrying their own payments, we'll look at adding it.
Calls to your API never pass through Keelie, and your Stripe account, your customers and your money are yours. If you ever leave, the sign-in and the metering are what you'd replace. Your API and your Stripe account don't change.
Read it left to right.
01 Set it up
02 Get found
03 Someone buys
04 Every call
05 The money
06 Keep it running
Every plan, the free one included, has what earns you money: your plans and prices, payment into your Stripe, caps your customers set, your AI Catalog, and the sign-in AI directories check. Paid plans add help running it.
PAYG
€0 forever
Growth
€499 a month
Scale
€1,999 a month
A connection is each app your customers connect, and each person who adds your API inside Claude or ChatGPT, counted once in any month it’s used. Free plans count too.
At the limit, nobody already active is cut off. New connections wait until you add capacity. On PAYG, extra capacity comes in packs: 500 more for €149 a month, or 2,000 more for €399 a month.
Keelie is in early access. Tell us what your API does and how people pay for it today, even if that’s “they don’t”. We’ll tell you straight whether Keelie fits it now, and if not, what’s missing.
No card, no call. Two questions and an email address.