# Tempo Halowerk – Renderstart-Zeit Seite

> Tempo Halowerk – Renderstart-Zeit Seite is a paid API for AI agents from tempo.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Measures the time to first visible render start (Time to First Paint) for a given public web page URL.

## Facts

- Endpoint: POST https://tempo.halowerk.com/v1/pruef/tempo/renderstart/seite
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tempo-halowerk-renderstart-zeit-seite-8f7d8e82
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oGu4_tXftgsRdzg15G_Jh

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 tempo-halowerk-renderstart-zeit-seite-8f7d8e82 -d '<json body>'
```

Example prompt: Can you check how long it takes for https://www.example.com to show its first visible content — the time to render start?

## When to prefer this

Use this endpoint when you need to measure specifically the time to first visible render start (first paint latency) for a web page, particularly when building performance audits, CI/CD regression checks, or competitive benchmarking workflows. Prefer this over generic uptime or full-load-time checks when the user cares specifically about perceived render speed from a visitor's perspective.

## Known failure modes

- Non-public or unreachable URL returns an error or timeout
- Invalid URL format causes a validation rejection
- CSS selector matches no element, falls back to first match or returns an error
- Very slow or unresponsive target sites may cause measurement timeouts
- Rate limiting or bot-blocking on the target site may prevent accurate measurement

## How this service works

Prüft am Objekt seite den Befund Zeit bis zum sichtbaren Renderstart.

## Output

Returns the measured time (in milliseconds or seconds) until the first visible render event occurs when loading the specified page, giving a concrete front-end performance data point for render start latency.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ziel": {
   "oneOf": [
    {
     "type": "string",
     "maxLength": 2048,
     "minLength": 1,
     "description": "Öffentliche HTTP(S)-Adresse; bei DNS-Befunden Domain oder öffentliche IP."
    },
    {
     "type": "object",
     "required": [
      "adresse"
     ],
     "properties": {
      "adresse": {
       "type": "string",
       "maxLength": 2048,
       "minLength": 1
      },
      "selektor": {
       "type": "string",
       "maxLength": 240,
       "minLength": 1,
       "description": "CSS-Selektor: genau ein Objekt, sonst erster Treffer des Objektfilters."
      },
      "vergleich": {
       "type": "string",
       "maxLength": 2048,
       "description": "Öffentliche Vergleichsadresse für Link-, Sitemap- oder Sprachbefunde."
      },
      "user_agent": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_-]{1,80}$"
      },
      "dkim_selektor": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_-]{1,63}$"
      }
     },
     "additionalProperties": false
    }
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tempo-halowerk-renderstart-zeit-seite-8f7d8e82/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tempo.halowerk.com](https://www.zero.xyz/host/tempo.halowerk.com/llms.txt)