Add allow/block list entries to an AgentMail pod's inboxes via MPP-paid API.
What it does
This endpoint creates a list entry (allow or block) scoped to a specific pod within the AgentMail platform. AgentMail provides programmatic email inboxes for AI agents, and this particular route lets you manage send/receive/reply allow-lists and block-lists at the pod level. The path parameters specify the pod ID, the direction (send, receive, or reply), and the list type (allow or block). The request body requires an email address or domain to add, with an optional reason.
The endpoint is part of a comprehensive AgentMail MPP gateway (OpenAPI 3.1.0) that covers inbox management, message sending/receiving, threads, drafts, domains, webhooks, and metrics. This specific "Create List Entry" operation uses HTTP POST and is priced at $0.01 per call via the MPP protocol, settling on Tempo L2 (chain ID 4217). The MPP 402 challenge was captured live, confirming the endpoint is operational. Most read operations (GET, LIST) in the API are free, while write operations carry small per-call charges.
Authentication is via Bearer token in the Authorization header. The response returns a PodListEntry object containing the entry value, pod ID, direction, list type, entry type (email or domain), organization ID, and creation timestamp.
Capabilities
Use cases
- —Block spam domains from reaching an AI agent's pod-level inboxes
- —Allow only specific sender addresses to deliver messages to agent inboxes
- —Restrict which addresses an agent inbox can reply to
- —Programmatically manage email filtering rules across all inboxes in a pod
- —Build automated email triage workflows with allow/block lists
Fit
Best for
- —AI agent developers needing per-pod email filtering controls
- —Automated workflows that dynamically manage sender allow/block lists
- —Multi-inbox pod setups requiring centralized list management
Not for
- —Human-facing email clients or webmail interfaces
- —Bulk email marketing or newsletter distribution
- —Non-email communication channels
Quick start
curl -X POST 'https://mpp.api.agentmail.to/v0/pods/MY_POD_ID/lists/receive/block' \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"entry": "spam@example.com", "reason": "Known spam sender"}'Example
Request
{
"entry": "spam@example.com",
"reason": "Known spam sender"
}Response
{
"entry": "spam@example.com",
"pod_id": "pod_abc123",
"direction": "receive",
"list_type": "block",
"created_at": "2025-01-15T12:00:00Z",
"entry_type": "email",
"organization_id": "org_xyz789"
}Endpoint
Quality
Full OpenAPI 3.1.0 schema with detailed component definitions, live MPP 402 challenge confirming the endpoint is operational, and clear pricing ($0.01/call). Docs pages on the MPP gateway return 404, but the OpenAPI spec and landing page provide sufficient detail. Response schema is well-defined via $ref to PodListEntry.
Warnings
- —No dedicated documentation pages found on the MPP gateway (docs/api/pricing all return 404)
- —The currency address in the MPP challenge is not a well-known stablecoin contract; price interpretation relies on the OpenAPI x-payment-info field which states 0.010000
- —Direction and ListType enum values are inferred from OpenAPI schema refs
Citations
- —The endpoint uses MPP protocol with Tempo settlement on chain ID 4217https://mpp.api.agentmail.to/v0/pods/:pod_id/lists/:direction/:type
- —Create List Entry is priced at 0.010000 (fixed) per the OpenAPI x-payment-infohttps://mpp.api.agentmail.to
- —Direction enum values are send, receive, reply; ListType enum values are allow, blockhttps://mpp.api.agentmail.to
- —AgentMail provides email inboxes for AI agents and raised $6M in seed fundinghttps://mpp.api.agentmail.to
- —Request body requires an entry field (email address or domain) with optional reasonhttps://mpp.api.agentmail.to