How it works
Tools, runs, credits and your rules, in one page.
Tools
A tool is one provider's endpoint, like frankfurter#rate or openalex#works_search. Its id is provider#name. supe has 2,000+ of them: search, scraping, people and company data, email, SMS, calls, images, video, speech and more.
Every tool has:
- Tags that say what job it does, like
exchange_rateorweb_search. Tools that share a tag do similar jobs, but each takes its own parameters. - A price per call, shown before you run it. Many tools are free.
- Parameters grouped by where they go in the request:
path,queryorbody.
Your agent runs exactly the tool it picked. supe never swaps in a different one behind its back.
The loop
- Find. Search by the job in plain words:
supe find "exchange rates". Free. - Inspect. Read one tool's parameters and price:
supe inspect frankfurter#rate. Free. - Run. Call it with its parameters:
supe run frankfurter#rate --path from=EUR --path to=USD. Billed.
The answer is the provider's own response, unchanged.
Credits
Everything is priced in credits. 1,000 credits are $1. Your workspace has one prepaid balance that every agent spends from. A call's price is held while it runs and charged only if it succeeds: a call that fails costs nothing.
Runs
Every paid call belongs to a run: a budget ceiling and one receipt. A run for a single call opens on its own. For a job of many calls, open one run with a budget and bill every call to it, so a loop can't overspend. See Runs and budgets.
Your rules
Before any call runs, supe checks it against the rules you set on the dashboard:
- Limits: budgets for the workspace, an agent, a tag, a provider or one tool, by call, day, month or in total.
- Tool switches: turn off tools you don't want used, or give an agent only some tools.
- Confirmations: anything that can't be undone, like sending an email, waits for your yes. You can require Face ID for it.
- Pause: one button stops all spending.
A refused call says which rule refused it. The agent tells you, and can ask for an exception instead of working around it.
Ways in
The same tools, rules and receipts apply whichever way your agent connects: the CLI, MCP or the HTTP API.