Operation contractscrypto.wallet.report search.web search.answer ai.execute sandbox.run prediction.markets prediction.market prediction.compare prediction.history prediction.signal crypto.wallet.balances crypto.wallet.tokens crypto.wallet.transactions

Catalog/Crypto Intelligence/crypto.wallet.report

Operation contract · canonical identity

Derive wallet intelligence

Derive one bounded multichain wallet report with holdings, activity, flows, counterparties, deterministic signals, coverage, freshness, and provenance.

crypto.wallet.report

PreviewNo operation-specific incident feed is boundNot bound in public operation truthcontract 2026-07-29.1

Review execution states Inspect contract

FamilyCrypto Intelligence

Family probelive

Quotefixed by operation

NetworkNot bound at operation level

Proofquote observed, unpaid

Observed2026-08-11T08:48:34.576Z

01 · What it does

The callable contract for this task.

Human meaning and machine truth stay together. Anything not bound by current canonical artifacts remains explicitly unavailable rather than filled from the design fixture.

Derive wallet intelligence

Derive one bounded multichain wallet report with holdings, activity, flows, counterparties, deterministic signals, coverage, freshness, and provenance.

Canonical operation ID · crypto.wallet.report

Current access · Publicly callable preview

Public route · /v1/crypto/execute

Boundary

Unknown fields stay unknown.

Action class, operation-specific health, latency, provider identity, and history are not inferred from family or fixture copy when current public truth does not bind them.

No hidden live execution from this page.

No fake quote, wallet, receipt, transaction, or settlement.

Gold only marks explicitly verified proof.

02 · Required input

Inputs are explicit before execution.

Where the current OpenAPI route binds an input schema, this page renders that exact schema. Otherwise the structure remains visible with a truthful unbound state.

operation

crypto.wallet.report

canonical identity

HTTP route

/v1/crypto/execute

published

Idempotency-Key

Required by the mapped public OpenAPI route.

required

Request schema · canonical OpenAPIOpen raw

{
  "oneOf": [
    {
      "type": "object",
      "required": [
        "kind",
        "address",
        "chains"
      ],
      "additionalProperties": false,
      "properties": {
        "kind": {
          "const": "balances"
        },
        "address": {
          "type": "string",
          "pattern": "^0x[a-fA-F0-9]{40}$"
        },
        "chains": {
          "type": "array",
          "minItems": 1,
          "maxItems": 2,
          "uniqueItems": true,
          "items": {
            "enum": [
              "eip155:1",
              "eip155:8453"
            ]
          }
        }
      }
    },
    {
      "type": "object",
      "required": [
        "kind",
        "address",
        "chains"
      ],
      "additionalProperties": false,
      "properties": {
        "kind": {
          "const": "tokens"
        },
        "address": {
          "type": "string",
          "pattern": "^0x[a-fA-F0-9]{40}$"
        },
        "chains": {
          "type": "array",
          "minItems": 1,
          "maxItems": 2,
          "uniqueItems": true,
          "items": {
            "enum": [
              "eip155:1",
              "eip155:8453"
            ]
          }
        }
      }
    },
    {
      "type": "object",
      "required": [
        "kind",
        "address",
        "chains",
        "lookbackDays",
        "limit"
      ],
      "additionalProperties": false,
      "properties": {
        "kind": {
          "const": "transactions"
        },
        "address": {
          "type": "string",
          "pattern": "^0x[a-fA-F0-9]{40}$"
        },
        "chains": {
          "type": "array",
          "minItems": 1,
          "maxItems": 2,
          "uniqueItems": true,
          "items": {
            "enum": [
              "eip155:1",
              "eip155:8453"
            ]
          }
        },
        "lookbackDays": {
          "type": "integer",
          "minimum": 1,
          "maximum": 90
        },
        "limit": {
          "type": "integer",
          "minimum": 1,
          "maximum": 50
        }
      }
    },
    {
      "type": "object",
      "required": [
        "kind",
        "address",
        "chains",
        "lookbackDays",
        "limit"
      ],
      "additionalProperties": false,
      "properties": {
        "kind": {
          "const": "report"
        },
        "address": {
          "type": "string",
          "pattern": "^0x[a-fA-F0-9]{40}$"
        },
        "chains": {
          "type": "array",
          "minItems": 1,
          "maxItems": 2,
          "uniqueItems": true,
          "items": {
            "enum": [
              "eip155:1",
              "eip155:8453"
            ]
          }
        },
        "lookbackDays": {
          "type": "integer",
          "minimum": 1,
          "maximum": 90
        },
        "limit": {
          "type": "integer",
          "minimum": 1,
          "maximum": 50
        }
      }
    }
  ]
}

