Research Discovery API

Public, read-only JSON resources. No authentication or API key is required.

• GET /api/v1/manifest.json: index URL, SHA-256 and release coordinate.
• GET /api/v1/index.json: searchable records and sourced, typed relationships.
• GET /api/v1/oeis/A010060.json: exact OEIS lookup, connected records and scope.
• GET /api/v1/records/{sha256-of-UTF8-record-id}.json: record, neighbors and incident edges.

OpenAPI 3.1 specification

Search the downloaded index by title, aliases, identifiers and summary. Query parameters do not filter these static endpoints. Unknown identifiers return HTTP 404, which means not indexed, not unsolved. Follow record URLs for human-readable results.

Research paths expose public_problem, general_theorem, representation, new_problem and human_understanding stages. Check each stage status: a worked example does not establish independent understanding; a proposed transfer does not establish measured benefit. For a future measured-transfer claim, require a fixed held-out target set, baseline and bridge-enabled runs under the same budget, an ablation, raw outcomes and a versioned evaluation report tied to the exact representation proof. Independent understanding requires a separate reader task and assessment record. Missing evidence remains missing. Literature records retain DOI/arXiv identity and author attribution. Citation and acknowledgement edges are source-authored, not extracted theorem-use dependencies.

Only result records carry reviewed proved/refuted status. Sequence associations, topic membership, proposed bridges and source anchors never propagate that status. Module membership does not certify every declaration. Source commits and release membership are separate. This curated index is not an exhaustive literature review or an extracted Lean theorem-use graph.

Read the manifest, fetch the index and check its SHA-256. Retry if deployment changes cause a mismatch. Record responses identify their index snapshot. These immutable IDs can be used to join data across releases; retain snapshots in your own client for history.