GET

/v1/schemas/fal/chat/openrouter/router/openai/v1/responses?kind=output

Accept:

kind outputactivity chathash 1c61d852…extracted Oct 31, 2026version currentsource upstream spec ↗

field	recorded source
schema	Source linked above. upstream-spec Source trace `adabed3ca9da049e03965d9c70135a587abe1a4565c9869100bae54280af9158` { "fetchedAt": 1793422802, "extractorVersion": "1", "verifiedAt": null }

Response body

0 properties · 0 required · 0 $defs

This schema isn’t a plain object with properties — showing the raw JSON instead.

application/json

{
  "provider": "fal",
  "activity": "chat",
  "endpointId": "openrouter/router/openai/v1/responses",
  "kind": "output",
  "contentHash": "1c61d85213a0378310eed0e80ce30ee0b31ced2c51217877a968516587c46a18",
  "specRevision": null,
  "provenance": {
    "sourceUrl": "https://api.fal.ai/v1/models?expand=openapi-3.0#openrouter/router/openai/v1/responses",
    "sourceHash": "adabed3ca9da049e03965d9c70135a587abe1a4565c9869100bae54280af9158",
    "fetchedAt": 1793422802,
    "extractorVersion": "1",
    "derivation": "upstream-spec",
    "verifiedAt": null
  },
  "createdAt": 1793422802,
  "supersededAt": null,
  "schema": {
    "additionalProperties": true,
    "type": "object",
    "description": "OpenAI-format response. This endpoint is an OpenAI-compatible passthrough to OpenRouter's Responses API: the request body follows the OpenAI Responses wire format and is forwarded with minimal normalization (usage accounting is enabled, and when a fal caller id is available, a privacy-preserving hash of it replaces any caller-supplied `user`); the response follows the OpenAI wire format, including the Responses API `usage` token fields (`input_tokens`, `input_tokens_details`, `output_tokens`, `output_tokens_details`, `total_tokens`) plus `cost`, the USD cost used for fal billing; other upstream `usage` fields are not returned. When `stream` is true on a synchronous invocation, the response is delivered as server-sent events instead of a single JSON object. Authoritative behavior, including which fields each model accepts, is defined by OpenRouter's implementation (https://openrouter.ai/docs/api-reference); see also the OpenAI Responses API reference (https://platform.openai.com/docs/api-reference/responses)."
  }
}

Validate a payload

before you spend tokens

shell

$ curl -X POST https://modelschemas.com/v1/validate \
    -d '{"provider":"fal","endpointId":"openrouter/router/openai/v1/responses","payload":{…}}'
→ {"valid": false, "errors": [{"path": "#", "keyword": "required", …}]}