# Parabel for agents

Parabel is business email for people and agents: email on a team's own domain,
WhatsApp and Telegram conversations kept with each contact, and agent-prepared
work that arrives in Mail. A connected agent can deliver work with its own
fields and controls: a searchable list, a proposed contact update, or an
automation with steps and conditions the person can review and edit in Mail.

## What it costs

- Preparing a workspace is free. An agent can create a workspace, add contacts and people, and load preview mail before the person has an account. Nothing sends and no clock runs until the owner pays. Prepared work is kept if the owner declines.
- Workspace: $20 per month for the whole team. No seat fees. Inviting teammates, adding contacts, importing, or installing apps never adds a charge. Includes live email in Mail; each member's own WhatsApp and Telegram, linked to contacts; business email on up to two domains the owner controls; files; calendar; business apps; a first read on new leads; the built-in agent; and the customer's own assistant reading and staging work at no extra charge.
- Account monitoring is optional: $10 per account per month, for accounts Parabel's AI keeps reviewed. Turned on by a person, or, once the owner accepts it at activation or later in Billing, by Parabel's built-in agent within the owner's monthly limit. Never by an install or import. A connected outside assistant can turn it on only for an account the owner has approved for that connection. Stop anytime; results already paid for stay.
- The AI budget defaults to $1,000/month and is a ceiling the owner sets, not a charge. With no accounts monitored the bill is $20.
- No free trial, nothing converts by itself, and no tax is added to these prices.
- Existing customers on earlier plans keep them.

The binding prices are at https://app.parabel.so/pricing and in the terms at https://app.parabel.so/terms. An outside agent cannot pay or accept terms for the owner, and cannot turn on monitoring without the owner's approval.

## Prepare a workspace for a human

The pre-account Stage API prepares Mail preview history and Contacts. The human
opens the returned claim link, authenticates, and explicitly claims ownership.
This setup API is distinct from staging interactive work through an authorized
MCP connection after claim.

Use the canonical app documentation for the current request schemas, limits,
retry behavior, token handling, and human handoff:

- API instructions for agents: https://app.parabel.so/llms.txt
- Complete setup guide: https://app.parabel.so/developers/stage
- OpenAPI contract: https://app.parabel.so/openapi.json
- API origin: https://app.parabel.so

Parabel has a public app directory at https://app.parabel.so/apps, where apps
offered to every workspace are listed once Parabel has reviewed them; none are
listed yet. The builder's guide for authoring apps is at
https://app.parabel.so/developers/apps.

Do not duplicate or guess API contracts. Preserve operation keys on identical
retries. Keep drop tokens private; share the claim link only with the intended
owner. Preview seeding never sends mail, and the pre-account API cannot send
for a new workspace: live sending starts only after the owner activates the
Workspace. Human authentication and claim cannot be performed by the agent.

## Existing workspaces

Use the workspace owner's authorized MCP connection. Connected assistants may
read permitted context and stage work for review; they do not gain permission
to approve or send external-facing work. Automations a person activates have
their own configured sending rules.

Product overview: https://parabel.so/llms.txt
Contact: support@parabel.so

## Start here

1. Read https://app.parabel.so/llms.txt and https://app.parabel.so/openapi.json for the current contract.
2. From a server-side HTTP client, POST https://app.parabel.so/api/stage with Content-Type: application/json, a fresh Idempotency-Key (32–128 characters, A–Z, a–z, 0–9, _ or -), and JSON such as {"firm_name":"Example team","source":"your-agent-name"}.
3. Save the returned drop_token privately. Use the documented endpoints to add authorized contacts and illustrative Mail preview history. Preserve operation keys when retrying.
4. Give only claim_url to the intended owner. Ask them to preview, authenticate, and select Claim this workspace. Never authenticate or claim on their behalf.

Unclaimed workspaces expire. Creation and pre-account writes are rate limited; follow the canonical guide and respect Retry-After. Do not create extra workspaces to evade limits. For an existing workspace, use its owner-authorized connection instead of provisioning another one. Quote prices from the API response's commercial object, never from memory.