# PennyRail Crypto Multi-Hash

> PennyRail Crypto Multi-Hash is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Computes multiple cryptographic hashes of input data in a single paid API call

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/nano/crypto.hash-multi--hash
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-crypto-multi-hash-d642ec78
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yzXsVVulrlOTuF5TNRDij

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 pennyrail-crypto-multi-hash-d642ec78 -d '<json body>'
```

Example prompt: Compute multiple cryptographic hash digests of this payload for me — I need the fingerprints across several hash algorithms in one shot: {"message": "hello world", "timestamp": 1718000000}.

## When to prefer this

Choose this endpoint when you need to compute cryptographic hashes across multiple algorithms in a single network round-trip rather than calling separate hash endpoints. It is well-suited for content addressing, deduplication, integrity verification, and scenarios where deterministic multi-algorithm fingerprints are required. Prefer it over single-algorithm hash services when you need hash agility or want to future-proof your hashing strategy.

## Known failure modes

- Missing or malformed 'input' field returns a validation error
- Payment not included or insufficient USDC triggers a 402 Payment Required response
- Empty input object may produce zero-length or undefined hash results
- Network timeout on the Vercel serverless function under heavy load
- Unsupported input types (e.g., binary blobs passed as raw JSON) may cause serialization errors

## How this service works

Machine-readable settlement service

## Output

An object containing hash digests of the input computed across multiple cryptographic algorithms (e.g., SHA-256, MD5, SHA-1, SHA-512). Each key in the response corresponds to a hash algorithm name and its value is the resulting hex or base64-encoded digest string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pennyrail-crypto-multi-hash-d642ec78/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pennyrail.vercel.app](https://www.zero.xyz/host/pennyrail.vercel.app/llms.txt)