Choose your integration
Start with the method that matches how much of the user experience you want to own. You can keep existing strategy cards and data integrations while adding a hosted Join link or embed. An approved partner configuration is required for the strategies and capabilities you use; installing a package does not grant access.
| Method | Effort and control | Advantages | Responsibilities and tradeoffs |
|---|---|---|---|
| Share links | Lowest integration effort; TrustedStake hosts the flow | A link from your existing page opens the maintained wallet flow | Use the issued strategy link or approved partner catalog link. Users leave your page for the flow. |
| Embed | Moderate setup; maintained UI inside your page | Keep your page context without building wallet orchestration | Qualify your exact HTTPS origin, content security policy and wallet/browser support. Retain the supported hosted continuation where needed. |
| Headless SDK | More integration work; your native UI | Own the presentation with typed session and recovery APIs | Build the UI, customer authorization, guarded wallet adapter and persistent recovery. Configure the approved API/network pairing and verify real flows. |
| Direct / existing API | Data reads can be simple; a custom wallet flow has the most maintenance | Retain existing data integrations and choose your own client | Keep server credentials private. A custom join or exit owns signatures, fees, finality, receipt reconciliation and recovery; it is not a shortcut around those duties. |
These methods can coexist within approved configuration, but credentials, sessions and wallet payloads are not interchangeable. Give each in-flight operation one owner; switching presentation must not launch a duplicate or replay an uncertain transaction.
Share links or embed
Section titled “Share links or embed”For the smallest integration, use the strategy link issued for your approved catalog rather than constructing a launch URL. An embed keeps the maintained flow inline. Restricted/customer-specific flows require their approved authenticated server handoff; a public link does not replace customer authorization.
Detailed share-link setup and embed setup require approved distribution documentation access. Wallet and exit support must be checked for the chosen configuration. Some embedded multisig exits require an explicit portfolio continuation.
Native headless SDK
Section titled “Native headless SDK”Review the isolated SDK source, agent integration guide and npm prerelease. Pin the reviewed version:
npm install --save-exact @trustedstake/partner-sdk@0.1.0-next.5The package is ESM and has no React requirement. Its core, browser and server entry points have no runtime dependencies. The optional /polkadot adapter requires its declared Polkadot peer packages; keep the server entry out of browser bundles. Installing the SDK does not require adopting the TrustedStake app or its framework.
The SDK supports native Join, setup repair and explicit allocation approval/recovery, subject to the approved deployment and capabilities. Version next.5 adds a separate native exit controller: review fees, end the exact membership generation, wait for in-flight work, remove eligible strategy authority, and optionally convert selected alpha to liquid TAO in the same wallet. These are separate explicit intents, not one automatic withdrawal or external transfer. Read the public native exit guide and qualify the matching owner-exit API before enabling it. The host supplies customer authentication, a guarded wallet submitter, network configuration and recovery storage. Wallet signatures remain user actions; an accepted membership is not proof of completed allocation. The SDK orchestrates the supported join, exit and recovery steps in your client. Its included Polkadot adapter constructs permission, protected conversion and supported exit calls locally; supported initial-allocation trades are backend-managed, not constructed by this adapter. Pinned clients do not upgrade automatically: breaking API or runtime changes can require an SDK/adapter update and renewed testing. Mock examples and package checks are useful starting points, not live partner acceptance.
Read the protected SDK setup guide and capability map after access is approved. Controller secrets stay within TrustedStake; partners never need them.
Direct / existing API
Section titled “Direct / existing API”An existing API-powered catalog can retain its data integration and add share links or an embed for Join. A team choosing custom wallet orchestration must maintain the exact current signing contract and recovery behavior itself. Legacy data credentials do not automatically grant newer session capabilities. The retired custom delegate shortcut is not a supported alternative.
The direct integration guide and distribution contracts require approved access. The public Manager API guide describes a separate manager surface; it is not a substitute partner contract. No named partner’s current implementation or live qualification is asserted here.
Give your coding agent a clear starting point
Section titled “Give your coding agent a clear starting point”Start with public integration instructions and the public documentation index. For detailed distribution setup, request access and use the protected agent index through an approved authenticated session. Never paste credentials, private launch capabilities or customer data into prompts.
Supply the chosen method, approved partner configuration, intended strategies, page origin and supported wallets. Compile the examples and test rejected approvals, reload/interruption, repeated actions and uncertain receipts before real acceptance. Report missing configuration or untested outcomes rather than claiming a universal one-click integration.