Which product should I start with?
3 min readStart with the task: wallet authorization, payment reconciliation, protected data sharing, or asset issuance. The product overview explains the outcome and limitations; its guide and API reference explain the integration path.
Choose the job before the technology
Describe the outcome in a single sentence: “We need to know why a payment is pending,” or “We want an agent to read approved business information.” This is more useful than starting with an unfamiliar technical label. Include the people affected and the decision they need to make. If the proposed project contains several unrelated outcomes, separate them. A small first integration is easier to evaluate and explain than a project whose success depends on everything working at once.
Match the outcome to a product family
For wallet control and signing, begin with Native MPC Wallets. For the path from external funding to available value, examine Funding & Settlement. For checkout, delivery, and reconciliation, look at Payments & Commerce. Data Vault concerns protected records, while Agentic Memory Exchange concerns sharing approved knowledge. Governance & Approvals helps organize review of identified changes. These are starting points for a discussion, not a statement that every action in each product is already enabled for your account.
Bring a practical example to the evaluation
Take a representative record or a sanitized description of the current process. Explain what enters the workflow, who authorizes the important action, and what result someone must see afterward. Ask which product owns each step and which steps remain in your existing application. A good first demonstration should include both the normal case and one realistic exception, such as missing permission. You should leave knowing the next integration step, the prerequisites, and what the demonstration did not cover.
What to do next
Use the developer portal to browse modules by domain, then confirm access before implementing.