Limits, billing and help
Current limits
For a human-owned early-access mailbox, the current public documentation states 100 stored messages, 10 MiB total storage and 1 MiB per incoming message including MIME overhead. The plain-text preview is bounded to 64 KiB and marks truncation. Up to 10 active read keys can be created, each expiring within 30 days. The list API accepts 1–100 messages per page and defaults to 50. A full mailbox cannot accept more mail; delivery then depends on the sender's retry behavior. There is no automatic retention period in the current human mailbox service.
The free agent-owned enrollment pilot has separate bounds: one inbox and one 24-hour read key per registration, 100 messages/10 MiB, up to 100 incoming messages per day, 600 reads per hour and 1 MiB per message. Enrollment has challenge and registration rate limits and a shared pilot capacity; an available handle alone does not guarantee an enrollment slot. The agent enrollment guide is authoritative for its current protocol and caps.
Plans and billing
Every account starts on the free plan: 1 inbox and 1,000 emails a month. Paid: one monthly plan with no tiers. Every $1 a month adds 1,500 emails, 5 inboxes and 1 custom domain, and the price scales in a straight line:
| Monthly price | Emails per month | Inboxes | Custom domains |
|---|---|---|---|
| $10 (minimum) | 15,000 | 50 | 10 |
| $20 | 30,000 | 100 | 20 |
| $50 | 75,000 | 250 | 50 |
| $200 (self-serve maximum) | 300,000 | 1,000 | 200 |
Each email one of your inboxes sends or receives counts once toward the monthly total. Inboxes are total account capacity, including the primary inbox and owner-created agent inboxes. For more than $200 a month, contact support as described below.
Checkout opens soon. Nothing can be bought or charged on agentemail.cc today. Sending from customer inboxes and custom domains are also coming soon; inboxes receive mail today. Until checkout opens, signed-in early-access mailboxes and the agent enrollment pilot keep the limits listed above; neither is a plan. When checkout opens, check that your dashboard shows the new plan and capacity before relying on it; an interrupted or canceled checkout is not an active subscription.
Existing subscriptions on earlier plans stay as they are. Your dashboard shows your account's current plan and capacity, and that is what you can use. A plan or allowance does not by itself authorize outbound mail: customer API sending will require a separately issued send key and an enabled, provider-approved sending route.
If something is not working
- Cannot sign in or see a mailbox: Refresh the dashboard session. Human sign-in uses your Guth account. An agent-owned inbox does not appear in the human dashboard through a claimed address, and human claim is not yet available.
- Email has not appeared: Confirm the full address, send from an independent mailbox, refresh the inbox, and allow for sender retries. A ready mailbox or a welcome message is not proof of external delivery. If the mailbox is full or the message exceeds 1 MiB, it cannot be accepted under current limits.
- API request denied: Check that the key was copied completely, has not expired or been revoked, and belongs to this inbox. Use the
Authorization: Bearerheader from a server-side client. A Guth browser session is not an API key, and a read key cannot call send or account operations. - Key lost: A human owner can revoke the old key and create another in API access. An agent owner must use its saved signing key and stable enrollment operation to reconcile or rotate; successful replay will not reveal the previous secret.
- Preview incomplete: Inspect
text_truncatedandpreview_available. The raw endpoint downloads the original message; parsed previews omit HTML execution and attachment bytes. - Checkout or send unavailable: A paid checkout is confirmed only when your account reports the new plan and capacity. A send allowance does not overcome missing authorization or a disabled outbound route.
For support, email services@getguth.com. Include the affected route, time, status code and a redacted error or request ID. Never send mailbox keys, private signing keys, payment credentials or full private messages in a support report.