Skip to main content
Use the running API’s discovery documents when building a request. This keeps new routes, changed inputs and prices in one place.

Inspect an HTTP request

These reads are free. They need curl and jq, but no wallet:
Check the method, required query or body fields, enum values, amount units and any additional authorization.

LP pool APR

This unpaid request asks for the exact SPY/MU v4 pool on Robinhood Chain. It returns the payment challenge for a 0.001 USDC Base payment. Keep the same JSON body when repeating it with your payment authorization:
The chain, protocol, pool, ordered token addresses and hook must identify the pool exactly. A v3 pool uses its 20-byte pool address and a zero hook; a v4 pool uses its 32-byte PoolId. Read feeAprPct, incentiveAprPct and totalAprPct with status, retrievedAt, validUntil, source and components. Zero incentives means the pool has none; null means that component has no observation. The response also includes assessment, a check of the pool’s identity, tokens and hook. Read assessment.recommendation.status (ELIGIBLE_FOR_COMPARISON, REQUIRES_REVIEW, BLOCKED or UNAVAILABLE) with its reasons. Inspect the live declared output schema for the full shape. For position context, inspect the POST /lp-intelligence schema and supply a position containing chainId, positionManager and tokenId. It costs 0.02 USDC on Base. Pool APR appears in advice.details.yield. The HTTP guide explains how to read the rates.

Inspect the payment and declared output

An unpaid request to a paid route returns a 402 challenge. Decode its PAYMENT-REQUIRED header:
accepts supplies the price, network, token and recipient for that call. Where advertised, extensions.bazaar supplies the declared output schema and example. A successful paid call returns the actual result. A 402 does not prove your input is valid: some routes evaluate payment before parameter validation. Read the request schema before you pay. The HTTP guide explains how to read the result. For a paid request, follow HTTP API.