Crest Crypto Market DataGET /data/prices · x402 API by Crest x402 Data
Real-time crypto prices, market caps, 24h/7d changes, gas prices across chains, trending tokens, DeFi TVL, funding rates, liquidations, NFT floors, and DEX pairs for AI agents. USDC pay-per-call on Base, no API keys.
What does this x402 API do?
Crest Crypto Market Data. This is an x402-gated GET API resource from Crest x402 Data. The latest safe availability check could not reach the resource on 2026-08-04. No normalized USD price is recorded; the listing names Base. No settled paid call has been verified.
- Published price
- No normalized USD price is recorded
- Networks
- Base
- Latest evidence
- The latest safe availability check could not reach the resource on 2026-08-04
- Resource ID
- 3779c3abf0669a2ea018356d
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://data.crestsystems.ai/data/prices", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Exact route checked
skipped origin unreachable · origin-check:UNSAFE_URL_ENOTFOUND: https://data.crestsystems.ai/
- Origin unavailable
UNSAFE_URL_ENOTFOUND: https://data.crestsystems.ai/
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: healthy.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is No normalized USD price is recorded. Raw protocol requirements remain visible below for implementation and audit use.