# Use TrustedStake documentation

Start with the public [integration comparison](https://docs.trustedstake.ai/markdown/integrations.md) for share links, embeds, the native SDK and direct API ownership. Detailed distribution contracts remain protected.

Help users and managers understand TrustedStake through the public product guides and [manager API contract](https://docs.trustedstake.ai/openapi/reference.yaml). Read [the manager guide](https://docs.trustedstake.ai/markdown/manager/overview.md) before implementing a server integration. Manager keys use Authorization: Bearer and remain server-side.

The SDK-only public source and agent guide are at https://github.com/TrustedStake/partner-sdk/tree/v0.1.0-next.5 and https://github.com/TrustedStake/partner-sdk/blob/v0.1.0-next.5/AGENT-INTEGRATION.md . They describe the next.5 prerelease, including the separate native exit lifecycle at https://github.com/TrustedStake/partner-sdk/blob/v0.1.0-next.5/NATIVE-EXIT.md . This needs the matching owner-exit API and guarded host wallet/auth/recovery implementation; it does not supply partner grants or prove a live financial integration. For the share-link, embed, native SDK and direct API method guides, obtain approved distribution documentation access at https://docs.trustedstake.ai/access/ and read https://distro.trustedstake.ai/llms.txt with that authenticated access. Private distribution contracts and Markdown are deliberately absent from this public build. Never ask a partner to paste credentials into an agent prompt.

Use the relevant guide and contract together, verify affected behavior, and distinguish API acceptance from completed chain execution. Report a concrete missing capability or access requirement instead of inventing an endpoint.