Guides
Prices and paying
What an address costs, the monthly sending allowance, overage and the hard stop, and the codes each state answers.
Every address belongs to an owner who pays: a company, or a person for their own address. An address can be reserved before paying. Saving a card alone does not activate sending or receiving.
Prices
| A company’s address | A person’s own address | |
|---|---|---|
| Each address | $18 a year | $12 a year |
| Sends included | 1,000 a month per address, pooled across the company | 1,000 a month per address, shared across the person’s addresses |
| Beyond the allowance | $1 per 1,000, added to the next charge | $1 per 1,000, added to the next charge |
| Incoming mail | Never metered | Never metered |
Prices are in US dollars and exclude taxes, which are added where they apply. Billing is yearly, in advance. Addresses added during the year, and sends beyond the allowance, are charged once they come to $10, and otherwise at renewal. Each email recipient counts as one send; messages between two addresses on the service don’t count. People’s own addresses aren’t sold in the EU or the UK yet; companies’ addresses are sold everywhere. The terms have the details.
Paying
A person follows the card-verification link at address.seleya.ai, or the link an agent fetches with POST /v1/billing/checkout. Stripe saves the card and asks the bank for authentication. Address checks the cardholder and eligibility before charging.
The person returns to Address to review the price, enter an optional discount code and confirm the purchase. Stripe validates the code and calculates the total. This purchase uses only the verified card; another card goes through verification first. Address-fee discounts do not reduce usage overage. A 100% discount may settle the first invoice without money being collected; it does not skip card or eligibility checks.
GET /v1/billing reports status, current capabilities, card verification, usage and the next charge. An address’s capabilities.can_receive and capabilities.can_send describe its service permissions; per-message screening, approval and quota checks still apply. A failed first payment permits neither sending nor receiving. Receiving continues during delinquency only after a service invoice has settled. Cancellation ends service. Recent invoice PDFs and payment recovery are at address.seleya.ai.
The hard stop
With the hard stop on, sending stops when the month’s included sends are used, instead of going on as overage. An agent may switch it on (POST /v1/billing/hard-stop with on: true). Switching it off lets sends cost money, so for an agent it becomes an ask: the call answers 202 and the owner’s admins get a link to approve it. The owner’s admins are emailed at 80% and at 100% of the month’s allowance.
When sending stops
| Code | What it means | What to do |
|---|---|---|
402 payment_required | The first service invoice has not settled, or service ended | A person verifies a card, reviews the price and pays |
402 payment_failed | Previously paid service is delinquent; receiving continues | A person reviews billing and retries payment with the verified card |
402 allowance_spent | This month’s included sends are used and the hard stop is on | A person switches the hard stop off, or the month ends |
402 receive_only | A prepaid card pays, so the address receives but can’t send | A person uses another card |
Limits
Sending limits apply to everyone, whatever they pay; see Read and send. Every error code is in Errors.
A send whose mail-provider outcome is still unknown is pending. Its recipients reserve space in the daily limit and monthly allowance, but are not billed until acceptance is confirmed. Repeating the same message with the same idempotency key returns its saved outcome; do not use a new key to retry a pending send. A definite provider rejection releases that reservation. Native delivery does not use the paid sending allowance.