# Zumpay Aero Signals API

> Zumpay Aero Signals API is a paid API for AI agents from aero-signals.zumpay.com.ar, paid per call via x402, $0.01/call, status down (last checked 2026-10-22).

Returns live Aerodrome DEX liquidity and whale-signal data for pools on the Base blockchain, paid per call via x402.

## Facts

- Endpoint: GET https://aero-signals.zumpay.com.ar/v1/signals/live?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zumpay-aero-signals-api-682dd11f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eSJtREiFhhZOnHVgvGzJ6

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 zumpay-aero-signals-api-682dd11f
```

Example prompt: Pull the latest live whale and liquidity signals from the Aerodrome pools on Base right now — I want to see what big moves are happening across the DEX.

## When to prefer this

Choose this endpoint when you need real-time, per-call Aerodrome DEX liquidity and whale-signal intelligence specifically on the Base network, especially inside an AI agent workflow that can handle x402 micropayments. It is ideal for trading bots, DeFi dashboards, or alert systems that need fresh on-chain signal data on demand rather than a subscription WebSocket feed.

## Known failure modes

- Payment not included or insufficient USDC balance (402 Payment Required)
- Invalid or malformed filter properties in request (400 Bad Request)
- Upstream Aerodrome data feed unavailable causing stale or empty data array
- Rate limiting if too many calls made in quick succession
- Network congestion on Base chain causing delayed signal data

## How this service works

Paid Aerodrome liquidity and whale-signal API for AI agents monitoring Base pools.

## Output

Returns a JSON object with status, product name, network, DEX identifier, feed type, signal count, an array of live signal data entries (liquidity and whale events), and a Unix timestamp of the response.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {
  "type": "object",
  "required": [
   "status",
   "product",
   "network",
   "dex",
   "feed",
   "count",
   "data",
   "timestamp"
  ],
  "properties": {
   "dex": {
    "type": "string"
   },
   "data": {
    "type": "array"
   },
   "feed": {
    "type": "string"
   },
   "count": {
    "type": "integer"
   },
   "status": {
    "type": "string"
   },
   "network": {
    "type": "string"
   },
   "product": {
    "type": "string"
   },
   "timestamp": {
    "type": "integer"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zumpay-aero-signals-api-682dd11f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aero-signals.zumpay.com.ar](https://www.zero.xyz/host/aero-signals.zumpay.com.ar/llms.txt)
