API Hub
API routes deserve their own public cluster because programmatic verification access is a real part of how CITAQ is evaluated and consumed.
This hub gathers the API-facing side of the public platform: overview routes, public verification access, trust-surface APIs, and evidence-model access surfaces that sit beside the MCP and discovery layers.
It exists to keep API-oriented discovery legible without collapsing the distinction between public trust routes, governed machine access, and operator-facing implementation detail.
It connects API docs, machine-access routes, trust-surface access, and evidence-model access patterns into one programmatic public cluster.
API Families
The API-facing routes this hub should connect
A high-level route for how programmatic access fits the larger verification system.
Public verification access routes matter because some product trust lookup paths are machine-consumed.
These routes connect public trust output to structured access patterns without blurring interpretation boundaries.
Evidence-model access routes matter where programmatic consumers need structured access to support concepts.
Priority Routes
Open the main API-facing public pages
Open the overview route for how public-facing APIs fit the system.
See the route for public verification-oriented programmatic access.
Open the route for how public trust surfaces relate to API-facing access.
Inspect the route for the structured evidence-model side of API usage.
Move into the broader machine-readable access hub beyond API-only routes.
See the platform route that frames governed programmatic access more structurally.
Connected Routes
Use the adjacent machine-access and trust hubs
Use the platform route for where agent access fits and where it stops.
Open the trust-boundary route behind API and agent-facing discovery.
See the human-readable machine-discovery route tied to public API and agent-facing access.
Use the schema route for public structured-data ownership around these API surfaces.
Browse the wider API and programmatic-access graph through the verification directory.
See the adjacent MCP-facing directory route where machine access broadens beyond APIs.
Next Step
Open machine access if you want the broader agent, MCP, and discovery layer next.
The API center is one part of the machine-readable public surface, while the machine-access hub connects APIs to MCP, schemas, feeds, and crawler-facing routes.