# Delx Commerce — SHA-256 Hash of Base64-Encoded Bytes

> Delx Commerce — SHA-256 Hash of Base64-Encoded Bytes is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Computes the SHA-256 hash of base64-encoded bytes and returns the hex digest along with the byte count.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/bytes-sha256-b64?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-sha-256-hash-of-base64-encoded-bytes-482408d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lHyAklMRN91GSOVSKxaFY

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 delx-commerce-sha-256-hash-of-base64-encoded-bytes-482408d3 -d '<json body>'
```

Example prompt: Can you compute the SHA-256 hash of these base64-encoded bytes: 'aGVsbG8='?

## When to prefer this

Choose this endpoint when you need a pay-per-use, no-signup SHA-256 hash of binary data that is already base64-encoded, especially in agent pipelines where USDC micropayments via x402 are acceptable and verifiable delivery is required. Prefer over self-hosted hashing when you want a trustless, on-chain-payment-verified cryptographic primitive.

## Known failure modes

- Invalid base64 string returns an error response
- Missing 'base64' field in request body causes a validation error
- Empty base64 string may return a zero-byte result or error
- Payment not provided or insufficient USDC results in HTTP 402 response

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns a JSON object containing the SHA-256 hex digest of the decoded bytes, the number of bytes, and a schema version string (e.g. {"sha256": "2cf24dba...", "nbytes": 5, "schema": "delx/util-bytes-sha256-b64/v1"}).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "base64": {
   "type": "string",
   "description": "Base64-encoded bytes"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "nbytes": 5,
  "schema": "delx/util-bytes-sha256-b64/v1",
  "sha256": "2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-sha-256-hash-of-base64-encoded-bytes-482408d3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)