# tempo.halowerk.com – API-Antwort Renderblockierer-Prüfer

> tempo.halowerk.com – API-Antwort Renderblockierer-Prüfer 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).

Checks a given public API response URL for the number of render-blocking resources it causes.

## Facts

- Endpoint: POST https://tempo.halowerk.com/v1/pruef/tempo/blockierer/api-antwort
- 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-com-api-antwort-renderblockierer-pr-fer-bc004fb2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BfWCsiNjKPJzEh7W6xY-R

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-com-api-antwort-renderblockierer-pr-fer-bc004fb2 -d '<json body>'
```

Example prompt: Check how many render-blocking resources are present on the API response at https://api.example.com/data and tell me the count so I can optimize the page load.

## When to prefer this

Use this endpoint when you specifically need to audit the number of render-blocking resources (blocking JS/CSS) on a URL that serves as an API response object. Prefer it over general page-speed tools when you need a programmatic, per-call count of render blockers that can be embedded in automated CI/CD pipelines or monitoring workflows. It is distinct from sibling endpoints that check other objects (video, image, iframe, script, font) or other metrics (TTFB, TLS handshake time, FCP).

## Known failure modes

- URL is not publicly accessible — returns error indicating unreachable target
- Invalid or malformed URL — validation error on 'ziel' field
- CSS selector matches no element — fallback to first match or error
- Target returns non-HTML content incompatible with render analysis — audit may return zero or error
- Rate limit exceeded — HTTP 429 response
- Network timeout reaching target URL — timeout error

## How this service works

Prüft am Objekt api-antwort den Befund Zahl renderblockierender Ressourcen.

## Output

Returns an audit result containing the count of render-blocking resources found when loading the specified public URL (API response object). May include details about which resources are blocking rendering.

## 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-com-api-antwort-renderblockierer-pr-fer-bc004fb2/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)