The API

Nodes, edges, paths and subgraphs over a public HTTP API, in one vocabulary across every grain. Reads need no key, and the same surface is available to agents.

One vocabulary, every grain

A path through anatomy and a path through architecture come back in the same shape, with the same nine kinds. An agent that can read one can read all of them without learning a second schema.

Folding is explicit

A subgraph request that exceeds its cap returns truncated: true and says what it left out. A client that ignores that flag will draw a confident picture of a graph nobody chose to fold, which is a defect this codebase has already paid for once.

Evidence travels with the edge

Where a grain records why it believes an edge exists, that evidence is on the edge in the response rather than looked up separately, so a caller cannot render the claim without the reason for it.

Questions

Is there a rate limit?

Yes, the platform-wide one for anonymous reads. An API key raises it and comes with the Atlas plan.