x-route-source

`x-route-source` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `app/api/v1/agents/[agentId]/mcp/route.ts`, `app/api/v1/agents/[agentId]/pins/route.ts`, `app/api/v1/chat-sessions/[sessionId]/route.ts`, `app/api/v1/workspaces/[workspaceId]/pins/route.ts`. Consistent with runtime & gateway — this is inferred from where the key appears and what it carries, not from any published definition.

Runtime & gateway derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
153 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 153

What its value looks like

Value shapeOccurrences
string153

Observed values

Sampled from the specifications, most frequent first.

app/api/v1/agents/[agentId]/mcp/route.tsapp/api/v1/agents/[agentId]/pins/route.tsapp/api/v1/chat-sessions/[sessionId]/route.tsapp/api/v1/workspaces/[workspaceId]/pins/route.tsapp/api/v1/agent-schedules/[scheduleId]/route.tsapp/api/v1/agents/[agentId]/route.tsapp/api/v1/agents/[agentId]/memories/route.tsapp/api/v1/automations/[automationId]/route.ts

Providers publishing it

All 1.

dokki-one

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the runtime & gateway job.