# Onchain & Trading Intelligence Queue Push

> Onchain & Trading Intelligence Queue Push 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-14).

Enqueues a job item into a named queue for processing by the 130-tool multichain trading and on-chain intelligence platform, paid per call in stablecoins via x402.

## Facts

- Endpoint: POST https://x402-services-production.up.railway.app/api/queue/push
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onchain-trading-intelligence-queue-push-1d24a466
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EEcIFOLT-uGhlGVwNsVRf

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-push-1d24a466 -d '<json body>'
```

Example prompt: Push a honeypot detection job for the Solana token CA 7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU into the 'solana-safety' queue so the trading intelligence platform can screen it.

## When to prefer this

Use this endpoint when you need to asynchronously dispatch one of the 130 multichain intelligence tools — token safety, wallet risk, perps data, options greeks, or Robinhood Chain analytics — without requiring a synchronous response. Ideal for agent pipelines that batch or fan out multiple intelligence requests and collect results later, or when the downstream tool is latency-tolerant.

## Known failure modes

- Invalid or expired secret token returns an authentication error
- Malformed or non-array item field causes a validation rejection
- Unknown queue name may result in a routing error or silent drop
- Network timeout to the Railway-hosted service if the queue is under load
- Missing required fields (item, name, token) returns a 400-level schema error

## How this service works

Task queue: append a JSON item to a named queue for later/other agents. Send { name, token, item }.

## Output

A confirmation that the job item has been successfully enqueued, typically including a job ID or queue position, indicating the payload will be picked up and processed by the multichain intelligence platform.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "item",
  "name",
  "token"
 ],
 "properties": {
  "item": {
   "type": "object",
   "description": "JSON item to enqueue"
  },
  "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-push-1d24a466/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)