API

A public, authenticated HTTP API is on the roadmap but not shipped yet. The internal endpoints under /api/* are not considered stable.

Why no public API yet

We want to ship sane primitives — auth keys, per-key budgets, usage dashboards, version pinning — before opening the door. Releasing the internal route shapes prematurely would lock us in.

What it will cover at v1

• Search — paper and book lookup with the same ranking the UI uses.
• Analyze — get the AI synthesis (or a cached one) for any work id.
• Ask — single-turn or multi-turn Q+A about a work.
• Compare — side-by-side comparison of 2–3 works.
• Citations — programmatic access to the citation graph data.

Want early access?

Email us. We'll prioritise integrations that have a clear use case (research tools, university systems, publishing workflows).