Native MPC Wallets
Separate wallet authorization from any one signing service.
Build with wallets, payments, digital assets, and protected data. Choose a domain, confirm access, and work from the current published contract.
Start with a read-only or decision-only workflow. Add mutations only after you understand authority, retries, and the required operating controls.
Write down the operation, environment, expected result, and acceptance criteria.
Find the product path ↓Establish the approved credential type, scopes, and account or workspace context.
Request integration access ↗Check required inputs, errors, ownership, and whether the operation is implemented or planned.
Explore published contracts ↗Exercise denied requests, expired credentials, retries, and unavailable services—not only the happy path.
Review implementation blueprints ↗Learn what a product does, then open its existing API module. The reference remains the source for exact operations and required scopes.
Separate wallet authorization from any one signing service.
Evaluate an agent’s spending proposal without handing it a private key.
Connect external funding observations to a controlled settlement workflow.
Follow a payment from request through delivery and reconciliation.
Understand the sources and policy behind a published price.
Connect a structured position to its quote, funding rules, and outcome.
Retain participation and decision records around a strategy lifecycle.
Keep an asset’s issuance, supply, and ownership history connected.
Connect a credential to its issuer, status, and verification history.
Keep counterparty checks and transfer decisions in one reviewable flow.
Turn machine and partner events into attributable, retained records.
Protect confidential records while retaining evidence of their integrity.
Trace randomness inputs through their delivery and attestation boundary.
Connect platform events to controlled, retry-safe business actions.
Business blueprints help you plan the integration. Treat illustrative function names as examples and verify all operations against the current API contract.
Browse implementation guides ↗Download the published OpenAPI definition for your tooling. Do not infer production readiness from a planned capability or an example response.
Open the published OpenAPI JSON ↗