Create Response
Authorizations
Enter your MeshAPI key (rsk_...) or, for the admin-keys endpoints, a dashboard session token — sent as Authorization: Bearer <token>.
Headers
Dated version of the API contract to pin this request to. Omit it and the request is served under 2026-08 — the oldest supported version, so an existing integration is never moved by a release. A malformed or unsupported value is rejected with 400 invalid_api_version rather than falling back silently. The version actually served is echoed as X-Mesh-Version on every response, including errors.
2026-08, 2026-09 Body
auto, default, flex x >= 10 <= x <= 20 <= x <= 1Custom function tool in the Responses API flat format.
The Responses API uses a flat structure (name/description/parameters at top level) unlike Chat Completions which nests them under a "function" key:
Responses API: {"type": "function", "name": "add", "parameters": {...}} Chat Completions: {"type": "function", "function": {"name": "add", ...}}
- ResponsesFunctionTool
- BuiltinTool
A stable, anonymised identifier for the end user making this request, recorded on the usage row and available as a filter and a group-by dimension in the usage API. Supersedes the deprecated user field. Use an opaque id, not an email address or a name.
2562561 <= x <= 10x > 0Your own labels for this request, echoed back on the usage row and available as a filter and a group-by dimension in the usage API. String keys to string values. Never put personal or sensitive data here — tags are stored with the usage record and are not redacted.
Response
Completed response (JSON), a queued background job when background=true, or an SSE stream when stream=true