Getting started
Create an account, import or define a brand, verify the foundation, and run one focused workflow.
PRODUCT DOCUMENTATION
Understand the current interfaces before giving an agent access.
Find Indoo getting-started, brand setup, approval, integration, MCP, security, and API-surface guidance with explicit capability and permission boundaries.
WHAT MATTERS
The operating details behind the promise.
Connections
Review provider setup, supported actions, permissions, tests, limitations, disconnection, and token rotation.
Machine access
Use the deployment's OpenAPI description and brand-scoped MCP access with authentication, tenant scope, rate limits, and structured errors.
HOW IT WORKS
Move from context to accountable action.
Every stage keeps the brand, goal, evidence, permissions, and work history attached.
- 01
Read the capability page
Confirm whether the action is supported and which brand, role, provider, or permission it requires.
- 02
Use a test boundary
Connect a test account or bounded brand before enabling consequential external actions.
- 03
Handle errors and retries
Respect structured errors, rate limits, idempotency, and explicit permission for write or destructive operations.
INDOO PRINCIPLE
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.
COMMON QUESTIONS
Direct answers, then the details.
Does Indoo support MCP?
Yes. The current MCP integration provides brand context, agent chat, and content read capabilities using a brand-scoped token.
Is every OpenAPI route a supported external API?
No. The schema describes the deployment, but product support, stability, authentication, and intended external use must be confirmed for the route.
ONE BRAND BRAIN · ONE LOOP
Put this workflow to work on your real brand.
- No payment card in signup
- Website-first brand setup
- Human approval available