Developer surface

Integration surfaces remain status-labeled.

Loquitur is shaped as API/SDK-first verification middleware, but public developer wording stays conservative: preview, candidate, private preview or sandbox. Nothing on this page should be read as a stable public API or production package claim.

Read developer docsView registry preview
sanitized preview objectJSON
1{2  "object_type": "registry_entry",3  "registry_entry_id": "re_••••",4  "receipt_id": "rcpt_••••",5  "issuer_id": "iss_••••",6  "manifest_hash": "sha256:••••",7  "receipt_hash": "sha256:••••",8  "policy_id": "policy.rwa.review",9  "verdict": "pass",10  "reason_codes": ["INTEGRITY_OK", "AUTHORIZATION_VERIFIED"],11  "anchor": null12}

Surface ledger

Limits travel with the surface.

Developer artifacts are preview/candidate materials for integration review. They are not SLA-backed endpoints, externally audited packages or stable public contracts.

boundary

Not a hosted production API, stable public API or SLA-backed endpoint.

Reference OpenAPI. PREVIEW. Reviewable implementation-preview artifact for API-first discussion and internal contract alignment. Not a hosted production API, stable public API or SLA-backed endpoint.
boundary

Not an externally ratified standard or stable public contract.

Schemas package. CANDIDATE. Candidate schema surfaces for bundle, receipt, summary, registry-entry and trust-registry shapes. Not an externally ratified standard or stable public contract.
boundary

No inclusion proof (L4) and no anchor finality (L5). The trust-registry root signature is not verified; no production trust root is pinned.

Offline verifier. CANDIDATE. Verifies bundle structure (L0), file and manifest integrity (L1), the bundle-to-registry-entry link (L2) and issuer authorization against a trust registry (L3). An executed conformance gate holds the Python and TypeScript implementations in agreement on L0 and L1 and on schema contract; it does not yet exercise L2 or L3, because its bundle cases carry no registry entry and no trust registry. No inclusion proof (L4) and no anchor finality (L5). The trust-registry root signature is not verified; no production trust root is pinned.
boundary

No stable public npm package or partner-ready SDK claim.

TypeScript SDK. PRIVATE PREVIEW. Private preview wrapper and generation proof used for integration narrative and future hardening. No stable public npm package or partner-ready SDK claim.

Integration posture

Disclosure comes before developer marketing.

1.Status labels travel with every surface.

2.Private evidence is not exposed through public registry-preview routes.

3.Verifier claims remain scoped until release gates prove higher levels.

4.Integration review starts from policy, evidence and disclosure boundaries, not generic API marketing.

Docs bridge

Docs before endpoints.

The docs surface should orient engineers around identity, architecture, registry commitments and verification limits before any generated client or endpoint list is treated as stable.

Open developer docs
1

Use the docs subpage to orient engineers before discussing endpoints or generated clients.

2

Keep protocol identity, two-layer architecture, registry-entry boundaries and verification modes visible during integration review.

3

Treat the docs surface as a public-safe bridge, not as an API reference, production portal or partner handoff.

Readiness checks

Integration readiness is a set of gates.

The developer surface is useful only when contract, verification and SDK posture remain explicitly bounded.

Contract discipline

Do not infer a stable public API from the OpenAPI preview material.

Contract discipline. Surface first, endpoint second.. Developer review starts from object boundaries: bundle, receipt, summary, registry entry and trust-registry shapes. Do not infer a stable public API from the OpenAPI preview material.
Verification discipline

Do not claim L4/L5 verification, live anchoring, issuer legal identity verification or production trust roots.

Verification discipline. Local replay before network trust.. Verifier language should distinguish local integrity and receipt replay from future registry-link, signature and anchor checks. Do not claim L4/L5 verification, live anchoring, issuer legal identity verification or production trust roots.
SDK discipline

No public npm release, partner-ready SDK or stable generated client claim.

SDK discipline. Preview wrappers are not public contracts.. The TypeScript SDK surface may help integration review, but it remains private preview until package, docs and compatibility gates are complete. No public npm release, partner-ready SDK or stable generated client claim.