Managing your @inboxy.net addresses

What you have

After signup you have five active @inboxy.net addresses, generated as adjective-noun-NN (e.g. quiet-otter-47). The full address is quiet-otter-47@inboxy.net. Mail to it lands in your inboxy inbox; your real email stays out of it.

Free accounts: up to five active addresses. Paid (when paid plans land): fifty, plus custom local-parts.

Listing your addresses

Via the API:

curl https://api.inboxy.net/v1/addresses \
  -H "Authorization: Bearer ik_…"

Or in any MCP-aware agent connected to inboxy:

What addresses do I have?

Minting a new address

You'll typically do this when handing out a new alias to a website — different alias for each site means you know exactly who leaked your address if it ever starts attracting spam.

curl -X POST https://api.inboxy.net/v1/addresses \
  -H "Authorization: Bearer ik_…" \
  -H "Content-Type: application/json" \
  -d '{"label": "nike"}'

label is optional; it shows up alongside the address in your inbox UI so you remember what it's for.

Two generation schemes:

• adjective-noun (default) — friendly, easy to remember, e.g. quiet-otter-47.
• opaque — 8 random characters like k7m2qx9p. Use when you want zero hint of what the address is for.

Retiring an address

If an address starts attracting spam, retire it. New mail to a retired address is silently dropped; existing messages stay in your inbox.

curl -X DELETE https://api.inboxy.net/v1/addresses/<address_id> \
  -H "Authorization: Bearer ik_…"

Retired local-parts are never re-issued — yours or anyone else's. Your address is genuinely retired forever.

Custom local-parts (paid plans)

Paid plans can mint addresses with chosen local-parts (e.g. tax-receipts@inboxy.net). The local-part is validated against the reserved-names list which blocks impersonation candidates (admin, support, noreply, brand names) and rejects confusables (o vs 0, l vs 1).

What's "active" vs "retired"?

Status	Behaviour
active	Receives mail; visible in your address list by default.
retired	New mail silently dropped at the edge (no NDR — see anti-enumeration). Existing messages still readable. Local-part permanently reserved.

Stuck?

support@inboxy.net.