Getting started
Create an account, import or define a brand, verify the foundation, and run one focused workflow.
Opening Indoo…
Find Indoo getting-started, brand setup, approval, integration, MCP, security, and API-surface guidance with explicit capability and permission boundaries.
What this page covers
Getting started · Connections · Machine accessIndoo documentation begins with the supported public product surfaces: website-first brand setup, brand-scoped work, approvals, social connections, Slack, Telegram, MCP, account usage, security, and the deployment's OpenAPI description.
Verified against the current Indoo product · 2026-08-17Create an account, import or define a brand, verify the foundation, and run one focused workflow.
Review provider setup, supported actions, permissions, tests, limitations, disconnection, and token rotation.
Use the deployment's OpenAPI description and brand-scoped MCP access with authentication, tenant scope, rate limits, and structured errors.
For docs, the sequence keeps context, ownership, and the next decision visible.
Confirm whether the action is supported and which brand, role, provider, or permission it requires.
Connect a test account or bounded brand before enabling consequential external actions.
Respect structured errors, rate limits, idempotency, and explicit permission for write or destructive operations.
The same-origin application exposes an OpenAPI description at /openapi.json for the deployed API. Not every internal route is intended as a public developer product; verify support before building against it.
Answers stay specific to docs and the current product boundary.
Yes. The current MCP integration provides brand context, agent chat, and content read capabilities using a brand-scoped token.
No. The schema describes the deployment, but product support, stability, authentication, and intended external use must be confirmed for the route.