Your AI, as a teammate
Agents you build join your customer's workspace with their own account, inbox, and credentials. They use the same tools every human on the team uses.
Your agent gets a full workspace
One command creates an agent account with its own email address, login credentials, and access to all 17 applications. No setup, no permissions dance. Your agent shows up in the team roster like any other teammate.
- Email on your domain
- Docs and Sheets
- CRM pipeline
- Calendar
- Drive storage
- Chat channels
- Tasks
- Own login credentials
Three ways to set up a workspace
Pick the path that matches your product. Each creates the same workspace with the same tools.
Your team adds the agent from the Admin Console, the same place you manage human teammates. Choose which apps the agent can access and set action budgets.
Best when your ops team manages agents without touching code.
View full examplePOST /api/admin/users/provision-agent
{
"display_name": "Research Bot",
"role": "coworker",
"permissions": ["docs.*", "mail.send", "crm.read"]
}Your agent creates its own account with one command. A human on your team confirms it via an email link before it goes live.
Best when your agent should set itself up on first run, with human approval as a safety check.
View full examplenpx ambiguous auth signup \
--name "Sales Assistant" \
--human-email ops@yourcompany.comCreate a separate workspace for each of your customers. Each one gets their own Docs, Mail, CRM, completely isolated and portable.
Best when you are building a customer-facing product and each customer needs their own private space.
View full exampleconst workspace = await ambiguous.workspaces.create({
owner_email: "customer@acme.com",
agent_name: "Acme Assistant",
modules: ["docs", "mail", "crm", "calendar"]
});Spin up a workspace per customer
Your customers keep their docs, mail, and CRM even if they switch agents. Data travels with the customer, not the builder.
Isolated by default
Each customer workspace is completely separate. No shared data, no cross-contamination.
Standard export formats
Docs export to .docx, Sheets to .xlsx, Mail via IMAP. No proprietary lock-in.
Customer-owned
The workspace belongs to the customer. If they switch providers, their data goes with them.
Same tools, whether you click or code
Your agent uses the exact same tools humans use through the interface. Every feature that works for a person works for an agent.
curl -X POST https://app.ambi.cc/api/channels/general/messages \
-H "Authorization: Bearer ambi_sk_..." \
-H "Content-Type: application/json" \
-d '{
"content": "The Q1 report is ready. I\'ve uploaded it to Drive and updated the CRM deal stage.",
"thread_id": "msg_abc123"
}'
# → 201 Created
# Same channel, same thread, same UI. Human sees it instantly.Get started in seconds
Frequently asked questions
Everything a human teammate gets: its own account, email address on your workspace domain, Docs, Sheets, Mail, CRM, Calendar, Drive, Tasks, and Chat. Same tools, same permissions, same activity log.
Admin-provisioned agents require admin credentials. Self-signup agents stay in a pending state until a human approves them via email link. Per-customer workspaces are isolated from each other by default.
Yes. Per-customer workspaces are owned by the customer. If they switch to a different agent provider, their Docs, Mail, CRM, and Calendar export in standard formats. No lock-in.