GET

AI wallet control

Get policy

/api/v2/ai-wallets/{binding_id}/policy

AUTHENTICATIONBearer token · ai-wallets:readService ownercore-ai-wallet-controlContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Return the complete versioned capability, allowlist, budget, velocity, and approval policy.

When to use it

Call this when a wallet, treasury, custody, or governed agent workflow needs to evaluate the current status, readiness, policy, or aggregate posture of policy so it can make a custody decision inside the correct owner, workspace, network, and policy boundary.

OUTCOME · Evaluate readiness

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 evaluate policy.
Makes custody state understandable without exposing seeds, shares, nonces, private keys, or other reusable signing material.

ISOLATION + AUTHORITY

The authenticated owner, workspace, network, and wallet policy remain authoritative. A wallet record, policy result, approval, ceremony, or balance never grants another lifecycle stage and cannot substitute for threshold signing or separately owned funding, settlement, publisher, matching, or trading authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Supply the required binding_id (path) exactly as defined by the live contract.
Resolve the active workspace, network, wallet lifecycle, and applicable custody policy before relying on this result.

WHAT TO DO NEXT

Re-read the wallet and policy state before the next governed action, especially after an ambiguous or concurrent result.
Refresh policy when its observation time, version, or lifecycle state is no longer adequate for the decision.

AGENT GUIDANCE

Use policy only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required binding_id (path) exactly as defined by the live contract.
Keep enrollment, activation, policy evaluation, approval, ceremony, signing, submission, confirmation, and settlement as distinct states.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

AI WALLET AUTHORITY BOUNDARY

Implemented reads expose bearer-derived workspace projections, exact policy versions and commitments, independent native-asset budgets, retained decisions, and execution-readiness evidence. POLICY_APPROVED is not transaction construction, signing, broadcast, confirmation, or settlement. The implemented intent-evaluation route is a dry run: it creates no intent, reservation, event, approval, transaction, signature, or broadcast. Any lifecycle, policy, retained-intent, cancellation, or execution operation marked planned is non-executable and must not be registered as an agent tool.

Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

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

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing the ai-wallets:read scope.EXAMPLEBearer hc_live_…

binding_idpathRequired

32-character lowercase hexadecimal UUIDAI wallet binding visible in the authenticated workspace.EXAMPLEa1b2c3d4e5f6471890abcdeffedcba09

X-Request-IDheaderOptional

stringOptional caller correlation value. The gateway returns the effective request identifier.EXAMPLEagent-run-20260901-0042

RESPONSES

Status and payload examples

200Current committed policy.Read completed · JSON RESPONSE+

{
  "policy_uuid": "104db2e6b7b842bb8ab733e3b6e74870",
  "binding_uuid": "a1b2c3d4e5f6471890abcdeffedcba09",
  "version": 4,
  "lifecycle": "ACTIVE",
  "capabilities": [
    "wallet:read",
    "wallet:quote"
  ],
  "assets": [
    "DHYBRID",
    "USDC"
  ],
  "asset_budgets": [
    {
      "asset_code": "DHYBRID",
      "max_single_amount": "100.00000000",
      "daily_limit": "500.00000000",
      "monthly_limit": "5000.00000000"
    },
    {
      "asset_code": "USDC",
      "max_single_amount": "250.000000",
      "daily_limit": "1000.000000",
      "monthly_limit": "10000.000000"
    }
  ],
  "destinations": [
    "dhyb1approveddestination…"
  ],
  "max_single_amount": "100.00000000",
  "daily_limit": "500.00000000",
  "monthly_limit": "5000.00000000",
  "velocity_window_seconds": 3600,
  "velocity_max_count": 20,
  "autonomous_threshold": "0",
  "currency": "DHYBRID",
  "policy_commitment": "4c2ac3d7…",
  "created_by_profile_uuid": "profile-01",
  "created": "2026-09-01T18:00:00Z",
  "expires_at": null
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then re-read the wallet and policy state before the next governed action, especially after an ambiguous or concurrent result.
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. Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.

401The bearer credential is missing or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "The bearer credential is missing or invalid."
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY: Retry only with a newly valid credential and fresh replay-protection values. Do not replay an expired signature.
STATE RECONCILIATION: Authentication failed before an authoritative read was returned for owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

403The credential lacks ai-wallets:read or is outside the derived workspace.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks ai-wallets:read or is outside the derived workspace."
}

INTEGRATION DECISIONinsufficient_scope

CALLER ACTION: Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY: Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION: Confirm the caller and resource resolve to the same authority boundary for owner-scoped wallet inventory, custody policy, balances, intents, reservations, transactions, and receipts.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

404The binding or child resource is not visible in this workspace.Resource not visible · JSON RESPONSE+

{
  "code": "ai_wallet_resource_not_found",
  "message": "The binding or child resource is not visible in this workspace."
}

INTEGRATION DECISIONai_wallet_resource_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: Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

422One or more path identifiers are malformed.Request must change · JSON RESPONSE+

{
  "code": "invalid_identifier",
  "message": "One or more path identifiers are malformed."
}

INTEGRATION DECISIONinvalid_identifier

CALLER ACTION: Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY: Do not retry the same invalid request. A corrected read may be sent as a new attempt.
STATE RECONCILIATION: Compare the submitted values with the documented constraints before another call. Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

503The authoritative AI wallet control plane is unavailable and failed closed.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "ai_wallet_control_unavailable",
  "message": "The authoritative AI wallet control plane is unavailable and failed closed."
}

INTEGRATION DECISIONai_wallet_control_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: Re-read the wallet, intent, reservation, and transaction status on the same network; compare policy version, nonce, digest, and terminal receipt before another command.
ESCALATE WHEN: Escalate when funds, reservations, transaction digests, or MPC state remain ambiguous after authoritative wallet and network reconciliation.

OPERATIONAL NOTES

Security and lifecycle guarantees

The gateway derives workspace and principal context from the bearer; callers cannot supply or override either boundary.
Policy approval is evidence of a policy decision only. It is never transaction construction, signing, broadcast, confirmation, settlement, or value-movement authority.
Amounts and limits are exact native-asset decimal strings. Never parse them through binary floating point or aggregate unlike assets.
Private keys, MPC shares, seeds, signing nonces, participant secrets, and credentials are never accepted or returned.
Bind any downstream decision to policy_uuid, version, and policy_commitment; re-read before consequential use.

Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory