Create Response
Responses
Create Response
Responses API endpoint — provider resolved dynamically from DB.
Auth: Authorization: Bearer rsk_<ULID>
Streaming: set stream=true for SSE chunks
Rate limits: RPM and RPD enforced per key via Redis fixed-window counters
Spend cap: enforced if key.spend_cap_usd is set
Provider: resolved from model_pricing.provider (same as chat/completions)
POST
Create Response
Authorizations
Enter your MeshAPI key (rsk_...) — sent as Authorization: Bearer <key>.
Body
application/json
Required range:
x >= 1Required range:
0 <= x <= 2Required range:
0 <= 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
Maximum string length:
256Required range:
1 <= x <= 10Required range:
x > 0Response
Completed response (JSON), a queued background job when background=true, or an SSE stream when stream=true