# x402 Hash Tools API

> x402 Hash Tools API is a paid API for AI agents from call402.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-28).

Computes SHA-256/SHA-512 hashes, Base64 encodes/decodes text, or generates UUIDs via a pay-per-call USDC micropayment endpoint

## Facts

- Endpoint: POST https://call402.com/api/hash-tools?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-hash-tools-api-5e21cdbd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_g3h8J7QqFecnwtxTiURMm

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 x402-hash-tools-api-5e21cdbd -d '<json body>'
```

Example prompt: Can you hash the text 'hello world' using SHA-256 for me?

## When to prefer this

Choose this endpoint when your agent needs lightweight cryptographic utilities (SHA-256/SHA-512 hashing, Base64 encoding/decoding, or UUID generation) via a pay-per-call micropayment model without requiring API key management. Ideal for agentic workflows on Base mainnet using the x402 protocol where per-call USDC billing is preferred over subscription access.

## Known failure modes

- Missing or invalid 'op' enum value returns a 400 error
- Missing 'text' field for operations that require it
- Payment not provided results in HTTP 402 with payment requirements; must retry with PAYMENT-SIGNATURE header
- Malformed Base64 input for decode operation may return an error
- Network or facilitator issues may cause payment verification failures

## How this service works

USDC pay-per-call APIs for AI agents via the x402 protocol (v2, exact, Base mainnet). Send a request, receive HTTP 402 with payment requirements, pay with @x402/fetch or any x402 client, retry with the PAYMENT-SIGNATURE header.

## Output

A JSON object containing the computed result: for 'hash' operations, both sha256 and sha512 hex digest strings; for 'base64-encode' or 'base64-decode', the transformed string; for 'uuid', a newly generated UUID string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "op": {
   "enum": [
    "hash",
    "base64-encode",
    "base64-decode",
    "uuid"
   ],
   "type": "string"
  },
  "text": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "sha256": "2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824",
  "sha512": "9b71d224bd62f3785d96d46ad3ea3d73319bfbc2890caadae2dff72519673ca7"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-hash-tools-api-5e21cdbd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from call402.com](https://www.zero.xyz/host/call402.com/llms.txt)