API V2 · Explorer

Bring public evidence
into your application.

Read the public records behind Hybrid-Chain Explorer through API V2. These endpoints require no authentication and do not change trading, settlement, custody or market state.

200Explorer contracts195implemented reads195production listed5planned compositions
INTEGRATION CONTRACT

Call https://api.hybrid-chain.com/api/v2/explorer/…. Successful responses use {"success":true,"response":…} and may include meta for pagination. Every operation page lists its exact path, query, and optional X-Request-ID header parameters. Unknown query parameters return HTTP 422 instead of being ignored. HTTP 404 means the exact public record does not exist; HTTP 503 means its authoritative read model is unavailable.

Open the authoritative OpenAPI 3.1 contract Browse every V2 operation

PAYLOAD EXAMPLES

Copyable public reads

Payloads below are illustrative, not live network measurements. Use each endpoint’s contract for its full response schema and fetch the API for current records.

DATA VAULT SUMMARY

Request and canonical envelope

GET https://api.hybrid-chain.com/api/v2/explorer/data-vault/summary
{
  "success": true,
  "response": {
    "anchors": 128,
    "evidence_records": 4096,
    "latest_anchor_at": "2026-08-23T12:00:00Z"
  }
}

DATA VAULT ANCHORS

Request and canonical envelope

GET https://api.hybrid-chain.com/api/v2/explorer/data-vault/anchors?limit=50&offset=0
{
  "success": true,
  "response": [
    {
      "uuid": "8d4f3b7f5c8a4b918ec68fe4e6884231",
      "status": "ACTIVE",
      "created": "2026-08-23T12:00:00Z"
    }
  ],
  "meta": {
    "limit": 50
  }
}

MAINNET READINESS STATUS

Request and canonical envelope

GET https://api.hybrid-chain.com/api/v2/explorer/settlements/mainnet-readiness/status
{
  "success": true,
  "response": {
    "network_id": "hybrid-mainnet",
    "ready": false,
    "decision": "HOLD",
    "evaluated_at": "2026-08-23T12:00:00Z"
  }
}

Composition recipes

Build a view from the right records.

Use the resource-level reads in each recipe to assemble a funding, settlement or asset view. The planning paths shown as references are not callable: they return HTTP 404 and are not in production OpenAPI.

  1. 01GET /api/v2/explorer/funding

    Funding evidence dashboard

    Call only the funding resources your workflow displays: operations; bindings; deposits; settlement-intents; integrity-audit; acceptance-certificates; acceptance-authorities; activation-governance; escrow-positions; and shadow-observations.

    PARAMETERS
    Pass the same limit (1–250) to bounded collections. Operations, acceptance authorities, and activation governance are singleton reads.
    JOIN + INTERPRETATION
    Join by deposit_uuid, binding_uuid, intent_uuid, position_uuid, and retained commitment fields. An unavailable optional source is unknown, not empty evidence.
  2. 02GET /api/v2/explorer/settlements

    Settlement evidence dashboard

    Compose status, evidence, operations, operations/history, archive-checkpoints, integrity-audit, quorum-canaries, authorization-activations, wallet-enrollments, wallet-activations, network-scoped faucet evidence, testnet infrastructure, synthetic assets, and funding settlement-intents.

    PARAMETERS
    Only the evidence collection accepts limit, before_sequence, network_id, address, and transaction_uuid together. Every other component declares its own narrower query contract.
    JOIN + INTERPRETATION
    Use network_id, core_sequence, bundle_uuid, transaction UUID, wallet identifiers, and evidence commitments. Operational telemetry is not settlement proof or readiness authority.
  3. 03GET /api/v2/explorer/settlements/faucet-claims/{identifier}

    Network-scoped faucet claim

    Choose /mpc-wallets/devnet-faucet/claims/{claim_identifier} or /mpc-wallets/testnet-faucet/claims/{claim_identifier}; do not probe both networks to guess ownership.

    PARAMETERS
    The claim identifier is required. Persist network_id beside it when consuming a claim-list response.
    JOIN + INTERPRETATION
    Use claim_identifier and network_id. Faucet records are test-network evidence and carry no production balance, settlement, or trading authority.
  4. 04GET /api/v2/explorer/transfers/native

    Native settlement-transfer view

    Read /funding/settlement-intents?limit={1–250}, then follow /funding/settlement-intents/{intent_identifier} when exact detail is required.

    PARAMETERS
    limit is optional. Filter locally using returned intent_type, network_id, currency, state, consent, sequence, and commitment fields.
    JOIN + INTERPRETATION
    Use intent_uuid. HTTP success means the evidence was read; only a documented terminal state and retained proof establish transfer completion.
  5. 05GET /api/v2/explorer/vault-assets/{uuid}

    Public vault asset holdings

    Start with /assets?owner_vault_uuid={uuid}&limit={1–200}&offset={n}; fetch /assets/{asset_uuid} only when holdings, supply, issuer, or proof detail is needed.

    PARAMETERS
    owner_vault_uuid is required for this recipe; limit, offset, status, and q are optional. Bound detail fan-out and preserve decimal values as strings.
    JOIN + INTERPRETATION
    Match asset.uuid to the detail path and holding.vault_uuid to the requested vault UUID. /vaults/{uuid} and its history provide vault context, not asset ownership by themselves.
Reference version and availability details

Production OpenAPI snapshot recorded 2 Oct 2026, 23:27:55 UTC. 195 Explorer contracts are implemented and 5 planned compositions remain non-executable. Check the live contract before integration.

OPERATION-BY-OPERATION DETAILS

Filter the V2 directory to chapter Explorer for all 200 contracts. Each implemented operation includes its exact accepted parameters, production response examples, status codes, authoritative owner, runtime source, and direct OpenAPI JSON Pointer.

Open the Explorer operation directory