GET
/v1/schemas/fal/chat/openrouter%2Frouter%2Fopenai%2Fv1%2Fembeddings
Accept:
Request body
0 properties · 0 required · 0 $defsThis schema isn’t a plain object with properties — showing the raw JSON instead.
application/json
{
"provider": "fal",
"activity": "chat",
"endpointId": "openrouter/router/openai/v1/embeddings",
"kind": "input",
"contentHash": "798dad18d3fee4fc5098184eb65db8507417722108de672d1548b23702baffa2",
"specRevision": null,
"provenance": {
"sourceUrl": "https://api.fal.ai/v1/models?expand=openapi-3.0#openrouter/router/openai/v1/embeddings",
"sourceHash": "706478d9f4a1f9c8207bfd3754511aa35a294255504b1c353cf3e0cccaee7420",
"fetchedAt": 1784610160,
"extractorVersion": "1"
},
"createdAt": 1784610160,
"supersededAt": null,
"schema": {
"additionalProperties": true,
"description": "OpenAI-format request. This endpoint is an OpenAI-compatible passthrough to OpenRouter's Embeddings API: the request body follows the OpenAI Embeddings 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 except that `usage`, when returned non-null, is replaced with fal's accounting shape (`prompt_tokens`, `completion_tokens`, `total_tokens`, `cost`, `prompt_tokens_details`; fields may be null). Authoritative behavior, including which fields each model accepts, is defined by OpenRouter's implementation (https://openrouter.ai/docs/api-reference); see also the OpenAI Embeddings API reference (https://platform.openai.com/docs/api-reference/embeddings). Any field accepted there is accepted here, subject to the normalization above.",
"type": "object"
}
}Validate a payload
before you spend tokensshell
$ curl -X POST https://modelschemas.com/v1/validate \
-d '{"provider":"fal","endpointId":"openrouter/router/openai/v1/embeddings","payload":{…}}'
→ {"valid": false, "errors": [{"path": "#", "keyword": "required", …}]}