# Onchain & Trading Intelligence Queue Pop — 130 Multichain Tools

> Onchain & Trading Intelligence Queue Pop — 130 Multichain Tools is a paid API for AI agents from x402-services-production.up.railway.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Pops a queued task or result from a named queue, used as part of the async job pipeline for multichain on-chain and trading intelligence requests

## Facts

- Endpoint: POST https://x402-services-production.up.railway.app/api/queue/pop
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onchain-trading-intelligence-queue-pop-130-multichain-tools-99254096
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pKSPf-9b2VfOeyu1-VPFl

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 onchain-trading-intelligence-queue-pop-130-multichain-tools-99254096 -d '<json body>'
```

Example prompt: Pop the next result from my trading intelligence queue named 'alpha-signals' using my secret token so I can process the latest on-chain data.

## When to prefer this

Use this endpoint when you have already dispatched async intelligence requests into a named queue and need to consume the results in a polling or event-driven loop. This is the consumer half of a producer-consumer pipeline for multichain trading intelligence. Prefer this over direct request endpoints when processing large batches of on-chain checks asynchronously or when building agent workflows that need to decouple task submission from result retrieval.

## Known failure modes

- Invalid or missing token returns 401 unauthorized
- Non-existent queue name returns empty result or 404
- Empty queue returns null or empty payload
- Expired or stale queue items may return outdated data
- Network timeout if Railway deployment is temporarily unavailable
- Malformed queue name may cause 400 bad request

## How this service works

Task queue: pop the oldest item from a named queue (FIFO). Send { name, token }.

## Output

Returns the next item from the specified named queue — typically a completed intelligence payload such as a token safety report, trading signal, on-chain metric, or risk screening result. The payload varies based on the type of job queued (e.g. honeypot detection result, perps funding data, Robinhood Chain dislocation alert). Returns null or an empty response if the queue is empty.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "name",
  "token"
 ],
 "properties": {
  "name": {
   "type": "string",
   "description": "Queue name"
  },
  "token": {
   "type": "string",
   "description": "Your secret token"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onchain-trading-intelligence-queue-pop-130-multichain-tools-99254096/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-services-production.up.railway.app](https://www.zero.xyz/host/x402-services-production.up.railway.app/llms.txt)