Market

What trades on each chain, and how far the read of it got.

Also for this capability: API · CLI · MCP · SDKs

What trades on each chain, and how far the read of it got.

Base URLhttps://api.hanzo.ai
Operations5
AuthAuthorization: Bearer $HANZO_API_KEY

Specification

Specification pending — no HIP in hanzoai/hips declares capability: market yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.

Four surfaces

SurfaceReaches this capability asCoverage
RESTmarket at its own prefix5 operations
CLIhanzo market …5 of 5
SDKMarketApi in every published client5 methods
MCPtool market on https://api.hanzo.ai/v1/mcp3 operations, 1 under the document's own id — ask describe for the rest

Quickstart

export HANZO_API_KEY=sk-...   # console.hanzo.ai → API keys

Then the first call — a read that needs nothing but the key. GET /v1/market/pools, operation get_market_pools:

hanzo market pools
import { Configuration, MarketApi } from 'hanzoai';

const api = new MarketApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getMarketPools();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import MarketApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MarketApi(client).get_market_pools()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.MarketAPI.GetMarketPools(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, market_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = market_api::get_market_pools(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MarketApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new MarketApi(client).getMarketPools();
curl https://api.hanzo.ai/v1/market/pools \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches market through the market tool, which names its 3 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_market_chains"
         }
       }
     }'

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
GET /v1/market/chainsAnswers every chain this deployment can read, what is deployed on each, and what its automated market maker amounts to.
GET /v1/market/poolsAnswers the automated market makers on one chain: their two tokens, their fee tier, and what has moved through each.
GET /v1/market/surveyAnswers which of the four settlement precompiles carry code on one chain.
GET /v1/market/tokenAnswers one token's daily history — open, high, low, close, price and volume per UTC day, oldest first.
GET /v1/market/tokensAnswers the tokens one chain's indexer has seen, with the decimals a caller needs to read any amount of one correctly.

All Hanzo APIs · Interactive reference

Was this page useful?