Resources
Everything written down, in one place
How the product works, how to go live, the API that reads it, and what to do when something goes wrong — it all lives at docs.prepaid.ai. This page is the map.
Where to look first
Guides
Walkthroughs for the paths people actually take: building your AI from your website, going live, teaching it who your regulars are, and hearing about calls the moment they end.
API reference
Four REST endpoints over the same workspace your console reads — balance, agents, numbers, calls — behind a bearer key you mint in Settings. Money arrives as integer credit-hundredths, because that is how it is stored: 100 is one dollar, and nothing is ever a float.
MCP server
If your AI assistant speaks the Model Context Protocol — Claude and Cursor do — it can read your workspace directly, with the same key the REST API uses. All four tools are read-only by decision: nothing inside an AI session can spend credits or change what your number says to callers.
Knowledge base
Answers to the things that go wrong, in the order the checks matter: what to look at when a number stops answering, what a hold in your ledger means, and why the browser demo is almost always a microphone permission.
Platform status
Live checks on the services underneath the product — the database, the carrier, the voice engine, payments — measured when the page loads, never asserted. If you are diagnosing something odd, start there: it says whether the problem is ours before you spend an hour proving it is not yours.
Countries and verification
Where your number can be, and what it takes. Numbers are instant in the United States and Canada; New Zealand, Australia and the United Kingdom need identity checks the carrier asks for first. You are told which the moment you choose a country, and the exact document list is waiting in your console before you pay a cent.
The longer answers
The short versions live on the home page. These are the ones with the mechanism in them — and if yours is not here, ask a human.
Why does my ledger show a hold instead of a charge?
Because the call reserved money before it spent any. When a call starts, a few minutes of credit are held so a conversation can never run past what you have; when it ends, the unused part of the hold comes back. Those are the two rows a call leaves in your ledger — credits held, then the hold returned — and what the call cost is the difference between them, with the running balance beside each row as the authoritative figure. A hold with no return yet is usually a call still in progress — not money gone.
My ledger shows a hold, not a charge →What happens to my number if I forget to recharge?
A plan is a validity window, like a prepaid SIM, and it lapses the same way. Your number is not taken back the moment the plan ends — there is a grace period first, and recharging inside it keeps everything: the number, the agent answering it, and any top-up credit, which rolls over for as long as a plan is active. Only after the grace period runs out is the number released.
Keeping your number →Will callers know they are talking to an AI?
Yes. It says so at the start of every call, by default, in the wording each country expects. In a growing number of jurisdictions that sentence is the law; everywhere else it is simply the honest way to answer a phone. A caller who finds out afterwards is the one who stops trusting the business — the disclosure exists so that moment never happens.
AI disclosure and recording →Do I need to be a developer to use any of this?
No. The console does everything on its own. The API and MCP server exist for teams that want their own tooling to read the same facts — balance, agents, numbers, calls — with a key created in Settings and shown exactly once, because only a hash of it is stored. Lose it and you mint another; nobody can read it back, including us.
Authentication →Can an AI assistant connected over MCP change my agent?
No, and not by omission. All four tools are read-only, so an assistant can tell you your balance or list your recent calls, but nothing reachable from inside an AI session can publish an agent, spend credits, or change what a real phone number says to real callers. Changes like that belong on a screen where a person confirms them.
MCP server →My number stopped answering — where do I start?
With three checks, in order. Is the agent published? A draft answers nothing. Is an agent actually attached to the number? With several agents and no default set, nothing is attached automatically — you pick one on the Numbers screen. And is the plan still holding the number? A plan in grace keeps the number and the line keeps answering; only a released number is really gone, so recharge inside grace and everything stays.
My number is not answering →Written down before you needed it
The quickstart takes a website address to an AI you can talk to, in about three minutes.