Agent Query Layer Skill Pack

---
name: agent-query-layer-skill-pack-864868b252bc
description: Use Agent-Query-Layer through gateway REST, WebSocket, and hosted JSON-RPC surfaces.
---

# Agent Query Layer Skill Pack

Use this skill when you need Agent-Query-Layer market-read or realtime workflows through gateway-owned hosted product surfaces.

This skill is a host-side wrapper and onboarding layer. It is not the capability contract.
It should still teach the host enough supported capability vocabulary to route common requests accurately.

For the currently backed service catalog and request routing guidance, use `references/capabilities.md`.

## Host Setup

- Create a workspace API key in portal `Dashboard Keys` before using hosted gateway access.
- Expose that key through the host environment variable referenced by your skill config, for example `AQL_WORKSPACE_API_KEY`.
- Configure the hosted gateway base URL at `https://gw-aql.tomo.services`.
- Configure gateway WebSocket subscriptions at `wss://gw-aql.tomo.services/v1/market/wss`.
- Authenticate hosted traffic with `Authorization: Bearer <workspace_api_key>`.
- Use gateway `REST` for request-response market reads, gateway `WebSocket` for live subscriptions, and gateway `JSON-RPC` for raw chain compatibility.
- Raw chain compatibility also supports path-style hosted access for enabled chains, for example `/v1/ethereum/{api_key}`, `/v1/base/{api_key}`, and `/v1/solana/{api_key}`.
- If your workspace setup explicitly includes a private MCP companion at `https://mcp-aql.tomo.services`, keep it separate and treat it as optional.
- Treat `workspace_id` as a diagnostic label, not as hosted auth.

## Test Deployment

- Current test gateway URL: `http://43.135.176.179:8080`.
- Current test gateway WebSocket URL: `ws://43.135.176.179:8080/v1/market/wss`.
- Use the same bearer-auth contract when validating the test node.
- Treat the test-node URLs as validation endpoints, not as the default published hosted URLs.

## Wrapper Boundary

- Use this skill to steer the host toward gateway-owned `REST` routes for canonical market reads.
- Use this skill to steer the host toward gateway-owned `WebSocket` subscriptions for live market events.
- Use this skill to steer the host toward gateway-owned `JSON-RPC` routes for raw chain compatibility.
- Do not treat a private MCP companion as the default product path after install.
- Do not connect directly to upstream providers from this skill.

## Supported Market Services

- Gateway `REST` asset identity reads through `https://gw-aql.tomo.services/v1/market/asset-profile`.
- Gateway `REST` market identity reads through `https://gw-aql.tomo.services/v1/market/market-profile`.
- Gateway `REST` latest price reads through `https://gw-aql.tomo.services/v1/market/price-snapshot`.
- Gateway `REST` short-range OHLCV reads through `https://gw-aql.tomo.services/v1/market/ohlcv-window`.
- Gateway `WebSocket` realtime delivery through `wss://gw-aql.tomo.services/v1/market/wss` for supported live event targets.
- Gateway raw EVM compatibility through `https://gw-aql.tomo.services/v1/{chain}/{api_key}` or internal raw routes such as `https://gw-aql.tomo.services/rpc/bnbchain` and `https://gw-aql.tomo.services/rpc/base`.
- Gateway raw Solana compatibility remains beta through `https://gw-aql.tomo.services/v1/solana/{api_key}` or `https://gw-aql.tomo.services/rpc/solana`.

Current boundary:

- Phase 1 keeps DEX token and pool reads as the richer current path.
- Current public EVM market-read chains are `ethereum`, `bnbchain`, `base`, `arbitrum`, `optimism`, `polygon`.
- Solana remains beta or experimental in user-facing copy unless the public docs explicitly promote it.
- Gateway `REST` now also exposes live minimal symbol-first CEX market-read support through canonical `asset_profile`, `market_profile`, `price_snapshot`, and `ohlcv_window` queries.
- Gateway `WebSocket` is for live market delivery, but current realtime target support should still be treated as DEX-first unless later contract docs say otherwise.
- Discovery-heavy requests such as trending, gainers, or new listings are not part of the current skill-pack promise.

## Request Routing Guide

- If the user asks for `the latest token price`, prefer gateway `GET /v1/market/price-snapshot`.
- If the user asks for `candles`, `ohlcv`, `chart`, or `price window`, prefer gateway `GET /v1/market/ohlcv-window`.
- If the user asks for `token metadata`, `symbol`, `name`, or `profile`, prefer gateway `GET /v1/market/asset-profile` or `GET /v1/market/market-profile`.
- If the user asks for live price or short-range OHLCV updates, prefer gateway `WebSocket` subscribe flow on `/v1/market/wss`.
- If the user provides a Base `0x...` token address, route market reads with `market_kind=dex&chain=base&address=...`.
- A Base token address should route as `market_kind=dex&chain=base&address=...` for market reads.
- If the gateway returns an error for a supported-looking chain or address, report the actual gateway response instead of claiming the chain is unsupported from memory.
- If the user asks for raw chain calls, prefer compatibility URLs such as `POST /v1/base/{api_key}` or use internal raw routes such as `POST /rpc/base` when bearer-auth routing is required.
- Use `POST /rpc/bnbchain` or `POST /rpc/solana` only when the host specifically needs bearer-auth internal raw routes.
- If a separately provisioned private MCP companion is explicitly available, use it only for that companion workflow rather than as the standard hosted path.

## Code And Query Expectations

- Prefer gateway `REST` for request-response market reads.
- Prefer gateway `WebSocket` for live market subscriptions.
- Use gateway `JSON-RPC` only when the caller needs raw chain compatibility semantics.
- Use bearer auth and issued product endpoints in all generated examples.
- When writing sample code, show concrete `chain` plus `address` inputs for DEX market requests.
- For CEX examples, use concrete `symbol` plus `market` inputs such as `BTCUSDT` and `spot`.
- Do not invent support for trending, discovery, portfolio, or execution features that are not present in the current service catalog.

## References

- [Capabilities](references/capabilities.md)
- [Hosted Access](references/hosted-access.md)
- [Quickstart](references/quickstart.md)
- Repository gateway API inventory: `docs/standards/agent-api-inventory.md`