# Bitcoin HASH160 (RIPEMD-160 of SHA-256)

> Bitcoin HASH160 (RIPEMD-160 of SHA-256) 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).

Computes the Bitcoin HASH160 hash of an input — applies SHA-256 then RIPEMD-160 — accepting either a hex-encoded byte string or raw text.

## Facts

- Endpoint: POST https://twin.unykorn.org/hash-hash160?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/bitcoin-hash160-ripemd-160-of-sha-256-bec19672
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zlTPzST6wga1hZ5yppKOA

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 bitcoin-hash160-ripemd-160-of-sha-256-bec19672 -d '<json body>'
```

Example prompt: Compute the Bitcoin HASH160 of this compressed public key hex: 0x0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798

## When to prefer this

Use this endpoint when you need to compute Bitcoin's HASH160 (RIPEMD-160(SHA-256(x))) specifically — the standard hash used for P2PKH and P2SH Bitcoin addresses and script hashes. Prefer this over generic SHA-256 or RIPEMD-160 endpoints when working in a Bitcoin context, and over local computation when you need a verifiable, receipted, pay-per-use API call in an agentic workflow. It accepts both raw hex bytes and text, making it flexible for both public key hashing and arbitrary data.

## Known failure modes

- Invalid hex prefix: input hex must start with 0x or request will be rejected
- Input text exceeds 49152 character limit causing a validation error
- Malformed hex string (odd length or non-hex characters) resulting in a parse error
- Missing both hex and text fields returns an error
- Payment failure on x402 protocol causes 402 response before processing begins

## How this service works

Bitcoin HASH160 — RIPEMD-160 of SHA-256 — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok=true, the hash type identifier ('hash-hash160'), the HASH160 digest (20-byte RIPEMD-160 output of the SHA-256 of the input), a generation timestamp, and a payment receipt including the transaction hash, USD amount, and receipt ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "hex": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]*$"
    },
    "text": {
     "type": "string",
     "maxLength": 49152
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "hash-hash160",
  "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/bitcoin-hash160-ripemd-160-of-sha-256-bec19672/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)