Outborn Agent Platform · Technical reference
Built-in apps and external connections
Distinguish first-party product apps from the external provider connections an integration may use.
Applied guidance
Best practices for built-in apps and external connections
Recommended
- Treat first-party app availability and external provider grants as separate decisions.
- Use an application or MCP connection for a provider integration, subject to its own scopes and owner.
Avoid
- Do not use the internal built-in app catalog as a third-party marketplace or assume a catalog entry grants provider access.
01
First-party catalog
GET /api/v1/plugins/apps/catalog is the current built-in app catalog route in the source. It describes first-party product capabilities and availability; it is not a third-party marketplace or a grant to protected data. Its direct external use needs a deployment-specific API contract.
02
External provider connections
External applications and MCP servers are configured as connections with their own credentials, scopes, owner, health, and product grants. A built-in app appearing in navigation does not mean an agent can access an external provider.
03
Extension boundary
The first-party app registration runtime lives in the product repository and is maintained with backend authorization. The reviewed source does not publish a general third-party plugin SDK, marketplace install flow, or stable download contract. External developers should use the documented MCP surface or an agreed product API instead.
Related documentation