Numonic — The Email Control Plane

Canonical State

System of Record

Other platforms reconstruct what happened from scattered events. Numonic owns the state — every check, every transition, every reason — in one record from first API call to final outcome.

"Did my emails get delivered?" now has a real answer.

GET /v1/sends/snd_01jt4k/explanation

{
  "send_id":      "snd_01jt4k...",
  "state":        "bounced",
  "reason_code":  "bounce.hard_bounce",
  "reason":       "Mailbox does not exist",
  "smtp_code":    "550",
  "transitions": [
    { "state": "queued",    "at": "10:30:00" },
    { "state": "sent",      "at": "10:30:02" },
    { "state": "bounced",   "at": "10:30:09" }
  ],
  "checks": [
    { "suppression_list": "passed" },
    { "domain_verified":   "passed" }
  ]
}

Intelligent Queuing

Emails Never Disappear

On other platforms, a failed send is a lost email. On Numonic, it's held — with a state and a reason. Marketing sends queue automatically and release when conditions allow.

Send once. Numonic handles the rest.

                  
State Timeline

                    queued — API request received
                  
09:00:01

                    held — warmup limit reached, queued for release
                  
09:00:02

                    released — domain quota reset, send resumed
                  
10:00:00

                    delivered — accepted by recipient server
                  
10:00:03

Infrastructure Layer

Built for Machines

Email platforms were built for humans watching dashboards. Today, backend services and AI agents send the majority of email — automatically, without anyone watching. When something goes wrong, there's no one to catch it.

Passive infrastructure wasn't built for this. Numonic was.

Domain Health

Protect Your Rep

By the time reputation damage shows up in your metrics, it's already done. Numonic monitors continuously and intervenes — holding excess volume, blocking suppressed addresses — before anything goes out.

Other platforms show you the damage afterward. Numonic stops it before it starts.

mail.yourapp.com

Warmup Stage 4

81 / 100 health score

Bounce rate 1.2%

Complaint rate 0.02%

Daily send limit 5,000

Sends held today 218 — queued for release

218 sends held — releasing at midnight when quota resets

Integration

One endpoint. Full visibility.

Send email the same way you always have. Numonic wraps every request in a Send object — tracking state, enforcing limits, blocking suppressed addresses.

Send once

POST to /v1/sends — the same as any email API. Numonic evaluates the send before it goes out: suppression check, domain health, warmup stage.

Numonic takes over

What's safe goes out immediately. What isn't is held — not dropped, not failed. Marketing sends queue automatically and release when conditions allow.

Query it any time

Every send has a permanent record. Every state change has a reason code. Cancel in flight, retrieve history, or pull the full explanation for any send at any time.

Read the API Docs →

Request

POST /v1/sends
Authorization: Bearer sk_live_...

{
  "to":          "user@example.com",
  "from":        "noreply@yourapp.com",
  "subject":     "Your order is confirmed",
  "body_html":   "<p>Thanks for your order.</p>"
}

Response 200 OK

{
  "send_id":       "snd_01jt4k...",
  "state":         "queued",
  "domain":        "yourapp.com",
  "warmup_stage":  4,
  "eligible":      true,
  "checks": {
    "suppression":  "passed",
    "domain":       "verified",
    "rate_limit":   "within_quota"
  }
}

Why Numonic

What Numonic does that no one else does

Provable state, not inferred events.

Call one endpoint. Get the reason code, the checks that ran, and the full transition history. Every other platform reconstructs an answer from events. Numonic's answer is a fact.

Failed sends don't disappear. They hold.

Every email exists as a record before SES ever sees it. Hit a limit, exceed a quota, trigger a block — the email is held, not dropped. On every other platform, a failed send is a lost email.

Acts before damage, not after.

Elevated bounce rate? Numonic knows before the next send goes out. Warmup volume exceeded? The excess is held rather than sent and the domain takes the hit. Other platforms show you the damage. Numonic stops it.

Every decision recorded immutably.

policy_actions[] on every send. Append-only. Permanent. Audit any send at any time and see exactly what Numonic decided, in what order, and why. No other platform has a control record at the request level.

Built for systems, not just humans.

Other platforms assume a human made a deliberate decision. Numonic is designed for automated callers — it evaluates the send, decides what's safe, and returns a structured response with options. The infrastructure has agency.

Two levels of explanation, simultaneously.

Why did this email end up in this state? Why did the platform make the decisions it made? No other platform answers both because no other platform has the Send object as a first-class entity with its own audit trail.

A Single Source of Truth for Every Email