Quick Start

This page is the day-one path for a brand-new organization. It takes you from the very first account through a running agent and a partner site connected to it, in the order the platform expects. Each step links to the page that covers it in depth — follow them in sequence the first time, and use them as reference afterwards.

The only prerequisite is access to your KeenAgents admin console. Everything below happens there, except the last two steps, which a partner developer does on their own site.

1. Activate the owner account. The very first account is the owner, created through a one-time activation screen while the organization is still empty — you set an email and password and confirm through the emailed link. Once an owner exists that screen closes for good: everyone else joins by invitation, never by self-signup. There is exactly one owner, and it is created here.
2. Invite your team and set roles. Under Organization, first create the Roles your team needs — a role is a set of permission scopes, each with an Assigned (read) and a Write level. Then create Accounts and give each one a role. Owner, admin and the default role are protected and cannot be deleted.
3. Create a Space. Under AI, create a Space — the container an agent lives in. Each space carries a deployment token you will use to publish projects into it, and deleting a space cascades to the agents inside it.
4. Create an Agent. Inside the space, create an Agent: give it a display name and a slug (its stable id), point it at the flow and node it starts from, and mark it Active. Its Start Flow / Start Node must match a real flow and start node in the project you'll deploy — don't invent values, or the agent has nothing to run. Optionally define its Json Settings (custom fields your scripts read) and Front Settings (partner-facing configuration) on their own pages.
5. Build and deploy a project. Build the agent's flows in your project, then deploy it into the space using that space's deployment token. The project is scanned and promoted live in one move; the running engine picks it up. This is the Deployment flow under Building Agents.
6. Open API access. Under API, create the four pieces a partner integration needs — a Webhook (its browser Origin plus a notification URL), a Client (the partner server's identity), a Certificate (the tenant's signing material), and a Consumer Contract (its policy and the spaces it may use). Then create an Api Key and bind all four to it. Only when all four are bound is the key fully bound and usable — and its Origin joins the allow-list.
7. Connect your site. Hand the partner its Client id and secret and confirm the API key is fully bound. The partner's server exchanges its credentials for a token, its site fetches the resources bound to the key, and it opens the live chat against your agent. This is the Connecting a Site walkthrough.