OpenAPI
REST operations, parameters, responses and errors.
Documentation
Build against explicit limits, not implied certainty
The documentation explains request schemas, response states, evidence, freshness, pagination, quotas and failure handling.
Documentation formats
Markdown
Compact machine-readable service documentation.
MCP
Streamable HTTP tool discovery and invocation.
Protocol status: ARD and A2A Agent Card are linked for discovery but deliberately return machine-readable 404 responses until implemented.
Recommended integration flow
Begin with coverage, search for an entity, inspect evidence, then use visitability or walk planning only when the task requires it. Research packs are deterministic exports rather than generated narratives.
- Use stable IDs from search results; do not derive IDs from display names.
- Treat complete, partial and unknown as domain states.
- Keep source review age separate from HTTP cache age.
- Restart pagination when a cursor reports a dataset-version conflict.
Errors remain actionable
Syntax, semantic validation, authentication, authorization, missing entities, conflicts, size limits, quotas and dependency failures use distinct HTTP statuses and stable error codes.
No external actions in the first release
The six public tools read published records or compute a result from them. They do not make purchases, alter third-party systems or trigger paid upstream services.