# Count Audio Elements on Page

> Count Audio Elements on Page is a paid API for AI agents from page.intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-21).

Fetches a web page and counts the number of <audio> HTML elements, including attribute presence stats and total element count for context.

## Facts

- Endpoint: GET https://page.intel.rallylive.ca/page/count/audio?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/count-audio-elements-on-page-b9b5d083
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FDgqutZJYTM0DR2DXXBUE

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 count-audio-elements-on-page-b9b5d083
```

Example prompt: How many audio elements are on the page at https://example.com/podcast? I want to know the total count and how many have src or type attributes set.

## When to prefer this

Use this endpoint when you need a fast, cheap structural count of audio elements on a specific web page, especially for accessibility audits, CMS template comparisons, or detecting whether a page embeds audio content. It is ideal for single-page spot checks rather than bulk crawls, and when you need attribute-level detail (src, type, href) alongside the raw count.

## Known failure modes

- URL is unreachable or returns a non-200 status — count may be zero or an error is returned
- Page uses dynamically injected audio elements via JavaScript — those may not be counted since fetching is likely static
- Page blocks crawlers with bot-detection — fetch may fail or return a non-representative page
- Invalid or malformed URL input — request fails with validation error
- Very large pages may increase latency or cause timeouts

## How this service works

How many <audio> elements does the page have? Fetches the URL and counts audio tags (plus, where relevant, how many have alt/src/href/type attributes), and the page's total element count for scale. Structural audits and template comparisons in one number. $0.01 per page.

## Output

Returns the count of <audio> HTML elements found on the fetched page, alongside counts of how many have alt, src, href, and type attributes, plus the total number of HTML elements on the page for proportional context.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/count-audio-elements-on-page-b9b5d083/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from page.intel.rallylive.ca](https://www.zero.xyz/host/page.intel.rallylive.ca/llms.txt)