DEVELOPERS

Market context should be read as a contract, not just a route list

API and later MCP surfaces should be explained in terms of contracts, scopes, and context packages, not only endpoint names.

Current public state

Public docs

Endpoint and access model

The current docs explain public endpoints and the access model only.

Current shell

API key and auth lane

The dashboard/auth shell exists today while the developer plane remains a next step.

Next stage

MCP-ready surface

Tool, connector, and context-package documentation belongs in the next developer lane.

User keys, org keys, and tool scopes need their own visible boundaries.

Request/response contracts, context packages, and output schemas should eventually matter more than route lists.

Longer term, this should evolve into a tool and connector catalog with explicit auth boundaries.

TODAY

Today the public site explains the current API and access model.

Context packages, artifact schemas, and scope documentation need to sit beside route docs.

LATER

A future lane can explain tool catalogs, connectors, and execution boundaries.

Developer surface	Public today	Next stage
API docs	Endpoint + access model	Contracts + schema + examples
Auth scopes	API key issuance shell	User / org / tool scope separation
MCP tools	Not public	Tool / connector catalog
Sandbox	No dedicated surface yet	Local and staging sandbox guide

The developer plane should explain contracts and boundaries, not just endpoints.
MCP remains a next-stage readiness lane rather than a current public claim.
Docs and code should share the same auth and access truth layer.