# AgentMail Create List Entry

> AgentMail Create List Entry is a paid API for AI agents from AgentMail at mpp.api.agentmail.to, $0.01/call, status unknown (last checked 2026-10-12).

Adds an email address or domain to an allow or block list for a specific email direction (send, receive, or reply)

## Facts

- Endpoint: POST https://mpp.api.agentmail.to/v0/lists/:direction/:type?utm_source=zero.xyz
- Price: $0.01/call
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Provider: AgentMail
- Docs: https://docs.agentmail.to
- Website: https://agentmail.to
- Tags: email, inboxes, domains, drafts, threads, webhooks, messaging, ai, social
- Canonical page: https://www.zero.xyz/c/agentmail-type-fd04be6c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RtyTaQrCLw77Iz24Z1u38

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentmail-type-fd04be6c -d '<json body>'
```

Example prompt: Add the domain 'spam.example.com' to my AgentMail block list for incoming emails — they keep sending junk and I want to stop receiving anything from them.

## When to prefer this

Use this endpoint when you need to programmatically manage allow or block lists for an AgentMail inbox — specifically when controlling which email addresses or domains are permitted or blocked for sending, receiving, or replying. Prefer this over manual inbox configuration when automating email access control for AI agents.

## Known failure modes

- Invalid email address or domain format returns a 400 validation error
- Missing required 'entry' field returns a 400 bad request
- Invalid direction or type path parameter returns a 404 or 400 error
- Unauthorized or missing Bearer token returns a 401 error
- Duplicate entry may return a 409 conflict error

## How this service works

Create List Entry

## Output

Returns a ListEntry object confirming the newly created entry, including the email or domain added, the direction (send/receive/reply), the list type (allow/block), whether it is an email or domain entry, the organization ID, and the creation timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "title": "CreateListEntryRequest",
 "required": [
  "entry"
 ],
 "properties": {
  "entry": {
   "type": "string",
   "description": "Email address or domain to add."
  },
  "reason": {
   "type": "string",
   "description": "Reason for adding the entry."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "title": "ListEntry",
 "required": [
  "entry",
  "organization_id",
  "direction",
  "list_type",
  "entry_type",
  "created_at"
 ],
 "properties": {
  "entry": {
   "type": "string",
   "description": "Email address or domain of list entry."
  },
  "reason": {
   "type": "string",
   "description": "Reason for adding the entry."
  },
  "direction": {
   "enum": [
    "send",
    "receive",
    "reply"
   ],
   "type": "string",
   "title": "Direction",
   "description": "Direction of list entry."
  },
  "list_type": {
   "enum": [
    "allow",
    "block"
   ],
   "type": "string",
   "title": "ListType",
   "description": "Type of list entry."
  },
  "created_at": {
   "type": "string",
   "format": "date-time",
   "description": "Time at which entry was created."
  },
  "entry_type": {
   "enum": [
    "email",
    "domain"
   ],
   "type": "string",
   "title": "EntryType",
   "description": "Whether the entry is an email address or domain."
  },
  "organization_id": {
   "type": "string",
   "title": "OrganizationId",
   "description": "ID of organization."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentmail-type-fd04be6c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mpp.api.agentmail.to](https://www.zero.xyz/host/mpp.api.agentmail.to/llms.txt)