# Allium SQL Explorer Run Async

> Allium SQL Explorer Run Async is a paid API for AI agents from Allium at agents.allium.so, paid per call via x402 or MPP, $0.03/call, status unknown (last checked 2026-10-12, last successful call 2026-05-27).

Submit raw SQL for asynchronous execution against Allium's onchain blockchain data explorer

## Facts

- Endpoint: POST https://agents.allium.so/api/v1/explorer/queries/run-async?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402, MPP
- Status: unknown
- Last checked: 2026-10-12
- Last successful call: 2026-05-27
- Success rate: 33% of calls made through Zero
- Activations on Zero: 3
- 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-run-async-c1bd7436
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YGnrIu0RCul3on3hEUlG-

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-run-async-c1bd7436 -d '<json body>'
```

Example prompt: Submit this SQL for async execution on Allium's blockchain explorer: 'SELECT wallet_address, SUM(amount_usd) as total_volume FROM solana.transactions WHERE block_timestamp >= NOW() - INTERVAL 7 DAY GROUP BY wallet_address ORDER BY total_volume DESC LIMIT 100' — use the parameters map if any substitutions are needed.

## When to prefer this

Use this endpoint when you need to execute custom, ad-hoc raw SQL queries against Allium's blockchain data and the query may take longer than a synchronous response allows. Prefer this over saved-query endpoints when your SQL is dynamic or parameterized at runtime. Choose this when analyzing large onchain datasets across Solana, Base, or other supported chains where batch/async processing is appropriate.

## Known failure modes

- Invalid SQL syntax returns a 400 error with parse details
- Missing or malformed parameters object causes a validation error
- Query timeout for extremely large or unoptimized SQL scans
- Authentication failure (402 or 401) if payment or credentials are missing
- Rate limiting if too many concurrent async queries are submitted

## How this service works

Submit raw SQL for async execution

## Output

Returns a job/run identifier that can be used to poll the Status endpoint for completion and retrieve results once the async SQL query finishes executing against Allium's onchain blockchain dataset.

## Example request

```json
{
 "parameters": {
  "sql": "SELECT COUNT(*) as transaction_count, chain FROM transactions WHERE block_timestamp >= NOW() - INTERVAL '24 HOUR' GROUP BY chain LIMIT 10"
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "parameters": {
   "type": "object",
   "description": "Key-value map of query parameter substitutions",
   "additionalProperties": {
    "type": "string"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/allium-run-async-c1bd7436/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)