Subscription → API
Use the plans you already pay for
A subscription signs in to its own apps and nothing else. megaloop gives it a key, so any tool can use the capacity you already bought.
Multi-account AI inference gateway
You already pay a flat monthly fee. megaloop pools every account you link.
Subscription → API
A subscription signs in to its own apps and nothing else. megaloop gives it a key, so any tool can use the capacity you already bought.
Pooled & quota-aware
Five accounts on Starter, twenty on Pro. Work stays on one account until it runs low, then moves to the next with room.
Run by your agent
Every part of megaloop is an API, with an MCP server over it. Hand your coding agent one block and it makes the account, links your subscriptions, and runs them for you.
Link the subscriptions you already pay for. Approve in your browser, or paste a key. megaloop shows you which providers it supports.
Point your client at one base URL and give it your key, or let your agent do it. Your existing tools don’t know the difference.
A client sits on one account until that account is nearly spent, then moves to the next with room. megaloop shows which one is burning its limit.
What your subscriptions can serve through the pool right now. The megaloop- names are for editors that refuse to let you name a model they already ship.
No dashboard, no signup form. It needs two things from you: the six-digit code we email, and your yes to the terms — which it has to ask for, because the account being created is yours.
Set up megaloop for me, then use it.
megaloop pools the AI subscriptions I already pay for behind one endpoint and one key, routing
each request to an account that still has quota. Replies carry a "guidance" note about the call
you just made; read it. Full reference: https://megaloop.dev/llms.txt
1. ACCOUNT: two calls, no browser. The code arrives in my inbox — ask me for it.
POST https://megaloop.dev/v1/auth/code {"email":"MY_EMAIL"}
POST https://megaloop.dev/v1/auth/verify {"email":"MY_EMAIL","code":"CODE",
"accepted_terms":true}
Read the first reply before sending the second: it says what the second commits me to. The
second creates my account and returns a session token — hold it in memory, never in a file.
2. KEY: shown once. Save it where I keep secrets — it is what you use from step 4 on.
POST https://megaloop.dev/v1/keys bearer: the session token
{"name":"agent","capabilities":["read","inference"]}
A key carries read (my accounts, usage, traffic, plan), inference (serve requests, choose which
account they land on) and manage (link accounts, mint and revoke keys). Sending none gets
["inference"] alone; add manage only to link or rotate for me later, and ask me first — no key
widens itself, so adding it costs another code from my inbox.
3. LINK A SUBSCRIPTION: GET /v1/providers lists what I can link. Link with the session token, not
the key: linking puts an upstream into my pool, so the key from step 2 cannot do it.
POST /v1/accounts/link/direct a provider I hold a key for
POST /v1/accounts/link/start + /complete one that needs me to sign in
4. POINT MY APP AT IT: base URL https://api.megaloop.dev, my key as a bearer token. Then send one
real request through it and check content comes back.
5. POOLS: optional, and skip it unless I ask. A pool is a named subset of my accounts, and a key
bound to one reaches only those. Set the membership before minting the key — an empty pool with
a live key serves nothing at all.
POST /v1/pools {"name":"NAME"}
PUT /v1/pools/ID/accounts {"account_ids":["..."]}
POST /v1/keys {"name":"NAME","pool_id":"ID"}
6. GIVE YOURSELF THE TOOLS: the MCP server, so you call tools instead of curl. Needs node 20+.
Write this into whatever config my MCP client uses, then restart the client. Do not set
MEGALOOP_BASE_URL. Then call its `help` tool.
{"mcpServers":{"megaloop":{"command":"npx","args":["-y","megaloop-mcp"],
"env":{"MEGALOOP_API_KEY":"MY_KEY"}}}}Your team's plans reach every tool they use. Nothing is billed per token.
No token bill
The plans your team already buys become the capacity everyone codes against. Nothing is counted per token, so a heavy month costs what a quiet one does.
Ring-fenced
Set aside plans for a team and their key stays inside them. Traffic never crosses into capacity you reserved for someone else.
Visible
Every request is recorded against the key that made it and the plan that served it, so you can see where the capacity went without a per-token invoice to read.
14 days freeEvery account starts on a full-feature trial. No card, and the same twenty accounts Pro allows. Monthly after that.
megaloop
One API endpoint for every subscription you already pay for.
Works with the accounts you are authorised to connect. Whether your plan permits a given use is between you and that provider.
megaloop is not affiliated with, endorsed by, or sponsored by any provider. Provider names appear only to tell you which of your own accounts is which.