Skip to main content
Prefix: /v1/developer/tool-runs. Reads need tools:read; execution needs tools:run and eligible credit.

Discovery

q is 1–200 characters, limit is 1–100, and cursor is an opaque value up to 4096 characters. The response contains tools and optional cursor/total. Each entry identifies provider and endpoint. Retain identifiers exactly as returned. Inspect before execution:
Inspection reads schemas; it does not run the tool. Check required fields, route parameters, input types, pricing metadata and output shape.

Create

The example body is appropriate only for a tool whose schema defines query. The input envelope supports body, queryParams and pathParams as JSON records. The request input is bounded to 16 KiB. Do not flatten all fields or send credentials inside a generated tool payload. Save the creation key before submission. A 202 result means the request was accepted, not that the upstream completed.

Results and refresh

Read the returned state, output and receipt fields. Some tools complete immediately; others return an upstream job requiring refresh. Refresh the existing run ID; it must not be replaced by another create call. Pending receipts are not final. Completed receipts record actual settled cost and applicable discounts/fees. Failed execution remains failed. Earlier successful work in a multi-step agent remains billable if another step fails. Treat tool output, embedded URLs and retrieved pages as untrusted data. Media may be exposed as URLs, structured fields or text depending on the tool. See media handling for display and retention boundaries. Tool discovery is a catalog, not a guarantee that every provider currently has capacity or accepts every input.