# 1cent URL Timing

> 1cent URL Timing is a paid API for AI agents from 1cent.maxzoa.ru, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-16).

Measures and returns end-to-end HTTP fetch timing for a given public URL, with optional cache bypass.

## Facts

- Endpoint: POST https://1cent.maxzoa.ru/v1/url/timing
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/1cent-url-timing-e8880fdf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Yynh9xy1d5KJYrLKC0Gl3

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 1cent-url-timing-e8880fdf -d '<json body>'
```

Example prompt: Can you measure the end-to-end fetch timing for https://example.com right now — I want a fresh reading, not a cached one.

## When to prefer this

Use this endpoint when you need a lightweight, server-side measurement of HTTP fetch latency for a public URL without browser overhead or JavaScript execution. Ideal for monitoring, benchmarking, or verifying response times of public APIs or web pages. Prefer over browser-based tools when you only need raw HTTP timing, not full page load metrics.

## Known failure modes

- Non-public or private URLs rejected — only public HTTP/HTTPS targets accepted
- URLs requiring JavaScript execution will not return JS-rendered timing
- Malformed or non-absolute URLs will fail validation
- Timeout if the target URL is unreachable or extremely slow
- Cache may return bounded stale results if fresh=false and cached data exists

## How this service works

Return measured end-to-end fetch timing. Only public HTTP(S) targets are accepted; JavaScript is not executed. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to reuse cache; set fresh=true only when a new upstream fetch is required.

## Output

Returns measured end-to-end fetch timing data for the specified public HTTP(S) URL, including latency metrics captured during the server-side fetch. JavaScript is not executed; only raw HTTP response timing is measured. Results may be cached unless fresh=true is specified.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "title": "Url",
   "examples": [
    "https://example.com"
   ],
   "maxLength": 2048,
   "minLength": 1,
   "description": "Public HTTP or HTTPS URL to inspect."
  },
  "fresh": {
   "type": "boolean",
   "title": "Fresh",
   "default": false,
   "examples": [
    false
   ],
   "description": "Set true only when a new upstream fetch is required; false allows a bounded cached response."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/1cent-url-timing-e8880fdf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 1cent.maxzoa.ru](https://www.zero.xyz/host/1cent.maxzoa.ru/llms.txt)