# RIPEMD-160 Hex Digest of Hex-Encoded Raw Bytes

> RIPEMD-160 Hex Digest of Hex-Encoded Raw Bytes is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.009/call, status unknown (last checked 2026-10-02).

Computes a RIPEMD-160 hash of raw bytes supplied as a hex string, returning the digest as a hex string.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-ripemd160-hex-rawhex?utm_source=zero.xyz
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ripemd-160-hex-digest-of-hex-encoded-raw-bytes-8ccd5c4a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_krxFxWkIA7hEQGqnUpIYR

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 ripemd-160-hex-digest-of-hex-encoded-raw-bytes-8ccd5c4a -d '<json body>'
```

Example prompt: Can you compute the RIPEMD-160 hash of these raw bytes given as hex — '0x14a3b2c9d8e7f0a1' — and give me the result as a hex digest?

## When to prefer this

Choose this endpoint when you have raw binary data already encoded as a hex string and need a RIPEMD-160 digest returned as hex — common in blockchain workflows like Bitcoin HASH160 (SHA256 + RIPEMD-160), cryptographic fingerprinting, or key derivation. Prefer the free sandbox variant (/v1/sandbox/digest-ripemd160-hex-rawhex) for development and testing to avoid per-call charges. Use this paid endpoint when the sandbox is unavailable or rate-limited.

## Known failure modes

- Invalid or non-hex input string causes a parsing error
- Input hex string length is odd or contains non-hex characters, resulting in a 400 Bad Request
- Payment of $0.009 USDC not provided or fails, resulting in a 402 Payment Required
- Input exceeds maxLength of 100000 characters, resulting in a 413 or 400 error
- Missing required fields returns a validation error

## How this service works

Call when an agent needs a ripemd160 digest of hex bytes, encoded as hex. Exact $0.009 USDC. Prefer unpaid POST /v1/sandbox/digest-ripemd160-hex-rawhex first.

## Output

A hex-encoded RIPEMD-160 digest (40 hex characters) of the raw binary data supplied as a hex string. The response contains the hash output ready for downstream cryptographic use.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string",
   "maxLength": 512,
   "minLength": 1,
   "description": "HMAC secret. Required on HMAC SKUs. Omit it for plain digests and checksums. The key is not stored."
  },
  "text": {
   "type": "string",
   "examples": [
    "68656c6c6f"
   ],
   "maxLength": 100000,
   "minLength": 1,
   "description": "Message to digest. For raw-hex SKUs this is hex bytes; for utf16 or latin1 SKUs it is decoded with that encoding. Otherwise it is UTF-8 text."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ripemd-160-hex-digest-of-hex-encoded-raw-bytes-8ccd5c4a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)