Developer API
Call every tool and every data source from your own system with an API key, charged exactly as on the web.
The API has no price of its own: each call costs the credits of the tool it runs, exactly as if you had clicked run on the web. Credits are deducted before the system fetches anything, and if nothing usable comes back a reversing entry is written to the ledger.
Two things to read before your first line of code. First, slow tools return an accepted status with a run identifier rather than the result, so your loop has to handle both cases. Second, always send an Idempotency-Key from the very first call — if the network fails between request and response, resending the same key returns the earlier result and does not charge again.
What you put in
- An API key created in the app.
- The tool code and its parameters, the same ones as on the web.
- A self-generated Idempotency-Key, so retries are safe.
What you get back
- The result as JSON, the same data as the web version.
- For background tools: a run identifier to read the result later.
- The credits charged for that run.
The limit on one run
- No price of its own: each call costs the price of the tool it runs. Do not hard-code that number in your code, because an administrator can change it.
- Each tool's per-run limit is identical to the web version. There is no unlimited plan.
- There is a limit on calls per minute. Space your schedule out rather than firing in bursts.
What this tool does not do
- No endpoint returns email addresses, personal phone numbers, or a list of people to contact.
- No shortcuts: there is no way to run a tool without going through that tool's own runner.
- An account that has submitted a data block request is refused before credits are charged, over the API as over the web.
Frequently asked questions
Every figure here is an estimate from what the platform displays publicly. It is not a channel's or a marketplace's internal analytics, and it is not audited.