Back to Browse
SHA3-256 Base64url Digest (Latin1 Input)
x402
SHA3-256 Base64url Digest (Latin1 Input) is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-02).
Computes a SHA3-256 cryptographic hash of Latin1-encoded text and returns the digest encoded as base64url.
Price / call$0.004
Success—
StatusUnknown
How this service works
Call when an agent needs a sha3-256 digest of latin1 bytes, encoded as base64url. Exact $0.004 USDC. Prefer unpaid POST /v1/sandbox/digest-sha3-256-base64url-latin1 first.
Output
Returns the SHA3-256 digest of the provided Latin1-encoded text, encoded as a base64url string. The output is a fixed-length cryptographic hash suitable for integrity checks, deduplication, or tamper detection.
Example use cases
Integrity fingerprint for API payload
“Take this Latin1-encoded request body — 'name=José&amount=100¤cy=EUR' — and give me its SHA3-256 digest in base64url so I can use it as a checksum.”
Content deduplication key generation
“I need to generate a SHA3-256 base64url fingerprint of this Latin1 article text so I can detect if the same content gets submitted twice: 'El niño corrió por el jardín...'”
Tamper-evident log entry hashing
“Hash this Latin1 log message using SHA3-256 and return it as base64url so I can store it alongside the original for integrity verification: 'User änderung at 2024-06-01T12:00:00Z'”
Technical details
Endpoint
POSThttps://agentshelf.syntexa.ch/v1/digest-sha3-256-base64url-latin1?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you specifically need a SHA3-256 hash (not SHA-256 or MD5) with base64url output encoding (not hex) and the input is Latin1-encoded text. It is the right choice when downstream systems expect the SHA3-256 algorithm combined with base64url encoding and Latin1 byte semantics, distinguishing it from sibling endpoints that use SHA-256 hex or different encodings.
Side effects
- Input text contains characters not representable in Latin1 encoding — may return encoding error
- Text exceeds 100,000 character limit — request rejected
- Key field empty or exceeds 512 characters — validation error
- Network or payment failure — 402 or 5xx response
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| key | string | HMAC secret. Required on HMAC SKUs. Omit it for plain digests and checksums. The key is not stored. |
| text | string | 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. |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"