Open data contract

Every public claim should be queryable.

The preview exposes normalized profiles, complete representative run receipts, and an explicit scorecard schema through read-only JSON endpoints.

GET /api/assistants

Profiles, axis metrics, coverage, readiness, and evidence eligibility.

GET /api/runs/{runId}

One inspectable receipt with trace, state diff, assertions, and provenance.

GET /api/scorecard?assistant=harbor

Protocol metadata, gates, eligibility, and a labeled pooled demo reliability surrogate.

Profile export

Eligibility is data, not decoration.

Public ranking remains disabled for this synthetic preview even where a fictional profile technically meets protocol eligibility.

Demonstration assistant evidence status
ProfileConfigurationCoverageRepeatsHard gateProtocol status
Harbor2.4.1 · Web · iOS10/105 minimumNoneRank-eligible
Northstar1.9.0 · Web · SMS9/105 minimumNoneProvisional
Threadline4.2.2 · Web · Android · iOS9/105 minimumNoneProvisional
Hearth3.0.6 · iOS · Android8/105 minimumNoneProvisional
Localis0.8.4 · macOS · Windows · Linux7/104 minimumNoneDiagnostic only
Relay5.1.0 · Web · SMS10/105 minimumUnresolvedDiagnostic only

Harbor

Configuration
2.4.1 · Web · iOS
Coverage
10/10
Hard gate
None
Status
Rank-eligible

Northstar

Configuration
1.9.0 · Web · SMS
Coverage
9/10
Hard gate
None
Status
Provisional

Threadline

Configuration
4.2.2 · Web · Android · iOS
Coverage
9/10
Hard gate
None
Status
Provisional

Hearth

Configuration
3.0.6 · iOS · Android
Coverage
8/10
Hard gate
None
Status
Provisional

Localis

Configuration
0.8.4 · macOS · Windows · Linux
Coverage
7/10
Hard gate
None
Status
Diagnostic only

Relay

Configuration
5.1.0 · Web · SMS
Coverage
10/10
Hard gate
Unresolved
Status
Diagnostic only

Evidence labels are not interchangeable.

Controlled means an instrumented scenario execution. Field means consented real use. Source-only is a product claim or documentation observation. Only compatible controlled evidence feeds a comparative score.

Schema stability

Breaking changes will create a versioned route. Additive fields may land within v1; consumers should ignore unknown keys and use the top-level schemaVersion.