Future Access
Citable Infrastructure for Machines
Conceptual endpoints only. Nothing on this page is live, and no third-party integration is implied.
- GET/entity/{id}Entity Lookup
Resolve a name or identifier to an entity.
- GET/record/{record_id}Record Retrieval
Return the full Citable Record.
- GET/facts?type=serviceFact Query
Filter structured facts by type or status.
- GET/evidence/{fact_id}Evidence Retrieval
Return supporting sources for a fact.
- GET/relationships/{entity_id}Relationship Query
Traverse labeled entity relationships.
- SUB/events/record/{record_id}Change Events
Subscribe to Record change events.
- POST/answerCitable Answer
Return an answer with facts, evidence, and provenance.
Access Methods
API and MCP.
An API serves applications. MCP would serve agents, giving them Record context with evidence and provenance attached rather than loose text.
API
Programmatic retrieval of entities, facts, evidence, relationships, and change events for authorized applications.
MCP
Agent-accessible Record context. This is the direction explored by LocalWebMCP.com — the agent-access layer, not the primary product here.