# Paxie.fun Robinhood Chain Token Precall Data

> Paxie.fun Robinhood Chain Token Precall Data is a paid API for AI agents from api.paxie.fun, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-14).

Returns pre-call signal data for a specific Robinhood Chain token address, including buyer burst metrics, run scores, cluster flags, and rug check indicators captured before a trading signal fires.

## Facts

- Endpoint: GET https://api.paxie.fun/v1/rh/token/%7Baddr%7D/precall?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paxie-fun-robinhood-chain-token-precall-data-70732feb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qMLlJx-_nhLKG0Tp8PY37

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 paxie-fun-robinhood-chain-token-precall-data-70732feb
```

Example prompt: Can you pull the precall signal data for Robinhood Chain token 0x7c3e9a41d0b25f8e6a1c4d93b07e2f5a8c61d4b2 — I want to see the buyer burst count, run60 score, cluster flags, and how many wallets bought in the same block before I decide anything.

## When to prefer this

Use this endpoint when you need precall signal features for a specific Robinhood Chain token address before making a trading or routing decision. It is the right choice when you want front-run cluster detection, run60 momentum scores, and wallet-level burst data at the moment of signal posting, and you want to pay per call with no API key overhead. Prefer it over generic DEX data APIs when you specifically need Paxie's burst and rug-signal scoring on Robinhood Chain Uniswap pools.

## Known failure modes

- Invalid or malformed token address returns an error or empty precall object
- Token not tracked by Paxie (not a Uniswap v3/v4 ETH-quoted pool created in last 24h) returns no data
- Payment via x402 fails if USDC balance insufficient on Base or Solana
- Data lag up to 30s means very recently launched tokens may not yet appear
- Precall data may be null if token is too new and burst has not yet been detected
- signal+seconds fields will be null until 5-60s after signal fires

## How this service works

Launch data for Robinhood Chain and Solana, updated every 20 s (≤30 s lag). Robinhood Chain: every ETH-quoted Uniswap v4 and v3 pool created in the last 24 h. Solana: pump.fun tokens 5 min to 4 h old that show curve progress. Buyer bursts, a rug check on who holds each pool's liquidity (per burst, and per token before you buy), new pools, per-minute flow, repeat-buyer crews and copy-leader replays. Robinhood signals are scored 30 minutes later, Solana ones at graduation or 20 minutes, rugs counted. Data, not trading advice. Paid per call with x402 (USDC on Base or Solana); no API keys. Every schema property carries x-available: signal = Known when the burst fires. Safe to use as a feature. signal+seconds = Filled 5-60 s after the signal, computed from chain state as of the signal block. Safe as a feature once present; null until then. signal+30m = Outcome. Exists only after the scoring window closes (Robinhood 30 min; Solana graduation or 20 min). Never use as a feature: a backtest that does uses the future. now = Current state as of the response's generatedAt (or the row's checkedAt). Not tied to a signal. Errors (4xx/5xx) are never charged. /v1 is canonical; the original paid paths are also served unversioned.

## Output

Returns a JSON object containing the chain identifier, scoring rules, token address, token age in seconds, and a detailed precall object with buyer count, ETH volume, wallet count and list, run60 score, 1-hour price change, same-block wallet count, cluster and run flags, posted and captured timestamps, and whether the data is resolved — plus schema version and generation timestamp.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "robinhood",
  "rules": {
   "run": "ran >= 3x over the hour before the post (run60; DexScreener h1 change as fallback when the pool was not tracked)",
   "young": "token < 30 min old when the call was posted",
   "cluster": ">= 5 distinct wallets bought in ONE block in the 10 min before the post (front-run cluster)",
   "thresholds": {
    "maxRun60": 3,
    "windowMin": 10,
    "minAgeAtCallMin": 30,
    "sameBlockWallets": 5
   }
  },
  "token": "0x7c3e9a41d0b25f8e6a1c4d93b07e2f5a8c61d4b2",
  "ageSec": 12,
  "precall": {
   "buys": 23,
   "flags": [
    "run",
    "cluster"
   ],
   "run60": 3.4,
   "token": "0x7c3e9a41d0b25f8e6a1c4d93b07e2f5a8c61d4b2",
   "buyEth": 1.84,
   "chg1h0": 240,
   "symbol": "HOOD",
   "tracked": true,
   "wallets": 17,
   "postedAt": 1791568400000,
   "resolved": 30,
   "capturedAt": 1791568460000,
   "runFromMin": 58,
   "walletList": [
    "0x5e2a9c1d7f30b84e6a2d1c9f8b3e07a4d6c5f2b1"
   ],
   "ageAtCallMin": 41.2,
   "sameBlockMaxTx": 6,
   "walletsResolved": true,
   "sameBlockWallets": 6
  },
  "generatedAt": 1791570200000,
  "schemaVersion": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/paxie-fun-robinhood-chain-token-precall-data-70732feb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.paxie.fun](https://www.zero.xyz/host/api.paxie.fun/llms.txt)