Use SDKs when a product workflow needs typed helpers around FabricBloc API calls, request signing, service clients, or agent-host integration.
Core surfaces
The core SDK foundation is iOS, Android, TypeScript, Python, REST, and MCP. Treat mobile and REST/MCP as the primary product surfaces; use TypeScript and Python for server workflows, worker jobs, developer tools, and agent hosts.
TypeScript and Python
TypeScript and Python are the primary backend SDK surfaces. Keep SDK usage server-side unless a method is explicitly documented as browser-safe.
Mobile
FabricKit covers native iOS and Android app integrations. Mobile integrations should keep wallet and token orchestration behind trusted app or backend boundaries. Public docs should describe the flow and link to generated examples only after those examples are reviewed upstream.
REST and MCP
Use REST for direct service integration and MCP for agent-hosted wallet, token, vault, and balance operations. REST and MCP should remain first-class paths, not fallback documentation. Start from the generated API reference when you need the generated service contract.
Agent hosts
Agent SDK usage should start from capability-scoped credentials, explicit tool descriptions, and auditable execution logs. Avoid giving an agent broader wallet permissions than the action requires.
Generated examples
Generated SDK examples are rendered only when the docs catalog marks them as reviewed artifacts. The public site does not call an AI model at visitor time and does not publish unchecked generated code.