Open Astronomy Platform
The whole knowledge graph, open. A read-only public API, machine-readable exports in JSON and RDF-compatible JSON-LD, bulk downloads with verifiable checksums, and clear licensing — live today. The standards a research platform is measured by — SPARQL, GraphQL, SDKs, DOI releases, Virtual-Observatory interoperability — are here too, described honestly as architecture-ready, never faked.
Available now
Working today over the real graph — each with a live endpoint or export.
Bulk Downloads
Available nowSHA-256 checksummed
The full graph exports offered as bulk downloads, each with a REAL byte size and SHA-256 checksum computed from the exact bytes served, plus its licence and release. No download is fabricated — the checksum can be verified against the file.
Open →Citation Export
Available nowAPA · BibTeX · RIS
The real, source-backed citations behind entities, served as an API and exportable in APA, Chicago, MLA, Harvard, BibTeX, and RIS through the platform's citation engine. Every field comes from a verifiable citation record; none is invented.
/api/v0/citations →Dataset Exports
Available nowJSON · CSV
Every curated dataset — from named stars to live-provider status to 3D scenes — exportable as JSON and CSV with real record counts, licences, and provenance. A focused slice of the graph for a specific need.
/api/v0/datasets →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 →Licensing Matrix
Available nowCC BY-SA 4.0 + per-source
A clear matrix of the licences that apply — the platform's own CC BY-SA 4.0 for the graph and API, and the individual terms of each upstream source (NASA, ESA, IAU, and the rest) — so reuse obligations are never in doubt.
Open →Neighbours & Evidence Paths
Available nowREST / JSON
The graph query surface: breadth-first neighbourhood traversal and shortest evidence paths between two entities, cycle-safe and bounded. The same real algorithms behind the graph explorer and the grounded assistant, exposed as an API.
/api/v0/traversal →OpenAPI Specification
Available nowOpenAPI 3.1
A machine-readable OpenAPI 3.1 description of every implemented endpoint, generated from the endpoint registry — so a client, a code generator, or an agent can discover the API automatically.
/api/v0/openapi.json →Public Graph API
Available nowREST / JSON
A read-only, deterministic REST API over the whole knowledge graph — list and fetch entities, list relationships, search, and traverse neighbourhoods and shortest paths. Every response carries a provenance envelope (version, source, licence, attribution). No auth, no rate limits, no write endpoints.
/api/v0/entities →Sources API
Available nowREST / JSON
The registry of authoritative sources behind the platform — every source's name, organisation, canonical URL, licence, and scope — served as a public endpoint, so the provenance of any cited fact can be resolved programmatically.
/api/v0/sources →Versioned Releases
Available nowSemVer (graph & schema)
The graph and its schema carry versions, surfaced in every API response's provenance envelope, in the OpenAPI description, and on every export — so a consumer can pin a release and know when entities or the schema change.
/api/v0/openapi.json →
Architecture-ready
The roadmap →Defined interfaces built on the live data, not yet hosted — and honest about it. No fabricated endpoints.
DOI-Minted Releases
Architecture-readyDataCite DOI
Citable, DOI-minted snapshots of the graph, so a specific release can be referenced in the literature. The versioning and checksummed exports that a DOI release needs are live; minting DOIs through a registration agency is architecture-ready.
No DOI is minted yet. Versioned, checksummed releases exist; DOI registration via a DataCite member is architecture-ready, not done.
Federation-Ready Metadata
Architecture-readyLinked-data IRIs
Every entity already carries a resolvable IRI in the JSON-LD export, the foundation for federating the graph with other linked-data sources. A published federation manifest and cross-dataset link set are architecture-ready.
Resolvable IRIs exist in the JSON-LD; a formal federation manifest and external owl:sameAs link set are architecture-ready, not yet published.
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.
JavaScript / TypeScript SDK
Architecture-readyJS / TS client
A typed JavaScript/TypeScript client over the public API, for the browser or Node. As with the Python SDK, the OpenAPI description makes a client generatable today; a curated, published package is architecture-ready.
No package is published yet. Client generation from the OpenAPI spec works now; a curated JS/TS SDK is architecture-ready.
Python SDK
Architecture-readyPython client
A Python client over the public API — typed models for entities and relations, and helpers for search, traversal, and export. The API and its OpenAPI description are live, so a client can be generated today; a curated, published package is architecture-ready.
No package is published yet. The OpenAPI 3.1 spec supports client generation now; a curated Python SDK is 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.
Virtual Observatory (TAP / ADQL)
Architecture-readyIVOA TAP / ADQL
An interface prepared for the International Virtual Observatory Alliance protocols — a TAP service answering ADQL queries over the tabular catalogues (stars, deep-sky, exoplanets). The catalogues carry the real measured columns; a TAP/ADQL service over them is architecture-ready.
No TAP service is hosted. The catalogues hold the real columns (RA/Dec, magnitudes, distances); a TAP/ADQL endpoint is architecture-ready, not live.
For developers
Start at the platform overview for developers, browse the OpenAPI 3.1 spec, or pull the whole graph from /data/graph.json. Every API response carries a provenance envelope; the graph and API are licensed CC BY-SA 4.0.