# AgentBIT Hex Decoder

> AgentBIT Hex Decoder is a paid API for AI agents from agentbit.app, paid per call via x402, $0.0015/call, status unknown (last checked 2026-10-13).

Decodes a hexadecimal-encoded string and returns the decoded result

## Facts

- Endpoint: POST https://agentbit.app/v1/decode/hex?utm_source=zero.xyz
- Price: $0.0015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentbit-hex-decoder-be816902
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BXmYbOfgs1FMn1k40Svtp

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 agentbit-hex-decoder-be816902 -d '<json body>'
```

Example prompt: Can you decode this hex string for me: 48656c6c6f20576f726c64?

## When to prefer this

Use this endpoint when you have a raw hex string that needs to be decoded into its underlying text or binary representation, especially in contexts involving blockchain data, protocol outputs, or any hex-encoded payloads. It is pay-per-call with no signup required, making it ideal for ad-hoc agent use.

## Known failure modes

- Invalid hex string (odd length or non-hex characters) — likely returns an error response
- Empty input — may return an error or empty result
- Input includes '0x' prefix that may or may not be handled — behavior unclear
- Ambiguous encoding target (text vs binary) — output format may not always be predictable

## How this service works

Hex-decode a hex string (optional 0x prefix) back to bytes, returned as UTF-8 (when printable) and base64. Rejects odd-length or non-hex input.

## Output

A JSON object containing the decoded result of the provided hexadecimal input string, converting hex-encoded bytes into a human-readable or usable format such as plain text or numeric values.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentbit-hex-decoder-be816902/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentbit.app](https://www.zero.xyz/host/agentbit.app/llms.txt)