List tools
Every agent tool your key can use (web search, scrape and fetch, enrichment, SEO data), with its input and published price.
bearerAuthAuthorizationBearer <token>Your API key, sent as Authorization: Bearer <key>.
The tools.
application/json- response
object*stringdata*array<>curl -X GET "https://example.com/v1/tools" \ -H "Authorization: Bearer $OP_API_KEY"{ "object": "list", "data": [ { "id": "string", "object": "tool", "modality": "tool", "pricing": {}, "inputs": {} } ]}List tasks GET
The latest version of every task your key may call: a key may call a task only if it may use every model the task lists. Each entry carries its input and output schema and an estimated price. Accuracy targets, each a target and not a measurement: field F1 of at least 0.90 for `receipt-extract` and `entities`, and at least 0.80 for `keywords`, scored against a committed corpus of at least 50 cases per task.
MCP endpoint POST
A Model Context Protocol server that offers your key's tasks and your tenant's presets as tools. Stateless: one JSON-RPC 2.0 request or notification per POST, answered as `application/json`, with no session. Supports protocol versions 2026-07-28, 2025-11-25 and 2025-06-18. A request that carries an `Origin` header is refused with 403. A tool call is served by the task or chat route and billed as that route is. Only served where the MCP flag is on.