DEVELOPERS / DATA PLATFORM
Build on evidence, not ticker guesses
Public machine interfaces for canonical identity, observable state, and reproducible evidence.
MACHINE DELIVERY
Choose the public legacy interface that fits the workflow
Use the existing REST API, exports, RSS feed, read-only MCP catalog, or pinned legacy SDK v0.1 packages. Data Platform v2 contracts, streams, SDK v0.2 registries, MCP v2, semantic discovery, and Stories remain repository-only and are not publicly promoted.
Use the legacy API reference for cacheable JSON, feeds, and exact request contracts.
Use current production exports and their manifests for reproducible research workflows.
Use the separate setup truth page for the public legacy read-only MCP boundary.
TECHNICAL ≠ PRODUCTION
Delivery status by surface
A repository contract, passing offline gate, or vendored client is not a public deployment. Only the legacy production row below is publicly promoted.
| SURFACE | TECHNICAL STATUS | PRODUCTION STATUS | BOUNDARY |
|---|---|---|---|
| Legacy REST, OpenAPI, exports, feeds, and read-only MCP | IMPLEMENTED | PUBLIC LEGACY | These existing production surfaces remain the only public integration contract. |
| API v2, event streams, SSE, and webhooks | REPOSITORY CONTRACTS | NOT PROMOTED | Repository contracts and offline validation do not make a public route or subscription service. |
| JavaScript and Python SDK v0.2 | VENDORED / OFFLINE | LEGACY v0.1 LIVE / v0.2 NOT RELEASED | Legacy @chain4663/client 0.1.x and chain4663 0.1.0 packages are published. SDK v0.2 remains repository and offline-kit only. |
| MCP v2, semantic discovery, and Stories/exports beta | REPOSITORY / DORMANT | NOT PROMOTED | No public catalog, semantic endpoint, story route, renderer claim, or production compatibility is asserted. |
SDK distribution status
JavaScript and Python SDK v0.2 sources are vendored for repository and offline integration-kit use; v0.2 is not published to a registry.
V0.1 PACKAGES ARE LIVE. npm provides @chain4663/client 0.1.x and PyPI provides chain4663 0.1.0.
npm i @chain4663/client@0.1.1 or pip install chain4663==0.1.0. Use the checked-out repository or checksum-verified copied kit for v0.2.
FIVE-STEP LEGACY JOURNEY
Verify, fetch, subscribe, verify evidence, reproduce
This journey names only public legacy routes. Repository-only Data Platform v2 work is intentionally excluded from public instructions.
- VERIFYResolve an exact Chain 4663 contract and inspect its authority evidence; never substitute a ticker.
- FETCHRead the documented legacy v1 JSON, OpenAPI, feed, or bounded export surface.
- SUBSCRIBEUse the production RSS feed. API v2 streams, SSE, and webhooks are not public subscription paths.
- VERIFY EVIDENCEInspect source, block or timestamp, methodology, and publication evidence before relying on a value.
- REPRODUCEReplay the current export against its archive manifest, or use the repository-only offline integration kit.