# APEX Faucet Volume Check

> APEX Faucet Volume Check is a paid API for AI agents from apexfaucet.xyz, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-03).

Returns on-chain trading volume and token metrics for a given X1 token mint address over a configurable time window

## Facts

- Endpoint: GET https://apexfaucet.xyz/api/x402/volume-check/%7Bmint%7D?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apex-faucet-volume-check-5d58bd3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qKcXuHFUDUClHoWfKMGPI

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 apex-faucet-volume-check-5d58bd3a
```

Example prompt: Can you check the trading volume and holder count for the APEX token (mint address Du6Z596DwGnfUcMSyRHSBQzNybiQKu8GESVfruEv9Jqr) on X1 over the last 48 hours?

## When to prefer this

Use this endpoint when you need quick token metrics (price, holders, volume tier) for a specific X1 network token by its mint address. It is ideal for pre-trade screening, token health checks, or monitoring activity on the X1/Arc ecosystem. Prefer this over generic blockchain explorers when you specifically need volume tier classification and holder counts in a single low-cost API call.

## Known failure modes

- Invalid or malformed mint address returns an error or ok:false
- Unknown mint address not indexed returns empty or null data
- Hours value outside 1–168 range is rejected
- Network or RPC issues on X1 may cause timeouts
- Payment failure via x402 protocol prevents endpoint access

## How this service works

Free APEX on X1, and free USDC plus APEX on Arc, three times a day. No gas, no sign-up. Plus a swap, a screener, APEX City and token checks.

## Output

A JSON object containing a boolean ok status, a data object with the token symbol, holder count, and USD price, the payment amount used, the volume tier label (e.g. 'cheap'), and the asset used for payment (e.g. 'USDC').

## 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"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "mint"
     ],
     "properties": {
      "mint": {
       "type": "string",
       "description": "X1 token mint address (base58), e.g. Du6Z596DwGnfUcMSyRHSBQzNybiQKu8GESVfruEv9Jqr (APEX)"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "hours": {
       "type": "string",
       "pattern": "^[0-9]{1,3}$",
       "description": "Window in hours, 1 to 168 (default 24)."
      }
     }
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "schema": {
  "type": "object",
  "properties": {
   "ok": {
    "type": "boolean"
   },
   "data": {
    "type": "object"
   },
   "paid": {
    "type": "number"
   },
   "tier": {
    "type": "string"
   },
   "asset": {
    "type": "string"
   }
  }
 },
 "example": {
  "ok": true,
  "data": {
   "symbol": "APEX",
   "holders": 9902,
   "priceUsd": 0.0000041
  },
  "paid": 0.01,
  "tier": "cheap",
  "asset": "USDC"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apex-faucet-volume-check-5d58bd3a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apexfaucet.xyz](https://www.zero.xyz/host/apexfaucet.xyz/llms.txt)