# Hex Encode — REST API endpoint `hex-encode`

Encode UTF-8 text as a hexadecimal string. Optional separator between bytes and uppercase output.

- Category: encoding
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/hex-encode/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/hex-encode/
- Same tool on the other surface: https://findutils.com/mcp/hex-encode/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/hex-encode/execute \
  -H "Content-Type: application/json" \
  -d '{
    "text": "hi"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/hex-encode
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `text` | string | yes | Text to encode. |
| `separator` | string | no | String between bytes (e.g. " " or ":"). Default: "". |
| `upper` | boolean | no | Uppercase hex. Default: false. |

Example arguments (verified):

```json
{
  "text": "hi"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:hex_encode`. Full MCP reference: https://findutils.com/mcp/hex-encode/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt