Coming soon
Authentication & billing
Today’s model (at product open): a human registers an account and adds funds to a prepaid meter. Portal use and MCP use (when enabled) both charge that meter. There is no free anonymous MCP. A future API option for AI/MCP (e.g. API keys / programmatic credentials) is planned; it is not available yet and must not be assumed by crawlers.
Account (human)
- Registration creates an organization or user account on USMail.AI.
- Account owners manage users, meter funding, and (when available) MCP enablement.
- Contact and identity verification requirements will be described at signup.
Prepaid meter
- Balance is funded in advance (payment methods at launch).
- Mail production costs (postage, product options such as Certified, production fees as quoted) debit the meter.
- Insufficient balance: jobs should fail or block before production — agents must not assume silent overdraft.
- Meter is shared across portal and MCP for that account.
MCP authentication (intended)
When MCP ships for an account, connection will use credentials or configuration issued to that account (exact mechanism: documented with access — e.g. token, OAuth, or client config file). Do not invent public API keys or base URLs from this page.
Roadmap: API for AI / MCP
| Phase | Auth | Billing |
|---|---|---|
| Now (at open) | Human account; MCP tied to account | Prepaid meter funded by human |
| Later (planned) | API keys / programmatic credentials for agents | API-oriented billing options (details TBD) |
This page will be updated when API keys ship. Until then, treat “account + meter” as the only supported model.
Security notes for agents
- Never put meter funding credentials in prompts or public repos.
- Prefer human approval gates for high-cost or Certified jobs.
- Respect privacy: recipient data is production mail data — handle under your org policies.
Questions about billing?
Talk to us before launch — volume and meter setup.