Interface · v1

Knowledge API

What this is

One stable programmatic entry into the OCOM canonical model. Assistants, dashboards and agents read knowledge here, resolved, explained and graph-linked, instead of scraping HTML or search indexes.

This API is a publication interface of ocom.uno, not part of the OCOM model. The specification defines no API, database or technology (Core/Manifest.md, Scope); an implementation of OCOM is not required to expose these endpoints.

Endpoints (v1)

MethodPathReturns
GET/api/v1API manifest (version, endpoints, operations)
GET/api/v1/termsAll Core Vocabulary terms
GET/api/v1/term/{slug}Full knowledge record for one term
GET/api/v1/resolve/{id}Resolve a URI, Definition ID, Doc ID, Specification chapter ID or Comparison ID
GET/explain/{id}Explain a resolution: why, canonical URI, related, evidence. Term identifiers only (URI, Definition ID, Doc ID)
GET/api/v1/neighbors/{slug}Graph neighbors (depth 1 + depth 2 + backlinks)
GET/api/v1/graphThe knowledge graph
GET/api/v1/governanceGovernance candidates

Example

GET /api/v1/term/object → the Object knowledge record. GET /explain/OCOM-DEF-0012 → why OCOM-DEF-0012 resolves to Ownership. GET /api/v1/neighbors/object → Object's graph neighbors to depth 2.

Every endpoint is a deterministic, cacheable rendering of the canonical model. Extensionless paths resolve to JSON. A dynamic POST /api/query can be layered on later without changing these URLs.