Back to Browse
Compare Two Strings in Constant Time
x402
Compare Two Strings in Constant Time 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).
Compares two strings (hashes or secrets) using constant-time comparison to prevent timing attacks
Price / call$0.001
Success—
StatusUnknown
How this service works
Compare two hashes or secrets in constant time — Genesis402 / UnyKorn Operator Network
Output
Returns a JSON object with an 'ok' boolean indicating whether the two inputs matched, a 'type' field confirming 'compare-digest', a 'generated_at' ISO 8601 timestamp, and a 'receipt' object containing the transaction hash, USD amount charged, and a unique receipt ID for the micropayment.
Example use cases
Verify HMAC signature safely
“I need to check whether this incoming HMAC signature 'a3f9d2b1c4e7f8a0' matches the expected digest '3f9d2b1c4e7f8a0a' using constant-time comparison so attackers can't exploit timing differences.”
Validate API key in agent pipeline
“Compare these two API key hashes in constant time for me — 'sha256-abc123def456' and 'sha256-abc123def456' — I'm building a secure auth step and can't risk a timing side-channel.”
Check password reset token equality
“I need a timing-safe comparison between a user-submitted password reset token 'tok_XyZ9q2R' and the stored token 'tok_XyZ9q2R' — can you run that through the constant-time comparator?”
Technical details
Endpoint
POSThttps://twin.unykorn.org/compare-digest?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a cryptographically constant-time string comparison to prevent timing side-channel attacks — ideal for comparing HMACs, API keys, password hashes, or any secret where a simple equality check could leak timing information. Prefer it over local comparison when operating in untrusted or sandboxed environments where you can't guarantee constant-time execution semantics.
Side effects
- Missing or malformed 'a' or 'b' parameters — returns validation error
- Payment failure via x402 — returns 402 Payment Required if USDC payment not provided
- Network timeout on the UnyKorn node — endpoint unreachable
- Empty string inputs may return an error or unexpected comparison result
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| params | object |
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"type": "compare-digest",
"receipt": {
"tx_hash": "0x<64hex>",
"amount_usd": 0.001,
"receipt_id": "g402-<16hex>"
},
"generated_at": "<iso8601>"
}
}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"