# Tempo Halowerk – Video Render-Blocking Resources Check

> Tempo Halowerk – Video Render-Blocking Resources Check 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).

Analyzes a video resource URL and counts the number of render-blocking resources it introduces.

## Facts

- Endpoint: POST https://tempo.halowerk.com/v1/pruef/tempo/blockierer/video
- 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-video-render-blocking-resources-check-eeb91b72
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eWfwvQNcF2C1aIFCGNLws

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-video-render-blocking-resources-check-eeb91b72 -d '<json body>'
```

Example prompt: Can you check how many render-blocking resources are associated with the video at https://example.com/media/intro.mp4 and tell me if it's a performance concern?

## When to prefer this

Use this endpoint when you specifically need to audit a video resource for render-blocking resource count as part of a web performance workflow. It is distinct from sibling endpoints that check other objects (pages, scripts, images, iframes) or other metrics (TTFB, visual render start, modern image formats). Choose this when the asset under test is a video and render-blocking resources are the metric of interest.

## Known failure modes

- URL is not publicly accessible — returns an error or empty result
- Non-video URL passed — audit may return unexpected or empty findings
- CSS selector matches zero elements — falls back to first matched element or returns no result
- Network timeout when fetching the target URL — request fails
- Invalid URL format — input validation error returned

## How this service works

Prüft am Objekt video den Befund Zahl renderblockierender Ressourcen.

## Output

Returns a numeric finding representing the count of render-blocking resources detected for the specified video resource, along with associated audit metadata such as the target URL and analysis timestamp.

## 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-video-render-blocking-resources-check-eeb91b72/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)