# AgentMail List Management Lookup

> AgentMail List Management Lookup is a free API for AI agents from x402.api.agentmail.to, callable via x402, Free, status unknown (last checked 2026-09-08).

Looks up a specific entry in an email list by direction, type, and entry identifier

## Facts

- Endpoint: GET https://x402.api.agentmail.to/v0/lists/%7Bdirection%7D/%7Btype%7D/%7Bentry%7D
- Price: Free
- Payment: x402
- Status: unknown
- Last checked: 2026-09-08
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentmail-list-management-lookup-7f38a4c7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_s-Kbh56_jiFYed-hVO5Gp

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-list-management-lookup-7f38a4c7
```

Example prompt: Check AgentMail's list records to see if the entry 'noreply@example.com' is on an inbound blocklist — look it up by direction 'inbound', type 'blocklist', and entry 'noreply@example.com'.

## When to prefer this

Use this endpoint when an AI agent needs to verify whether a specific email address or identifier appears in a particular directional list (e.g. inbound/outbound blocklist, allowlist) within an AgentMail workspace. Prefer this over listing all entries when the exact entry is known and only a single lookup is needed.

## Known failure modes

- Entry not found — returns 404 if the specified direction/type/entry combination does not exist
- Invalid direction or type values — returns 400 if path parameters are not recognized enum values
- Authentication failure — returns 401 or 402 if payment or credentials are missing
- Empty response body — the example schema is empty, so parsing logic must handle sparse responses

## How this service works

AgentMail gives AI agents real email inboxes. Create, send, receive, and search messages via REST API — built for autonomous agents and agentic workflows.

## Output

Returns a JSON object containing the details of the specified list entry, including its direction, type, and entry value. The response schema is open-ended but confirms whether the entry exists and what properties are associated with it.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "pathParams"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "direction",
      "type",
      "entry"
     ],
     "properties": {
      "type": {
       "type": "string"
      },
      "entry": {
       "type": "string"
      },
      "direction": {
       "type": "string"
      }
     },
     "additionalProperties": false
    },
    "queryParams": {
     "type": "object",
     "properties": {},
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   },
   "additionalProperties": false
  }
 },
 "additionalProperties": false
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentmail-list-management-lookup-7f38a4c7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.api.agentmail.to](https://www.zero.xyz/host/x402.api.agentmail.to/llms.txt)