Create one
Open API keys
Go to agentmore.app/app/api-keys.
Copy it now
The full key is shown once. After you close the dialog only the name and a
truncated preview remain.
Paste it where your agent asks
A skill file prompts you for it; an MCP client takes it as a bearer token, as
on MCP server.
agentmore_sk_ prefix is secret. Treat it like a password: it
belongs in your agent’s config, not in a repo, a ticket or a chat message.
What the scope covers
Every key has one scope, shown in the app assupertool — the internal name for
skills. It reaches the tool catalog and your own runs, and nothing else.
A key cannot sign in to the app, read your chats, files or sites, change your
password or two-factor settings, change your plan, or raise
your budget caps.
So the worst a leaked key can do is spend, and only up to the caps you set at
Budgets. Revoke it and that stops.
Some URLs your agent calls keep an older
/api/supertool prefix for compatibility.
It is the same service under a previous name — nothing to configure.A free account can create one
You do not need a plan to make a key — runs are paid from your credit balance, and new accounts get a small trial credit automatically. See Pricing when you want included monthly credit.Limits
There is no per-key rate limit to configure. What decides whether the next call runs is your balance and your two caps — per call and per day — at Budgets. A call over a cap is refused before anything is sent, so it is terminal and free.Revoke a key
Delete it at agentmore.app/app/api-keys. It stops working immediately and any agent still holding it gets a401; finished runs stay
in your history. To rotate, create the new key and paste it in first, then delete
the old one.
Next
MCP server
Where the bearer token goes in a client config.
Budgets
The per-call and per-day caps that bound what a key can spend.