# Allium Query Run Status Check

> Allium Query Run Status Check is a paid API for AI agents from Allium at agents.allium.so, paid per call via MPP, $0.01/call, status unknown (last checked 2026-10-11).

Polls the status of a previously submitted async SQL query run on Allium's blockchain data explorer

## Facts

- Endpoint: GET https://agents.allium.so/api/v1/explorer/query-runs/:run_id/status?utm_source=zero.xyz
- Price: $0.01/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Provider: Allium
- Docs: https://docs.allium.so
- Website: https://allium.so
- Tags: blockchain, prices, tokens, wallet, balances, transactions, pnl, sql, explorer, solana, base, defi, data
- Canonical page: https://www.zero.xyz/c/allium-status-579dc008
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9beopSeADCEyALuw7OIJu

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 allium-status-579dc008
```

Example prompt: Can you check whether my Allium query run with ID 'run_abc123' has finished executing yet?

## When to prefer this

Use this endpoint after submitting an async SQL query via Allium's Run Async endpoint to poll for completion before fetching results. Essential in any polling loop where you need to know when a long-running blockchain data query is ready.

## Known failure modes

- Invalid or non-existent run_id returns a 404 not found error
- Expired run_id (run purged from system) returns a 404 or 410 gone response
- Unauthorized access to another user's run_id returns a 403 forbidden
- Network or service errors return 500 with no status information

## How this service works

Check status of a query run

## Output

Returns the current execution status of the specified query run — e.g. pending, running, completed, or failed — allowing the agent to determine whether results are ready to fetch.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "addresses": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "token_address",
     "chain"
    ],
    "properties": {
     "chain": {
      "type": "string",
      "description": "Blockchain network (e.g. ethereum, solana, base)"
     },
     "token_address": {
      "type": "string",
      "description": "Token contract address"
     }
    }
   }
  },
  "timestamp": {
   "type": "string",
   "format": "date-time",
   "description": "ISO 8601 timestamp"
  },
  "time_granularity": {
   "enum": [
    "15s",
    "1m",
    "5m",
    "1h",
    "1d"
   ],
   "type": "string",
   "description": "Time granularity for price buckets"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/allium-status-579dc008/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.allium.so](https://www.zero.xyz/host/agents.allium.so/llms.txt)