Crypto FX Market Data

finance

Serving

Current crypto prices and 24-hour change from CoinGecko, in the currency you choose. POST /v1/crypto with {ids, vs_currency} using CoinGecko coin ids (e.g. bitcoin, ethereum) and get one JSON object back. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/crypto-fx-market-data/v1/crypto
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

Derived from the published request schema.

curl -X POST https://agent.pocket.network/v1/crypto-fx-market-data/v1/crypto \
  -H 'content-type: application/json' \
  -d '{"ids":"bitcoin","vs_currency":"usd"}'

Example response

This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.

{}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Crypto FX Market Data accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/crypto`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "The request body for POST /v1/crypto.",
  "properties": {
    "ids": {
      "type": "string",
      "description": "Comma-separated CoinGecko coin ids, e.g. bitcoin,ethereum."
    },
    "vs_currency": {
      "type": "string",
      "description": "Quote currency, e.g. usd."
    }
  },
  "required": [
    "ids",
    "vs_currency"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/crypto, a JSON object with `prices` keyed by coin id (price and 24h change), vs, source and a cache flag. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field."
}