> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Token Pairs

Look up token pairs on DEX Screener by chain and token addresses. Returns detailed pair data including price, volume, liquidity, transactions, price changes, and market cap. Accepts up to 30 comma-separated token addresses. Ideal for: real-time token price monitoring, liquidity analysis, volume tracking, building token dashboards.

![Get Token Pairs logo](https://ai-icon.b3.fun/logo/dexscreener)
Catalog action Blockchain Data

Look up token pairs on DEX Screener by chain and token addresses. Returns detailed pair data including price, volume, liquidity, transactions, price changes, and market cap. Accepts up to 30 comma-separated token addresses. Ideal for: real-time token price monitoring, liquidity analysis, volume tracking, building token dashboards.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `dexscreener-get-token-pairs` |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `dex`, `token`, `trading-pairs`, `price`, `liquidity`, `volume`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `chainId` | `string` | Yes | Chain identifier \(e.g. 'base', 'solana', 'bsc', 'ethereum'\) |
| `tokenAddresses` | `string` | Yes | Comma-separated token addresses to look up \(max 30\) |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `pairs` | `array` | Yes | Array of token pair data |

## Examples

**Workflow node**

```json
{
  "type": "dexscreener-get-token-pairs",
  "payload": {
    "chainId": "8453",
    "tokenAddresses": "0x0000000000000000000000000000000000000000"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/dexscreener-get-token-pairs/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "chainId": "8453",
    "tokenAddresses": "0x0000000000000000000000000000000000000000"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.