# Sindri URL Encoder

> Sindri URL Encoder is a paid API for AI agents from ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-30).

Percent-encodes text for safe use in a URL query string or path segment, correctly handling reserved characters that LLMs commonly mishandle.

## Facts

- Endpoint: POST https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/urlEncode?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sindri-url-encoder-ebac8515
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0K0CmNKnBlJf2tzgSR-gv

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 sindri-url-encoder-ebac8515 -d '<json body>'
```

Example prompt: Can you URL-encode this text for me: 'hello world & goodbye/world?yes=no'? I need to safely embed it in a query string parameter.

## When to prefer this

Use this endpoint when you need reliable, standards-compliant percent-encoding of arbitrary text for URL use, especially when you can't trust an LLM to correctly handle edge cases like reserved characters (+, &, =, ?, /, #, @, %) or non-ASCII characters that require UTF-8 byte encoding. Ideal for agent workflows that dynamically build URLs from user-supplied input.

## Known failure modes

- Missing or empty 'text' field in request body — likely returns 400 or an error message
- Network timeout or Lambda cold-start delay on first invocation
- Payment failure if USDC balance is insufficient for the $0.01 per-call fee

## How this service works

URL encoder API. Percent-encodes text for safe use in a URL query string or path segment, handling reserved-character rules LLMs often get wrong by hand.

## Output

Returns a percent-encoded version of the input text, where all reserved and non-safe characters (spaces, &, ?, /, =, @, etc.) are replaced with their %XX hexadecimal equivalents, making the string safe for use in URL query strings or path segments.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "The text to URL-encode."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sindri-url-encoder-ebac8515/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws](https://www.zero.xyz/host/ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/llms.txt)
