# tempo.halowerk.com – Page Request Count Check

> tempo.halowerk.com – Page Request Count 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-14).

Checks and returns the number of loaded resources (requests) for a web page object as a performance metric.

## Facts

- Endpoint: POST https://tempo.halowerk.com/v1/pruef/tempo/anfragen/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-com-page-request-count-check-0fcbf586
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__66SOTcYLBePS3BV7Yq3e

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-page-request-count-check-0fcbf586 -d '<json body>'
```

Example prompt: How many resources does https://example.com load when the page opens? I want to audit the total number of HTTP requests it makes.

## When to prefer this

Use this endpoint when you need to specifically count the number of HTTP requests/resources a web page loads, as a web performance audit metric. Prefer this over generic page auditing tools when you need a single focused metric (request count) for a specific page or element, especially when monitoring changes over time or comparing two URLs.

## Known failure modes

- URL is not publicly accessible or returns non-200 status
- CSS selector matches zero or multiple elements and first-match fallback is used
- Target page requires JavaScript rendering that times out
- Invalid or malformed URL in the ziel field
- Page blocks automated access (bot protection, CAPTCHA)

## How this service works

Prüft am Objekt seite den Befund Zahl geladener Ressourcen.

## Output

Returns the total count of HTTP resources (requests) loaded by the target page, giving a quantitative performance finding that can be compared against benchmarks or tracked over time.

## 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-page-request-count-check-0fcbf586/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)