Outborn Agent Platform · Technical reference
Client and SDK options
Use a compatible MCP client for the documented external surface; treat repository runtime packages as internal.
Applied guidance
Best practices for client and sdk options
Recommended
- Choose an MCP-capable client that supports the advertised protocol and authorization flow.
- Record the deployed origin and discovered schemas your client targets.
Avoid
- Do not treat packages/outborn-ai-runtime-sdk as a published external client SDK.
01
Use an MCP-capable client
An external client can integrate with the documented /mcp/v1 JSON-RPC endpoint and Outborn Account authorization flow. Discover the resource, obtain a token for it, and call tools/list rather than hardcoding an assumed tool inventory. Choose a client library that supports the advertised protocol version and your deployment's authorization flow.
02
Internal runtime package
The repository contains packages/outborn-ai-runtime-sdk for first-party runtime integration. It is not presented here as a published, versioned external client SDK. Do not import it into an external application without a separate support contract.
03
Pin the integration boundary
Record the deployed MCP origin, protocol version, discovered tool schemas, and the Outborn Account authorization configuration your client was built against. Recheck discovery and permissions after deployment changes.
Related documentation