# SHA3-256 Hash Digest API

> SHA3-256 Hash Digest API 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 a SHA3-256 cryptographic digest from plain text or raw hex-encoded bytes

## Facts

- Endpoint: POST https://twin.unykorn.org/hash-sha3-256?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/sha3-256-hash-digest-api-08915ce2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QuglEtuK0s_uZ6jRYC7pq

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 sha3-256-hash-digest-api-08915ce2 -d '<json body>'
```

Example prompt: Can you compute the SHA3-256 hash of the text 'Hello, world!' for me?

## When to prefer this

Use this endpoint when you need a SHA3-256 (not SHA2-256 or Keccak-256) digest of either plain text or raw hex-encoded bytes, especially in agentic or blockchain-adjacent workflows where on-chain payment receipts are required or useful for auditability. Prefer it over local hashing when a receipted, auditable proof-of-computation is needed.

## Known failure modes

- Invalid hex format (not matching ^0x[0-9a-fA-F]*$) returns a validation error
- Text input exceeding 49152 characters is rejected
- Missing both hex and text parameters may return an error
- Payment failure or insufficient funds results in a 402 response
- Malformed JSON request body causes a parsing error

## How this service works

SHA3-256 digest of text or raw bytes — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok:true, the hash type ('hash-sha3-256'), and a receipt containing the blockchain transaction hash, USD amount paid, and a unique receipt ID, along with a generated_at ISO8601 timestamp.

## 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-sha3-256",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.25,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sha3-256-hash-digest-api-08915ce2/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)
