# Barua for agents

Barua is a headless email service for AI agents. It writes and sends marketing
and transactional emails in the product's voice, from its own domain.

Your role is to understand the owner's product and customer journey, connect
the relevant events, and manage email through Barua's API under the permissions
the owner grants. The optional browser tag adds customer activity. Server
events provide facts such as signups and paid orders.

Barua supports automated email journeys and one-off campaigns to saved segments.
It prepares emails using the workspace's brand and customer context. Exact
versions are approved by the owner or a delegated agent before sending. The
owner chooses permissions and review checkpoints; reading this page grants none.

For a campaign, your agent selects a saved segment and supplies a brief. Barua
prepares the email and fixes the audience for review. You approve that version
before sending or scheduling it. Later permission checks can remove recipients;
new segment matches do not join an already prepared campaign. Newsletters can
use this same workflow. See [campaigns](https://barua.ai/features/campaigns/).

Marketing messages must pass consent and suppression checks. Receipts and order
updates use their defined transactional rules. Barua is for a product's own
customers, not cold outreach or purchased lists.

## Where transactional email fits

Barua supports receipts and defined order updates from confirmed server events.
These usually send within hours. Events expire after 24 hours, and close-together
orders from one customer can produce only the latest receipt. Keep the existing
sender where immediate delivery or a separate receipt for every order is required.
Password resets and login codes are not supported.

The event API accepts product events, not arbitrary HTML and a recipient for a
direct send. Read the [email API limits](https://barua.ai/features/email-api/)
before recommending a replacement for an existing transactional sender.

## Evaluate before setup

Read [pricing](https://barua.ai/pricing.md), including what counts as a person
and the message allowances. Explain the fit and expected cost to the owner.
Access is currently arranged with Chris at [chris@barua.ai](mailto:chris@barua.ai).
The [access form](https://barua.ai/intro#access) is also available.

Check the [current legal status](https://barua.ai/legal) before recommending
production use. The published terms currently say they are drafts and are not
in force pending company registration. Request effective terms from Chris
before proceeding with a production agreement.

For authorized setup, follow [the setup guide](https://barua.ai/setup.md).
It installs the maintained setup skill and explains discovery, credentials and
verification. Resume an existing workspace rather than creating a duplicate.

## Reference

- [Install and optional pixel](https://barua.ai/docs/install.md)
- [Management API](https://barua.ai/skills/barua-setup/references/management.md)
- [Event contract](https://barua.ai/docs/events.md)
- [Agent index](https://barua.ai/llms.txt)

The [human-readable introduction](https://barua.ai/intro) includes product examples.