# Vextorium Hashing & Encoding API

> Vextorium Hashing & Encoding API is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.0045/call, status unknown (last checked 2026-10-02).

Computes cryptographic hashes (SHA-256, SHA-512, SHA-3, Keccak-256, MD5, SHA-1, BLAKE2, RIPEMD-160, CRC32), HMAC signatures, encodes/decodes Base64/Base64URL/Hex/URL/Base58, decodes JWTs with expiry check, and generates UUIDs v4/v5 — all in a single POST endpoint.

## Facts

- Endpoint: POST https://api.vextorium.com/codificar-pago?utm_source=zero.xyz
- Price: $0.0045/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-hashing-encoding-api-26ca9347
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DMDifa2phqA85j9fPzvi2

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 vextorium-hashing-encoding-api-26ca9347 -d '<json body>'
```

Example prompt: Hash the text 'Hello, world!' using SHA-256 and also give me the Keccak-256 digest so I can compare them.

## When to prefer this

Choose this endpoint when you need a single, paid-per-call API that consolidates a wide variety of hashing and encoding operations without deploying your own crypto library or server. Especially useful in agentic pipelines that need keccak256 (for EVM/blockchain work), Base58 (for Bitcoin/Solana address handling), JWT validation, or all-hashes-at-once comparison in one request. Prefer it over custom code when you want a serverless, stateless crypto utility with no infrastructure overhead.

## Known failure modes

- Missing 'operacion' field returns a 400-level error
- Invalid or unsupported operation name returns an error response
- HMAC operation without a 'clave' secret key fails
- Input data exceeding 1 MB size limit is rejected
- Invalid base64 or hex input when formato_entrada is set to hex/base64 causes a parse error
- Invalid UUID namespace for uuid5 operation returns an error
- JWT decode on a malformed token string returns an error

## How this service works

One endpoint for hashing and encoding: sha256, sha512, sha3, keccak256, md5, sha1, blake2, ripemd160, crc32, all-hashes-at-once, HMAC, base64/base64url, hex, URL and base58 encode/decode, JWT decode (with expiry check) and UUID v4/v5. Input as text, hex or base64.

## Output

Returns a JSON object with an 'operacion' field (the operation name), a 'resultado' field (the output: hash hex string, encoded/decoded string, JWT claims object, UUID string, or for 'todos_los_hashes' a map of all algorithms to their digests), and 'bytes_entrada' (the number of bytes in the input).

## 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": {
     "required": [
      "operacion"
     ],
     "properties": {
      "clave": {
       "type": "string",
       "description": "Secret key (HMAC only)"
      },
      "entrada": {
       "type": "string",
       "description": "Input data (up to 1 MB)"
      },
      "espacio": {
       "type": "string",
       "description": "UUID v5 namespace: dns, url (default), oid, x500 or a UUID"
      },
      "algoritmo": {
       "type": "string",
       "description": "HMAC hash: sha256 (default), sha512, sha384, sha1, md5, sha3_256"
      },
      "operacion": {
       "type": "string",
       "description": "sha256, keccak256, md5, todos_los_hashes, hmac, base64_codificar, base64_decodificar, base64url_codificar, base64url_decodificar, hex_codificar, hex_decodificar, url_codificar, url_decodificar, base58_codificar, base58_decodificar, jwt_decodificar, uuid4, uuid5..."
      },
      "formato_entrada": {
       "enum": [
        "texto",
        "hex",
        "base64"
       ],
       "type": "string",
       "description": "How to read the input: texto (default), hex or base64"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": [
      "object",
      "null"
     ],
     "properties": {
      "operacion": {
       "type": [
        "string",
        "null"
       ]
      },
      "resultado": {
       "type": [
        "string",
        "null"
       ]
      },
      "bytes_entrada": {
       "type": [
        "number",
        "null"
       ]
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "operacion": "sha256",
  "resultado": "ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad",
  "bytes_entrada": 3
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-hashing-encoding-api-26ca9347/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)