The HTTP API
Calling the same tools from a script, without an AI client in the middle
When to use it
MCP is for an assistant working on your behalf. The HTTP API is for a scheduled job, a dashboard, or a spreadsheet — anything that wants the numbers on a timer with no model involved.
Both run the same tools through the same code. A number from the API and the same number on screen cannot disagree, because there is only one implementation of each.
Authentication
Create a key in Settings → API keys and send it on every request:
Authorization: Bearer <key>
X-API-Key: <key> also works. Keys are shown once, at creation. Give each integration its own key with the narrowest scope that does the job — a reporting script has no business holding a key that can post to Slack.
The two endpoints
GET https://app.getscorra.com/api/v1/tools list the tools this key may call POST https://app.getscorra.com/api/v1/tools/<name> call one, with its arguments as JSON
Status codes
| Code | Meaning |
|---|---|
| 400 | The arguments do not match the tool's schema |
| 401 | Missing, invalid or revoked key |
| 403 | Your plan does not include machine access |
| 404 | No such tool, or no data for what you asked |
| 500 | Our side failed — the body says what |
Rate and cost
Read calls do not consume credits. Calls that start agent work do, at the same rate as work started from the panel.