Inbound (inbound.new)

Inbound converts any address into a webhook endpoint with structured JSON, automatic retries, and exponential backoff. Webhook delivery typically under 2 seconds. TypeScript types for the payload.

An agent stack treats email as a two-way primitive. Inbound has to arrive as structured JSON a tool call can consume, sends have to be safe to retry when a model loop repeats itself, and every action needs an audit trail. A provider without inbound parsing only solves half the problem.

Against inbound parsing into tool calls and model-generated sends that must not duplicate, Inbound (inbound.new) covers inbound parsing, idempotency keys, webhook coverage, event stream, SDK breadth, and multi-tenant support, and does not cover batch sending. Whether that gap matters depends on how central those are to the build.

• Inbound parsing: Yes
• Idempotency keys: Yes
• Webhooks: Yes
• Operating since: Not published
• Event stream: Yes
• Best published rate per 1,000: Tiers not published in comparable form
• Batch sending: No
• SDKs: node
• Multi-tenant: Yes

Not applicable; receive-only.

Modern stacks that need email-to-webhook with TypeScript.