DOCUMENTATIONv2

GET

Explorer · contracts

Get contract explorer verify

/api/v2/explorer/contracts/{launch_uuid}/verify

AUTHENTICATIONNone · publicAUTHORITATIVE OWNERcontract-evidence-read-modelCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

Return the verification projection for contract explorer verify from the public Explorer read model, with the identifiers and verification metadata defined by the live contract.

WHEN THIS CALL IS USEFUL

Call this when an explorer, wallet, indexer, auditor, or research agent needs to verify contract explorer verify from its commitments, evidence state, or integrity metadata so it can resolve public network state from a machine-readable projection.

OUTCOME · Verify

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to verify contract explorer verify.
Keeps website presentation separate from the stable public contract that wallets, indexers, and agents can ingest.

ISOLATION + AUTHORITY

This is a public, read-only Explorer projection. It exposes only fields admitted by the live OpenAPI schema; it grants no owner, wallet, signing, settlement, publisher, matching, or trading authority. Indexed observation time is not the same as chain finality.

BEFORE YOU CALL

No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
Supply the required launch_uuid (path) exactly as defined by the live contract.
Account for projection freshness, indexing position, and chain or domain finality in the consuming decision.

WHAT TO DO NEXT

Compare the returned commitment, signer, policy, lifecycle, and freshness fields with the caller's acceptance rules.
Follow the returned canonical identifiers and proof or related-resource links when independent verification is required.

AGENT GUIDANCE

Use contract explorer verify only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required launch_uuid (path) exactly as defined by the live contract.
Treat observation timestamps, indexing position, proof state, and finality as separate facts; do not infer final settlement or authority from presence in an Explorer result.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

MACHINE CONTRACT

The exact deployed parameters, schemas, responses, security requirements, and Hybrid-Chain agent metadata are authoritative at this operation's production OpenAPI JSON Pointer. The readable tables below add integration guidance; the deployed OpenAPI controls if guidance and the machine contract ever differ.

Open the authoritative production contract ↗

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

launch_uuidpathRequired

string · 1–160Contract launch UUID or canonical slug.EXAMPLE9b51ed4c9c8f4aec85d1bd5520e40557

RESPONSES

Status and payload examples

200Recomputed launch-intent and event-chain verification.Read completed · JSON RESPONSE+

{
  "launchId": "9b51ed4c9c8f4aec85d1bd5520e40557",
  "launchIntentHash": "sha256:bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
  "launchIntentValid": true,
  "eventChainValid": true,
  "authorityBindingsComplete": true,
  "finalizedChainEvidence": false,
  "verified": true
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then compare the returned commitment, signer, policy, lifecycle, and freshness fields with the caller's acceptance rules.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.

404The public contract does not exist.Resource not visible · JSON RESPONSE+

{
  "code": "contract_not_found",
  "message": "The public contract does not exist."
}

INTEGRATION DECISIONcontract_not_found

CALLER ACTION: Verify the canonical identifier and authenticated owner boundary. A 404 may intentionally conceal a resource outside the caller's authority.
RETRY SAFETY: Do not retry the unchanged identifier repeatedly. Refresh the relevant collection or lookup before choosing another identifier.
STATE RECONCILIATION: Refresh the draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

503Verification is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "contract_registry_unavailable",
  "message": "Verification is unavailable."
}

INTEGRATION DECISIONcontract_registry_unavailable

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh the draft or launch revision, approval state, artifact commitments, authority assignments, and deployment or rejection receipt before another mutation.
ESCALATE WHEN: Escalate when revision lineage, approvals, artifact hashes, deployment authority, or finality evidence cannot be proven consistently.

OPERATIONAL NOTES

Security and lifecycle guarantees

verified confirms intent and event-chain integrity; finalizedChainEvidence separately reports on-chain finality.

DOCUMENTATION STATUS

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-09-11T06:35:11.572Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation ↗Return to the V2 directory ↗