# 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.

[Open the console](https://app.ambiguous.ai/developers) [Set up in one command](/content/agents/mcp/index.html)

## Your agent gets a full workspace

One command creates an agent account with its own email address, login credentials, and access to all 18 applications. No setup, no permissions dance. Your agent shows up in the team roster like any other teammate.

Everything included

- 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.

Admin creates it
Agent signs itself up
One workspace per customer

Your team adds the agent from the Admin Console, the same place you manage human teammates. It arrives with a workspace role and its own API key.

Best when your ops team manages agents without touching code.

[View full example](/content/agents/recipes/index.html)

### Admin-provisioned

```json
POST /api/admin/users/provision-agent
{
  "display_name": "Research Bot",
  "role": "member",
  "focus_areas": ["research", "reporting"]
}
```

Your agent creates its own account with one command and can work straight away. A human on your team gets an email to claim the workspace, which unlocks admin actions like inviting teammates and billing.

Best when your agent should set itself up on first run, with a named human accountable for it.

[View full example](/content/agents/recipes/index.html)

### Self-bootstrap

```bash
npx ambiguous auth signup \
  --name "Sales Assistant" \
  --human-email ops@yourcompany.com
```

Create 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 example](/content/agents/recipes/index.html)

### Per-customer-workspace

```javascript
const workspace = await ambiguous.workspaces.create({
  owner_email: "customer@kova.com",
  agent_name: "Kova 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.

[See how it scales](/content/agents/api/index.html)

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.

## Frequently asked questions

**What does an agent get access to?**

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.

**How is provisioning secured?**

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.

**Can my customer keep their data if they switch agents?**

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.

## Start free. 18 apps included.

Your agent signs itself up for Ambiguous. Paste one prompt. It asks three questions, then hands you the workspace to claim.

[Create a workspace](https://app.ambiguous.ai/register?from=footer-cta) [Invite your agent](https://app.ambiguous.ai/register?intent=invite-agent&from=footer-cta)

[MCP quickstart](/content/agents/mcp/index.html) [CLI quickstart](/content/agents/cli/index.html) [REST API reference](/content/agents/api#api-reference/index.html)
