# Hubble RPC Natural Language Blockchain Query

> Hubble RPC Natural Language Blockchain Query is a paid API for AI agents from x402.bedev.hubble-rpc.xyz, paid per call via x402, $0.05/call, status down (last checked 2026-09-15).

Query Hubble blockchain data on Solana using plain natural language questions and receive structured results

## Facts

- Endpoint: POST https://x402.bedev.hubble-rpc.xyz/lego/api/v1/query
- Price: $0.05/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-bedev-hubble-rpc-xyz-98d458fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J3O6pF7M3mg4SJatAlABm

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 x402-bedev-hubble-rpc-xyz-98d458fc -d '<json body>'
```

Example prompt: Ask the Hubble RPC what the current total value locked in Hubble Protocol on Solana is, and get back the latest on-chain data.

## When to prefer this

Use this endpoint when you need to query Hubble Protocol or Solana blockchain data using natural language rather than raw RPC calls or SQL — ideal when the query structure is unknown or when building conversational interfaces over DeFi data without needing to write structured queries.

## Known failure modes

- Ambiguous natural language query returns empty or irrelevant data array
- Query outside Hubble/Solana domain scope returns no results
- Malformed query string causes success:false with empty data
- Rate limiting or payment failure results in HTTP 402 or 429
- Network timeout for complex on-chain data lookups

## How this service works

Query Hubble blockchain data with natural language. Supports Solana

## Output

Returns a JSON object with a 'data' array containing query results, a 'success' boolean indicating whether the query succeeded, and an ISO 8601 timestamp of when the query was executed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "array",
   "description": "Query results"
  },
  "success": {
   "type": "boolean",
   "description": "Whether the query was successful"
  },
  "timestamp": {
   "type": "string",
   "description": "ISO 8601 timestamp"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-bedev-hubble-rpc-xyz-98d458fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.bedev.hubble-rpc.xyz](https://www.zero.xyz/host/x402.bedev.hubble-rpc.xyz/llms.txt)