# x402 Crypto APIs – Coinbase Market Data (via x402 Micropayments)

> x402 Crypto APIs – Coinbase Market Data (via x402 Micropayments) is a paid API for AI agents from x402-crypto.vercel.app, paid per call via x402, $0.107667/call, status unknown (last checked 2026-09-15).

Fetches cryptocurrency market data (prices, candles, historical OHLCV) for a given product pair via Coinbase, paid per-call using x402 micropayments

## Facts

- Endpoint: POST https://x402-crypto.vercel.app/api/coinbase/%7Bpath%7D
- Price: $0.107667/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-crypto-apis-coinbase-market-data-via-x402-micropayments-441fdf4b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vJZcXq87aTKernZ7G5AXR

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-crypto-apis-coinbase-market-data-via-x402-micropayments-441fdf4b -d '<json body>'
```

Example prompt: Can you pull hourly candlestick data for BTC-USD from Coinbase from January 1, 2024 to January 31, 2024, using a granularity of 3600 seconds?

## When to prefer this

Choose this endpoint when you need historical or current OHLCV candlestick data for a specific Coinbase-listed cryptocurrency trading pair, especially when you want to pay per-call with no subscription using x402 micropayments. Prefer this over scraping or free-tier APIs when you need reliable, Coinbase-sourced market data with flexible granularity for trading analysis or backtesting.

## Known failure modes

- Invalid product ID returns an error or empty data (e.g. typo in BTC-USD)
- Invalid ISO 8601 date format causes a request failure
- Granularity value not supported by Coinbase returns an error
- Time range too large may be truncated or rejected
- Payment failure via x402 results in a 402 response before data is returned
- Missing required 'query' field returns a validation error

## How this service works

Paid cryptocurrency API endpoints via x402 micropayments

## Output

Returns a JSON object with a 'data' field containing the upstream Coinbase API response — typically an array of OHLCV candlestick records for the requested product and time range, including open, high, low, close, and volume values per candle interval.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "end": {
   "type": "string",
   "description": "End time for historical data (ISO 8601)"
  },
  "query": {
   "type": "string",
   "description": "Product ID or symbol (e.g. BTC-USD)"
  },
  "start": {
   "type": "string",
   "description": "Start time for historical data (ISO 8601)"
  },
  "granularity": {
   "type": "string",
   "description": "Candle granularity (e.g. 3600, 86400)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "description": "Response payload from the upstream API (structure varies by endpoint)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-crypto-apis-coinbase-market-data-via-x402-micropayments-441fdf4b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-crypto.vercel.app](https://www.zero.xyz/host/x402-crypto.vercel.app/llms.txt)