# Red Web Utils - Deployer Info Lookup

> Red Web Utils - Deployer Info Lookup is a paid API for AI agents from red-web-utils.agent-tools-x402.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-07).

Looks up on-chain deployer address activity, including trading pairs created, token addresses, and first/last seen timestamps on a DEX.

## Facts

- Endpoint: POST https://red-web-utils.agent-tools-x402.workers.dev/api/deployer?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-07
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/red-web-utils-deployer-info-lookup-a35f0f0a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sNPnbNjDFaTLa3sAQ_HQG

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 red-web-utils-deployer-info-lookup-a35f0f0a -d '<json body>'
```

Example prompt: Can you look up the deployer history for address 0xAbC123... on the DEX — I want to see what trading pairs they've created, which tokens are involved, and when they were first and last active?

## When to prefer this

Use this endpoint when you need to audit or profile a specific deployer address on a DEX — particularly to discover what trading pairs they have created, when they first and last appeared, and which tokens they have launched. Prefer this over generic blockchain explorers when you need structured, agent-ready JSON output specifically about DEX pair creation history for a deployer.

## Known failure modes

- Unknown or unindexed deployer address returns empty pairs array
- Invalid address format may return an error or empty result
- Address with no DEX activity returns zero pairs created
- Network or worker timeout if the underlying data source is slow
- Payment failure via x402 prevents the call from completing

## How this service works

Pay-per-call web and onchain utilities for AI agents (MPP + x402, USDC on Base).

## Output

Returns a JSON object containing the deployer's address, first and last seen timestamps, total number of pairs created, and an array of pair objects each with a timestamp, pair contract address, token0 address, and token1 address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "address": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "pairs": [
   {
    "ts": "...",
    "pair": "0x...",
    "token0": "0x...",
    "token1": "0x..."
   }
  ],
  "address": "0x...",
  "lastSeen": "2026-10-27T00:00:00.000Z",
  "firstSeen": "2026-10-20T00:00:00.000Z",
  "pairsCreated": 3
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/red-web-utils-deployer-info-lookup-a35f0f0a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from red-web-utils.agent-tools-x402.workers.dev](https://www.zero.xyz/host/red-web-utils.agent-tools-x402.workers.dev/llms.txt)