Persist first
Authenticate, validate, enforce idempotency, and store the immutable envelope before contacting a provider.
acceptedMessage infrastructure for AI agents
Every agent can act. Make every message arrive.
A durable delivery layer for agents and modern systems. Accept once, schedule for later, route through trusted providers, retry safely, and keep the evidence.
messenger / productionaccepted
requestPOST /v1/deliveries
messageagent.research.completed
delivernow · or later
referencemsg_7fd2…91ac
proofdurable ledger + receipt
Durable acceptanceScheduled deliveryDuplicate-safe executionProvider evidence
Messages should outlive the run
Agents think in seconds. Real systems fail, throttle, wait, and recover.
Messenger separates an agent’s intent from the messy reality of delivering it.
01
The agent finishes. The delivery keeps moving.
02
Provider credentials stay outside the agent runtime.
03
Retries do not become duplicate logical messages.
04
Every claim has a reference, attempt, and receipt.
From intent to evidence
One message. A visible lifecycle.
The product decides what should happen. Messenger makes transport durable, asynchronous, and observable.
Wake when due
Deliver immediately or at a future time. The task carries identifiers, never message bodies or credentials.
pendingClaim and send
Resolve a registered route, lease one attempt, call the provider, and safely retry transient failures.
processingKeep the receipt
Expose sanitized transport state so the calling product can reconcile the outcome in its own records.
provider acceptedOne envelope, many edges
Speak in outcomes, not provider plumbing.
A provider-neutral contract carries approved content. Registered routes choose the destination system, sender identity, and secret without exposing them to the caller.
Your system decidesAudience, consent, message, timing, and business status.
Messenger deliversScheduling, routing, attempts, retries, receipts, and isolation.
01Push
02Email
03Telegram
04In-app
05 / agent-nativeSigned webhooks
The modern message layer
Built around trust, time, and proof.
Traditional message plumbing stops at the handoff. Messenger is becoming the managed layer that understands agent identity, delivery policy, schedules, provider outcomes, and the product boundary around every message.
Currently an internal SaveADay platform in private preview. Provider and recipient evidence varies by channel.
Scoped by default
Every mutation and read stays inside verified project and environment authority.
Async by design
Agent runs can end while scheduled and retried delivery continues safely.
Bounded inputs
Registered schemas, routes, destinations, and credentials keep agents inside safe rails.
Proof over promises
Stable references, attempts, safe errors, and receipts make outcomes inspectable.