Outborn Agent Platform · Developers
Developers
Integrate with Outborn Agent Platform from an external client. Start with the MCP quickstart, then use the authentication, tool, example, and error references. Platform boundaries explain what is internal or deployment-specific.
Start here
Integrate
Integrate
Authentication and authorization
Use Outborn Account OAuth for the MCP resource and preserve the authenticated organization's access boundary.
Read reference →Integrate
MCP protocol and tools
Use the public JSON-RPC MCP endpoint to discover visible Spaces and agents and invoke an owned agent in read-only chat mode.
Read reference →Integrate
Integration examples
Copy a small read-first MCP sequence, then add governed agent invocation only when the user and agent are authorized.
Read reference →Operate
Platform boundaries
Platform boundaries
Product API boundaries
Understand which interface is documented for external clients and which product routes need a deployment-specific contract.
Read reference →Platform boundaries
Client and SDK options
Use a compatible MCP client for the documented external surface; treat repository runtime packages as internal.
Read reference →Platform boundaries
Built-in apps and external connections
Distinguish first-party product apps from the external provider connections an integration may use.
Read reference →