Durable intent
Required idempotency converges retries on one message, one usage reservation, and one provider submission.
Outbound transactional email / API v1
The same control plane for humans and agents.
Build through the dashboard, REST, TypeScript, Python, or MCP. One contract, one audit trail, and one explicit approval boundary.
Account creation is open. External sending is manually approved.
01 / One contract
A precise instrument, not another sending wrapper.
Marmunk keeps intent, policy, provider outcomes, suppressions, and webhooks in one durable model. A 202 means accepted by Marmunk—not delivered.
Every outcome
Correlate a Marmunk ID with policy decisions, recipient events, signed webhook attempts, and safe request metadata.
Policy at both edges
Approval, sender identity, suppression, credential, and limits are checked at acceptance and again before submission.
02 / Equal interfaces
One operation. Choose your instrument.
POST /v1/emails
Authorization: Bearer ••••••••
Idempotency-Key: order-4821-receipt
{ "from": { "email": "receipts@product.example" },
"to": [{ "email": "recipient@example.net" }],
"subject": "Your receipt", "text": "Thank you." }03 / The trace
Acceptance is a beginning, not an outcome.
01IntentPersisted atomically
02PolicyApproval + limits
03QueueDurable handoff
04ProviderSubmission evidence
05EventNormalized + signed
04 / Approval boundary
Reputation risk starts with permission.
Create an account and explore test mode immediately. External sending begins only after Marmunk reviews the organization, domain, workload, recipient source, volume, and rollback plan.
Domain ownership
DNS readiness remains separate from sending approval.
Wanted recipients
No purchased, scraped, or cold-prospect lists.
Narrow controls
Pause a key, domain, tenant, or platform boundary.
Audited decisions
Operator actions require reasons and retain history.
Pending review
Identity verified · domain checked · workload submitted
No automatic production access
05 / Straight answers
Before you connect.
Does creating an account enable sending?
No. New tenants start in test-only mode. External sending requires a separate, manual workload approval.
Is Marmunk a campaign or cold-email tool?
No. Phase One supports wanted, application-triggered transactional email only. Campaigns, newsletters, lead generation, and cold outreach are excluded.
Can an agent approve its own workload?
No. MCP and ordinary API credentials cannot approve sending, mint broad credentials, or access operator functions.
Does “accepted” mean delivered?
No. Accepted means Marmunk durably recorded the intent and queue handoff. Delivered appears only after normalized provider evidence.
What does it cost?
Public pricing is not available in Phase One. Account creation and approval review do not imply a commercial offer or SLA.
Make every send explain itself.
Create your account, configure test mode, and request sending approval.