# stall-row Page Metadata

> stall-row Page Metadata is a paid API for AI agents from stall-row-production.up.railway.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-21).

Fetches a web page's declared metadata — title, description, canonical URL, OpenGraph/Twitter card fields, language, favicon, heading outline, and word count — in a single call without retrieving full content.

## Facts

- Endpoint: POST https://stall-row-production.up.railway.app/v1/page-metadata?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stall-row-page-metadata-c95fde03
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SV3hiaoBwR_-7DHL3Tnfd

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 stall-row-page-metadata-c95fde03 -d '<json body>'
```

Example prompt: Before you fetch the full article, can you grab the metadata for https://example.com/some-article — I want to see the title, description, OpenGraph fields, heading outline, and word count so I can decide if it's worth reading in full?

## When to prefer this

Use this endpoint when you need a lightweight preview of a page's identity and structure before committing to a full content fetch. It is ideal for relevance filtering, link preview generation, SEO auditing, and heading-structure inspection. Prefer it over a full page-to-markdown fetch when you only need declared metadata fields and want to minimize cost and latency.

## Known failure modes

- URL is unreachable or returns a non-200 status — error response with HTTP status
- Page has no declared metadata — fields return null or empty strings
- SSRF guard blocks internal/private IP ranges — request rejected with an error
- Page uses JavaScript-rendered metadata not present in raw HTML — fields may be missing or incomplete
- Malformed URL input — validation error returned

## How this service works

One web page's declared metadata in one call: title, description, canonical URL, OpenGraph and Twitter card fields, document language, favicon, the h1/h2 heading outline, and word count — fetched through the same SSRF-guarded pipeline as page-to-markdown. Use this when an agent needs a page's identity and shape before deciding whether the full content is worth fetching.

## Output

A structured JSON object containing the page's title, meta description, canonical URL, OpenGraph fields (og:title, og:description, og:image, og:type), Twitter card fields, document language code, favicon URL, an ordered list of h1/h2 headings, and total word count — all sourced from the page's declared metadata without full content retrieval.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stall-row-page-metadata-c95fde03/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stall-row-production.up.railway.app](https://www.zero.xyz/host/stall-row-production.up.railway.app/llms.txt)
