Integrations
API and MCP
Taicho integration surfaces are organization-scoped so automated tools operate within the same boundaries as the workspace.
Preview
Public API reference and self-service credentials are being prepared. This page establishes the operating boundaries without publishing unstable contracts.
01
Organization-bound access
Credentials and delegated authorization are tied to a Taicho organization. Integrations cannot silently cross workspace boundaries.
02
Scoped capabilities
Clients receive only the capabilities approved for their use case. Sensitive operations remain explicit and auditable.
03
Stable contracts before examples
Endpoints, schemas, and SDK examples will appear here after the public contract is versioned. Internal implementation details stay private.