# encoding-transcode

> encoding-transcode is a paid API for AI agents from x402.agentindex.world, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Converts text between utf-8, base64, hex, URL-percent-encoding, and ASCII representations.

## Facts

- Endpoint: GET https://x402.agentindex.world/encoding/transcode?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/encoding-transcode-e6ca550f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iSU7Sd5mLnguiB96NM6kD

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 encoding-transcode-e6ca550f
```

Example prompt: Can you convert this base64 string 'SGVsbG8gV29ybGQ=' from base64 to utf-8 so I can read it as plain text?

## When to prefer this

Choose this endpoint when an agent needs a fast, lightweight, pay-per-call text encoding conversion without managing API keys or setting up a local library. It is ideal for quick one-off conversions between utf-8, base64, hex, URL-percent-encoding, and ASCII in automated pipelines, especially when the agent environment doesn't have convenient access to encoding utilities.

## Known failure modes

- Invalid or unrecognized from_encoding or to_encoding value (must match pattern: utf-8, base64, hex, url, ascii)
- Text content is not valid in the specified from_encoding (e.g. malformed base64 input)
- Empty or missing text parameter
- Payment failure or x402 authorization error ($0.002 USDC per call required)
- Network timeout or service unavailability

## How this service works

Convert text between utf-8, base64, hex, URL-percent-encoding and ascii representations.

## Output

Returns the transcoded text string in the requested target encoding. The response is a plain converted string — for example, a base64 string decoded to UTF-8 readable text, or a UTF-8 string encoded as hex or URL-percent-encoded format.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "title": "Text"
  },
  "to_encoding": {
   "type": "string",
   "title": "To Encoding",
   "pattern": "^(utf-8|base64|hex|url|ascii)$"
  },
  "from_encoding": {
   "type": "string",
   "title": "From Encoding",
   "pattern": "^(utf-8|base64|hex|url|ascii)$"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/encoding-transcode-e6ca550f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.agentindex.world](https://www.zero.xyz/host/x402.agentindex.world/llms.txt)