The graph as linked data
Machine-readable exports of the whole knowledge graph — a single JSON document and an RDF-compatible, SPARQL-ready JSON-LD document — plus the linked-data query standards (SPARQL, GraphQL) the platform is built for.
Knowledge Graph Export (JSON-LD / RDF)
Available nowJSON-LD 1.1 / RDF
The graph as JSON-LD — an RDF-compatible, SPARQL-ready document with a resolvable @id per node and relations as predicates. The linked-data foundation the SPARQL and federation layers are built to sit on.
/data/graph.jsonld →Knowledge Graph Export (JSON)
Available nowJSON
The complete typed graph — every entity and relation — as a single JSON document, generated from the real graph. The exact bytes served back the download manifest's size and checksum.
/data/graph.json →GraphQL API
Architecture-readyGraphQL
A GraphQL surface over the same graph, letting a client request exactly the entities, fields, and relations it needs in one query. The schema maps cleanly onto the typed graph; the resolver layer is architecture-ready and not yet served.
Not yet served. The REST API delivers the same data today; the GraphQL schema and resolvers are architecture-ready.
SPARQL Endpoint
Architecture-readySPARQL 1.1
A hosted SPARQL query endpoint over the graph's RDF. The linked-data shape is live in the JSON-LD export; a queryable SPARQL service is the architecture-ready next step and is not yet hosted — no endpoint is advertised as live.
Not yet hosted. The JSON-LD/RDF export exists and can be loaded into any triple store today; a public SPARQL endpoint is architecture-ready, not live.
The JSON-LD at /data/graph.jsonld loads into any triple store today. A hosted SPARQL endpoint and a GraphQL API are architecture-ready — see the roadmap.