03 · Returned result

Result, evidence, and receipt stay separate.

A useful response is not automatically a verified paid outcome. The page keeps schema, evidence, receipt, and proof state distinct.

result contract · canonical where bound

{
  "type": "object",
  "required": [
    "operationId",
    "state",
    "replayed",
    "requestHash"
  ],
  "properties": {
    "operationId": {
      "type": "string"
    },
    "state": {
      "const": "RECEIPTED"
    },
    "replayed": {
      "type": "boolean"
    },
    "requestHash": {
      "type": "string",
      "pattern": "^sha256:[a-f0-9]{64}$"
    },
    "receipt": {
      "type": "object",
      "additionalProperties": true
    },
    "output": {
      "type": "object",
      "properties": {
        "route": {
          "type": "object",
          "required": [
            "routeId",
            "qualificationId",
            "servingAdapters",
            "degraded",
            "fallback",
            "cost"
          ],
          "properties": {
            "routeId": {
              "type": "string"
            },
            "qualificationId": {
              "type": "string"
            },
            "servingAdapters": {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            "degraded": {
              "type": "boolean"
            },
            "fallback": {
              "type": "boolean"
            },
            "cost": {
              "type": "object",
              "additionalProperties": true
            }
          },
          "additionalProperties": true
        }
      },
      "additionalProperties": true
    },
    "execution": {
      "type": "object",
      "additionalProperties": true
    }
  },
  "additionalProperties": true
}

04 · Availability & limitations

Current availability before the call.

Operation publication and family probe truth are shown separately so a family-level live observation cannot silently make every operation callable.

Operation lifecyclePreview

Current catalog marks this operation publicly available.

Family probelive

Observed family state; not substituted for operation publication.

Operation healthNot bound

No operation-specific incident feed is bound.

Proof levelquote observed, unpaid

Current observed family proof vocabulary.

05 · Price, asset, network & approval

No hidden charge. No standing permission.

Current pricing truth is bound where the public pricing document has an exact operation record. Approval controls below are a labeled visual fixture and perform no authorization.

Current price boundary

fixed by operation

Current published maximum: 0.004 USDC.

Operationcrypto.wallet.report

Maximum0.004 USDC

NetworkNot bound at operation level

AssetUSDC

Price versioncrypto-product-2026-08-09.1-crypto.wallet.report

Observed2026-08-11T08:48:34.576Z

Approval boundary · design fixture

Not approved

0.004 max

Standing authorityNone

This UI state does not sign, authorize, fund, or settle anything. It exists only to preserve the locked approval information architecture.

06 · Execution states

Verified, refused, and unresolved are different outcomes.

Request red enters. Qualification, execution, and unresolved investigation use cyan. Gold appears only on the verified proof state.

Scenario · design fixture

Run the operating contract visually.

No API, provider, wallet, payment, or settlement action is performed.

Design-state fixture only. No live request, wallet action, payment, settlement, or receipt generation occurs here.

Request

Bounded task and identity received.

waiting

Qualify

Lifecycle, schema, policy, route and price boundary checked.

waiting

Execute

Selected route would perform the approved task.

waiting

Verify

Output, evidence and settlement truth would be checked.

waiting

Prove

Result, evidence, receipt and replay state close the contract.

waiting

07 · Expected latency & timeout

Unknown timing stays unknown.

The locked structure is preserved without fabricating a percentile chart, SLA, provider deadline, or reconciliation duration.

Operation latency

—

Not published.

No reproducible operation/version latency measurement is currently bound to this page.

Timeout & reconciliation

—

Not bound at operation level.

Platform recovery rules remain available below. A blind retry is never implied when settlement is unknown.

08 · Evidence & receipt fields

Proof is part of the product surface.

Exact paid proof is shown only when the current status authority names this operation. Otherwise the page keeps proof neutral.

Current proof boundary

quote observed, unpaid

family observation · Crypto Intelligence

operationcrypto.wallet.report

response schemaOpenAPI-bound

receipt generation herenone

customer revenue claimnone

Operation-specific proof

No paid outcome proof bound.

No gold production claim

settlementnot asserted

replaynot asserted

receiptnot invented

09 · Skill, MCP, SDK & HTTP

The same operation identity across every interface.

Only package publication and raw routes proven by generated public artifacts are shown. Operation-specific client syntax is omitted when it is not safely generated here.

POST /v1/crypto/execute
OpenAPI: /openapi.json
Idempotency-Key: required

Canonical publication evidence only. No `@clervo/router` publication or unsupported client compatibility is implied.

10 · Errors & recovery

Every known failure keeps a next action.

HTTP errors come from the mapped OpenAPI route where one exists. Platform recovery codes come from the generated onboarding contract and remain separate from operation-specific claims.

OpenAPIHTTP 400Invalid bounded Crypto Intelligence requestFollow published problem details; no recovery is invented here.

OpenAPIHTTP 402x402 or MPP payment requiredFollow published problem details; no recovery is invented here.

OpenAPIHTTP 409Idempotency or quote conflictFollow published problem details; no recovery is invented here.

OpenAPIHTTP 503Qualified supply, durable state, or settlement is unavailableFollow published problem details; no recovery is invented here.

Platform recoveryinsufficient_fundsinsufficient_fundsAdd enough of the quoted asset on the quoted network, then request a fresh quote. · retry: after action

Platform recoverywrong_network_or_assetwrong_network, wrong_asset, unsupported_network, unsupported_assetSwitch to the quote's exact network and asset, then request a fresh quote. · retry: after action

Platform recoveryexpired_quotequote_expired, expired_quoteRequest a fresh quote and never reuse the expired authorization. · retry: after action

Platform recoveryrejectedauthorization_rejected, payment_rejected, user_rejectedReview the maximum charge and approve again only if you still intend to pay. · retry: after action

Platform recoverytimeoutauthorization_timeout, payment_timeoutReconcile the existing idempotency key before deciding whether to retry. · retry: prohibited until reconciled

Platform recoveryunknown_settlementsettlement_unknown, unknown_settlementReconcile the existing operation and do not authorize or retry until settlement is definitive. · retry: prohibited until reconciled

11 · Idempotency & safe replay

The same bounded task does not silently become a second effect.

Where current OpenAPI requires an Idempotency-Key, that requirement is shown directly. Retention windows and scope are not invented.

Replay contract

Identity before retry.

The current mapped HTTP route requires Idempotency-Key. Retention duration and account scope are not published on this page.

Operation: crypto.wallet.report
Idempotency-Key: required · value supplied by caller
Retention: not published
Unresolved settlement: retry blocked until reconciliation

Replay · design fixture

Awaiting verified fixture

Live executionNone

Fixture replayNot requested

Additional live chargeNone

Run the verified design state first to demonstrate safe replay semantics.

12 · Version history & related operations

Current version truth without invented history.

The current contract, catalog, pricing, and observation identifiers are visible. Historical operation versions remain unclaimed until a canonical history exists.

Contract 2026-07-29.1Current generated contract

Catalog 2026-08-02.2. OpenAPI 2026-07-29.1. Observed 2026-08-11T08:48:34.576Z.

Operation historyNot bound

No synthetic changelog, sunset date, compatibility window, or replacement history is generated here.

Current machine surfaces

Inspect the source documents.

Catalog · 2026-08-02.2 OpenAPI · 2026-07-29.1 Pricing · observed 2026-08-11T08:48:34.576Z Status · observed 2026-08-11T08:48:34.576Z