Machine Access Hub
CITAQ is not only a human-facing trust system. It also needs clear, bounded routes for agents, crawlers, and machine-readable discovery.
This hub gathers the public routes that explain how machine consumers reach CITAQ, what they can inspect, where boundaries apply, and how discovery surfaces like `llms.txt`, schemas, feeds, and route-level documentation fit together.
The architecture source treats agent access, MCP, authentication floors, and public route discovery as real product concerns. They need their own public cluster rather than being hidden inside generic API copy.
It connects MCP, crawler access, public APIs, discovery manifests, and route-level documentation into one inspectable system.
Core Access Layers
The machine-readable families this hub should connect
The MCP layer explains how structured product and verification access is exposed to compatible machine consumers.
Machine-facing routes need a clear distinction between callable operations and read-oriented structured materials.
Agent access routes explain where public machine access begins and where stronger boundaries still apply.
Programmatic access needs a public story that stays separate from generic trust messaging and private internal access.
Crawlers and answer engines need route-level discovery support without dissolving trust boundaries or access control language.
Files and routes like llms.txt, schema indexes, and feeds help machine discovery stay organized across a large public graph.
Priority Routes
Open the main machine-access pages
See how structured machine access is framed inside the platform model.
Open the route that separates callable machine actions from the rest of the public site.
Inspect the read-oriented structured materials that agents can consume from CITAQ.
See where public machine access fits into the larger verification system and where it stops.
Open the route that separates public trust output from governed programmatic access.
Inspect the trust-boundary side of how machine consumers reach public routes.
Discovery Surfaces
Use the machine-readable and docs routes around this cluster
Use the documentation route for the broader MCP framing behind this public hub.
Open the docs route for how public access is framed within the MCP family.
Inspect the access-boundary documentation for how machine access stays governed.
Use the public LLM-facing route to understand the machine-readable discovery layer.
Open the route-level schema index that supports machine-readable discovery across the public graph.
Move into the API-facing public hub for verification access, trust-surface APIs, and evidence-model routes.
See the feed-discovery route that helps machine consumers find changing public content families.
Why This Exists
Machine access needs a visible public route cluster
The architecture positions MCP and structured machine access as a real operating surface, not a future optional add-on.
Files like llms.txt help, but the surrounding public routes still need accessible explanations, boundaries, and onward paths.
Machine-readable access should be discoverable without blurring the distinction between public trust routes and controlled programmatic access.
Next Step
Open the verification directory if you want the broader indexed route graph around machine access.
Machine access is one cluster inside a larger public system that also includes trust, standards, evidence, resources, and docs.