# OpenVerbs Text Encode

> OpenVerbs Text Encode is a paid API for AI agents from text.openverbs.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Encodes a UTF-8 string into base64, base64url, hex, base32, or URL percent-encoding format.

## Facts

- Endpoint: POST https://text.openverbs.com/v1/encode
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/openverbs-text-encode-60ad43f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qIUbmq3s_KkYrPTb4hNbp

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 openverbs-text-encode-60ad43f5 -d '<json body>'
```

Example prompt: Can you base64-encode this string for me: 'Hello, World! This is my API key payload.'

## When to prefer this

Use this endpoint when you need a reliable, API-accessible way to encode strings without running local code — ideal for agents operating in environments without native encoding libraries, or when you need a consistent, tested encoding implementation across base64, base64url, hex, base32, and URL percent-encoding formats. It pairs naturally with the sibling decode endpoint on the same service.

## Known failure modes

- Input text exceeds 1,000,000 character limit — request rejected
- Invalid or unsupported encoding type specified — validation error
- Malformed JSON request body — 400 bad request
- Payment not included or insufficient — 402 payment required
- Non-UTF-8 input may cause encoding errors

## How this service works

Encode a UTF-8 string into base64, base64url, hex, base32, or URL percent-encoding.

## Output

Returns the encoded representation of the input string in the requested encoding format (base64, base64url, hex, base32, or URL percent-encoding) as a string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "text",
      "encoding"
     ],
     "properties": {
      "text": {
       "type": "string",
       "maxLength": 1000000,
       "description": "The UTF-8 text to encode."
      },
      "encoding": {
       "enum": [
        "base64",
        "base64url",
        "hex",
        "base32",
        "url"
       ],
       "type": "string",
       "description": "Target encoding, one of base64, base64url, hex, base32, url."
      }
     },
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openverbs-text-encode-60ad43f5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from text.openverbs.com](https://www.zero.xyz/host/text.openverbs.com/llms.txt)