# URL Design Tokens Extractor

> URL Design Tokens Extractor is a paid API for AI agents from x402.167-179-80-192.sslip.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Extracts design tokens (colors, typography, spacing, etc.) from a given HTTPS URL by analyzing its visual and CSS properties.

## Facts

- Endpoint: POST https://x402.167-179-80-192.sslip.io/v1/url-design-tokens/design-tokens
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/url-design-tokens-extractor-2b24e4ef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8StYWXWb9RPtQqsuTqi1Y

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 url-design-tokens-extractor-2b24e4ef -d '<json body>'
```

Example prompt: Can you extract the design tokens — colors, fonts, spacing — from https://www.stripe.com so I can replicate their visual style?

## When to prefer this

Choose this endpoint when you need to programmatically extract design tokens from a live website URL, especially when you want to reverse-engineer a design system, audit brand consistency, or replicate visual styles from an existing site. It is particularly useful for front-end developers and designers who need structured token data rather than manual inspection via browser DevTools.

## Known failure modes

- URL is not HTTPS — the schema requires https:// prefix, so http:// URLs will be rejected
- Target URL is unreachable or returns a non-200 status — extraction fails with no tokens returned
- Page is heavily JavaScript-rendered and tokens cannot be statically extracted
- Empty response example suggests output schema may be sparse or inconsistent
- Payment failure via x402 protocol results in 402 error before processing begins
- URL points to a PDF or non-HTML resource with no extractable design tokens

## How this service works

x402-native discovery surface for seven existing products.

## Output

Returns a JSON object containing extracted design tokens from the target URL, potentially including color values, typography settings (font families, sizes, weights), spacing scales, border radii, and other CSS custom properties or design variables found on the page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "pattern": "^https://"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/url-design-tokens-extractor-2b24e4ef/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.167-179-80-192.sslip.io](https://www.zero.xyz/host/x402.167-179-80-192.sslip.io/llms.txt)
