# Decode Base58 to Bytes

> Decode Base58 to Bytes is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Decodes a Base58-encoded string into its raw byte representation

## Facts

- Endpoint: POST https://twin.unykorn.org/decode-base58?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/decode-base58-to-bytes-eb7d0b77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_toVx79MDYf5NwX1J1HH1a

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 decode-base58-to-bytes-eb7d0b77 -d '<json body>'
```

Example prompt: Can you decode this Base58 string '5HueCGU8rMjxECyDialwujznoty66qKbBQLWsRDpY' into its raw bytes for me?

## When to prefer this

Choose this endpoint when you need a pay-per-call, serverless Base58 decoding capability without standing up your own infrastructure — particularly useful in agent pipelines dealing with cryptocurrency addresses, IPFS CIDs, or other Base58-encoded blockchain data. It fits naturally alongside other UnyKorn crypto utility endpoints like ABI-encoding and RLP-encoding.

## Known failure modes

- Invalid Base58 characters in input string (contains 0, O, I, l) returns an error
- Empty or missing 'data' field in params returns a validation error
- Malformed JSON request body returns a 400-level error
- Payment failure or insufficient USDC balance prevents the call from completing

## How this service works

Decode base58 to bytes — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok=true, the operation type 'decode-base58', and a receipt containing the transaction hash, amount paid in USD, and a receipt ID. The decoded byte data is included in the response body.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "data": {
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "decode-base58",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.001,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/decode-base58-to-bytes-eb7d0b77/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)