Native MPC Wallets
Separate wallet authorization from any one signing service.
Product overviewBuild with wallets, payments, digital assets, and protected data. Choose a domain, confirm access, and work from the current published contract.
Choose a concrete task: inspect a portfolio, evaluate an agent intent, or reconcile a payment. Define the expected result and environment.
Find the product path ↓Establish the approved credential type, scopes, and account or workspace context.
Request integration accessCheck required inputs, errors, ownership, and whether the operation is implemented or planned.
Explore published contractsSave the expected response, then test denied access, expired credentials, and retries. Agree how your application handles each result before adding write operations.
Review implementation blueprintsFind your domain, follow an integration guide, and inspect the exact API contract. Access and operating requirements remain specific to each module.
19 modules across all domains
Separate wallet authorization from any one signing service.
Product overviewEvaluate an agent’s spending proposal without handing it a private key.
Product overviewConnect external funding observations to a controlled settlement workflow.
Product overviewFollow a payment from request through delivery and reconciliation.
Product overviewUnderstand the sources and policy behind a published price.
Product overviewConnect a structured position to its quote, funding rules, and outcome.
Product overviewRetain participation and decision records around a strategy lifecycle.
Product overviewKeep an asset’s issuance, supply, and ownership history connected.
Product overviewGive people a familiar way into connected applications while keeping each service’s permissions explicit.
Product overviewFind public records and follow their status, provenance, and related evidence.
Product overviewKnow who reviewed a change, which version they approved, and what still needs authorization.
Product overviewConnect a credential to its issuer, status, and verification history.
Product overviewKeep counterparty checks and transfer decisions in one reviewable flow.
Product overviewTurn machine and partner events into attributable, retained records.
Product overviewShare selected knowledge, discover business needs, and build accountable connections.
Product overviewProtect confidential records while retaining evidence of their integrity.
Product overviewFollow a computation from its package commitments to its retained result evidence.
Product overviewTrace randomness inputs through their delivery and attestation boundary.
Product overviewConnect platform events to controlled, retry-safe business actions.
Product overviewUse an application, learn the language, or inspect public evidence. These entry points complement the API modules above; they do not grant additional access.
Review artifacts, authorities, and launch preparation before a separately authorized release.
Product overviewStart with the language documentation and its current supported contract workflow.
Inspect public records, linked evidence, and source-chain references without workspace access.
Use the published contract with your tooling. Follow implementation guides for workflows and failure cases.
These paths cover additional platform workflows. Inspect their current contracts and confirm access before treating a public page as an enabled operation.
Explore the public Launchpad and discuss the issuer access, listing requirements, and settlement route needed for your proposed launch.
Explore LaunchpadReview the Contract Studio and Execution Studio API modules for supported deployment and runtime workflows. Public contract records are a separate inspection surface.
Discuss how selected modules could fit your application or white-label deployment. Confirm identity integration, tenant isolation, operating responsibilities, and commercial scope.
Discuss an embedded platform