ONCHAIN STATE. OFFCHAIN EVIDENCE. ONE CLEAR VIEW.Frontend preview
Documentation /

API reference

Full reconciliation and lightweight protocol status endpoints.

Availability

These endpoints are specified interfaces, not live endpoints on this website. The frontend never fabricates an API response when the service is absent. Backend deployment and evidence ingestion remain pending.

Source: Frontend deployment boundary

Comprehensive reconciliation

GET /v1/rwa/{address}/reconcile

Returns complete state verification and evidence context. The following JSON is reproduced from the source specification as documentation only. Its timestamps, quantities and block number are examples, not current observations.

The literal mixed-case asset address in this example fails EIP-55 checksum validation. It is preserved exactly as supplied, not silently repaired. Replace it with an independently validated token address when using a real API.

Documentation example
{
  "asset": "0x3b8909d7350711A72147311B9036aE102f43A910",
  "chainId": 46630,
  "status": "SAFE",
  "reconciliation": {
    "totalSupply": "10000000.00",
    "verifiedReserves": "10000000.00",
    "collateralRatio": "1.00",
    "reserveDeficit": false
  },
  "checks": {
    "contract": {
      "status": "healthy"
    },
    "proofOfReserve": {
      "status": "healthy",
      "lastAttestation": 1750000000
    },
    "navOracle": {
      "status": "healthy",
      "lastUpdate": 1750000000
    },
    "sequencer": {
      "status": "healthy"
    },
    "lifecycle": {
      "status": "active"
    },
    "permissions": {
      "status": "verified"
    }
  },
  "warnings": [],
  "checkedAt": 1750000010,
  "blockNumber": 1234567
}

Source: PDF p3 §7A; checksum verified with viem

Lightweight status

GET /v1/rwa/{address}/reconcile/status

Designed for wallet UI and protocol middleware. This is the literal example shape, not a live result.

Documentation example
{
  "status": "SAFE",
  "collateralRatio": "1.00",
  "checkedAt": 1750000010
}

Source: PDF p3 §7B

Integration requirements still to finalize

  • Authentication, rate limiting, request timeouts and error response schemas.
  • Supported-asset registry, token/reserve unit normalization and contract adapters.
  • The complete evidence/provenance payload required by §9.
  • Status expiry, observation consistency, complete rule precedence and missing-data policies.

Source: API details not specified in PDF; proposed implementation requirements