# apexfaucet.xyz X1 Token Trade History

> apexfaucet.xyz X1 Token Trade History is a paid API for AI agents from apexfaucet.xyz, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).

Returns up to 200 recent on-chain trades for a specific X1 token, ordered newest first, with timestamps, sides, amounts, mints, trader addresses, and transaction signatures.

## Facts

- Endpoint: GET https://apexfaucet.xyz/api/x402/trades/:mint?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apexfaucet-xyz-x1-token-trade-history-ffb747f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ir_rsHE_2bv7kxVMB6MPw

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 apexfaucet-xyz-x1-token-trade-history-ffb747f1
```

Example prompt: Pull the last 100 trades for the X1 token at mint address 0xAbC123... so I can see who's been buying and selling it and verify the transactions on-chain.

## When to prefer this

Choose this endpoint when you need recent trade-level granularity for a specific X1 token — including exact amounts, wallet addresses, and verifiable transaction signatures — sourced from an internally indexed history rather than a third-party API. Prefer it over the global all-tokens feed when you want trades scoped to a single mint, and over blockchain explorers when you need a structured, pageable JSON response ready for agent consumption.

## Known failure modes

- Invalid or non-existent mint address returns empty array or 404
- limit parameter exceeding 200 is capped silently at 200
- Token with fewer trades than requested returns only available rows
- Malformed mint address returns 400 bad request
- Payment failure (insufficient USDC balance) returns 402 Payment Required

## How this service works

Recent on-chain trades for one X1 token, newest first: timestamp, side, the amounts and mints on both legs, the trader address and the transaction signature, so every row can be checked on chain yourself. Returns up to 200 rows (?limit=N, default 50, hard cap 200) or fewer when the token has traded less than that. Read from our own indexed trade history, not from a third-party API.

## Output

A JSON array of up to 200 trade records (default 50), each containing: trade timestamp, side (buy or sell), input amount, output amount, input token mint, output token mint, trader wallet address, and transaction signature for on-chain verification. Results are ordered newest first and drawn from an internally indexed trade history.

## 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)"
      }
     }
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apexfaucet-xyz-x1-token-trade-history-ffb747f1/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)