# Trending Pools by Network

> Trending Pools by Network is a paid API for AI agents from stablecrypto.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Returns trending liquidity pools on a specified blockchain network, with optional filtering and pagination

## Facts

- Endpoint: POST https://stablecrypto.dev/api/coingecko/onchain/network/trending
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/trending-pools-by-network-748d01cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vc_EGxozIHEghg7y2C0Cb

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 trending-pools-by-network-748d01cf -d '<json body>'
```

Example prompt: What are the trending liquidity pools on Ethereum right now — show me the first page of results?

## When to prefer this

Use this endpoint when you need trending pool data scoped to a specific blockchain network rather than cross-network trending data. Prefer this over the all-networks trending pools endpoint when the user has a specific chain in mind (e.g., Ethereum, Solana, Base). Choose this over general trending coins endpoints when you need liquidity pool-level detail rather than coin-level trends.

## Known failure modes

- Invalid or unsupported network ID returns empty data or error
- Network ID not recognized results in 400-level error
- Pagination out of range may return empty data array
- Malformed request body missing required 'network' field returns validation error
- Upstream CoinGecko API unavailability causes 503 or timeout

## How this service works

Pay-per-request access to CoinGecko, DefiLlama, Alchemy, and Etherscan APIs. No auth, no subscriptions.

## Output

An array of pool objects for the specified network, each containing on-chain pool metadata such as pool address, token pairs, volume, price change, and liquidity data sourced from CoinGecko's on-chain (GeckoTerminal) data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "page": {
   "type": "number"
  },
  "include": {
   "type": "string"
  },
  "network": {
   "type": "string",
   "description": "Network ID"
  },
  "duration": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trending-pools-by-network-748d01cf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stablecrypto.dev](https://www.zero.xyz/host/stablecrypto.dev/llms.txt)
