# HTML Named Entity Encoder

> HTML Named Entity Encoder is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.007/call, status unknown (last checked 2026-10-02).

Encodes text by converting special characters to their HTML named entity equivalents (e.g. & → &amp;, < → &lt;)

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/html-named-encode?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/html-named-entity-encoder-215528f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gkkHb-K7L_T8Gy4jkgsbO

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 html-named-entity-encoder-215528f5 -d '<json body>'
```

Example prompt: Can you encode this string using HTML named entities so it's safe to embed in HTML markup: 'Hello <World> & "everyone" — it\'s alive!'

## When to prefer this

Choose this endpoint when you need deterministic, offline HTML named entity encoding without any LLM or network dependency. It is useful when you need to escape strings for safe HTML embedding and require exact, standards-compliant named entity output (e.g. &amp; rather than numeric &#38;). Note that an unpaid sandbox version at POST /v1/sandbox/html-named-encode should be preferred for testing or when cost must be avoided.

## Known failure modes

- Empty or missing 'text' field returns a validation error
- Text exceeding 100,000 characters is rejected
- Payment of $0.007 USDC not provided or x402 payment fails causes 402 response
- Malformed JSON body returns 400 error

## How this service works

Call when an agent needs text encoded with html-named. No network and no LLM. Exact $0.007 USDC. Prefer unpaid POST /v1/sandbox/html-named-encode first.

## Output

Returns the input text with all special characters replaced by their corresponding HTML named entity references (e.g. < becomes &lt;, & becomes &amp;, " becomes &quot;, etc.), making the string safe for direct embedding in HTML documents.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "examples": [
    "Hello, World!"
   ],
   "maxLength": 100000,
   "minLength": 1,
   "description": "Input for this SKU. The route description says whether it is plain text, a URL, base64 bytes, or an already-encoded token."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/html-named-entity-encoder-215528f5/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)