# agentshelf.syntexa.ch Twitter Card Meta Extractor

> agentshelf.syntexa.ch Twitter Card Meta Extractor is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-29).

Extracts the twitter:card meta tag value from a public web page URL or raw HTML string, with SSRF protection.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/css-meta-twitter?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshelf-syntexa-ch-twitter-card-meta-extractor-1b9deaf1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tgzrL2IHVSEGkd3q09Qn0

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 agentshelf-syntexa-ch-twitter-card-meta-extractor-1b9deaf1 -d '<json body>'
```

Example prompt: Can you extract the twitter:card meta tag value from https://example.com — I want to know what card type they're using for Twitter sharing?

## When to prefer this

Use this endpoint when you need to programmatically read the twitter:card meta tag from a public web page or a known HTML string, especially in agentic pipelines doing SEO audits, social preview validation, or web scraping. The SSRF-safe design makes it appropriate for production agent use. Prefer the free sandbox POST /v1/sandbox/css-meta-twitter endpoint first if available to avoid the $0.008 USDC cost.

## Known failure modes

- URL is unreachable or returns non-200 status — no content extracted
- SSRF protection blocks requests to private/internal IP ranges or localhost
- HTML input exceeds 200,000 character limit — request rejected
- No twitter:card meta tag present in the HTML — empty or null result
- Malformed HTML may prevent tag detection
- URL scheme is not http/https — may be rejected

## How this service works

Call when an agent needs twitter:card content via meta[name='twitter:card'] from a public page or HTML (SSRF-safe). Exact $0.008 USDC. Prefer unpaid POST /v1/sandbox/css-meta-twitter first.

## Output

Returns the content value of the meta[name='twitter:card'] tag found in the page or HTML — typically a string like 'summary', 'summary_large_image', 'app', or 'player'. Returns null or an empty result if no such tag is found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 8,
   "description": "Public page to fetch. The selector or profile is fixed by the SKU. Provide url or html."
  },
  "html": {
   "type": "string",
   "examples": [
    "<!doctype html><html lang=\"en\"><head><title>Hello</title>\n<meta charset=\"utf-8\"><meta name=\"description\" content=\"Desc\">\n<link rel=\"canonical\" href=\"https://example.com/\"><link rel=\"icon\" href=\"/favicon.ico\">\n</head><body><h1>Hello</h1><a href=\"https://example.com/a\">A</a></body></html>"
   ],
   "maxLength": 200000,
   "minLength": 1,
   "description": "HTML to extract from locally. Provide html or url. When both are set, html is used."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshelf-syntexa-ch-twitter-card-meta-extractor-1b9deaf1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)
