# Tempo Halowerk – Redirect Time to First Render (Weiterleitung/Renderstart)

> Tempo Halowerk – Redirect Time to First Render (Weiterleitung/Renderstart) 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-16).

Measures the time to first visible render (renderstart) for a redirect/forwarding target URL.

## Facts

- Endpoint: POST https://tempo.halowerk.com/v1/pruef/tempo/renderstart/weiterleitung
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tempo-halowerk-redirect-time-to-first-render-weiterleitung-renderstart-bd474071
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9KVVdjhCBIFLluhEVLI9N

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-redirect-time-to-first-render-weiterleitung-renderstart-bd474071 -d '<json body>'
```

Example prompt: Check how long it takes for https://example.com/old-path to show its first visible render after the redirect — I want the renderstart time for that forwarding URL.

## When to prefer this

Use this endpoint specifically when you need to measure the time-to-first-render (renderstart) for a URL that involves a redirect or forwarding step, as opposed to general page load time, TTFB, DNS resolution, or TLS handshake metrics. Prefer this over generic web performance tools when you need granular, single-metric redirect render timing via a pay-per-call API.

## Known failure modes

- Target URL is unreachable or returns a non-2xx/3xx status, causing measurement failure
- URL does not actually perform a redirect, making the redirect-specific metric inapplicable
- Target page has rendering blocked by JavaScript or heavy resources, skewing results
- Invalid CSS selector provided in the input object causes selector resolution failure
- URL exceeds maxLength of 2048 characters, rejected at validation
- Private/internal IP addresses or localhost URLs rejected as non-public

## How this service works

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

## Output

Returns a measurement of the time elapsed until the first visible render (renderstart) when accessing the given URL that involves a redirect or forwarding step, expressed as a duration metric.

## 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-redirect-time-to-first-render-weiterleitung-renderstart-bd474071/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)