# unprice JSON Fetch API

> unprice JSON Fetch API is a paid API for AI agents from volkov.evgeny.m2.fvds.ru, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-10).

Fetches the JSON response body of any HTTP GET URL via a pay-per-request proxy, returning the parsed JSON data and HTTP status code.

## Facts

- Endpoint: GET https://volkov.evgeny.m2.fvds.ru/pay/json?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/unprice-json-fetch-api-b97e3112
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AIcbaZMrII7sCOwvfVo6A

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 unprice-json-fetch-api-b97e3112
```

Example prompt: Fetch the JSON response from https://httpbin.org/json for me using the unprice proxy.

## When to prefer this

Use this endpoint when you need to fetch and parse the JSON body of a public HTTP GET endpoint via a pay-per-request micropayment proxy, especially when you want to avoid managing API keys or subscriptions and prefer per-call USDC billing on Base via x402.

## Known failure modes

- Remote URL is unreachable or times out — may return a non-200 status
- Remote URL returns non-JSON content — response may fail to parse
- Invalid or malformed URL input — request rejected
- Payment failure via x402 — request not processed
- Remote server rate-limits or blocks the proxy IP

## How this service works

Tiny paid web services for agents. Pay per request with USDC on Base via x402, plus non-x402 Base USDC tx-hash checkouts for Merchant Feed Audit, Base USDC receipts, and recent wallet statements.

## Output

Returns a JSON object containing the requested URL, the parsed JSON data from the remote response, and the HTTP status code (e.g. {url, data, status}).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "url": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "url": "https://httpbin.org/json",
  "data": {},
  "status": 200
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/unprice-json-fetch-api-b97e3112/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from volkov.evgeny.m2.fvds.ru](https://www.zero.xyz/host/volkov.evgeny.m2.fvds.ru/llms.txt)