Back to Browse
Delx Commerce ETag Match
x402
Delx Commerce ETag Match 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-01).
Compares two ETag values to determine whether they match, supporting weak and strong comparison modes.
Price / call$0.001
Success—
StatusUnknown
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 indicating whether the two provided ETags match (match: true/false), the comparison mode used (e.g. 'list'), whether the first ETag is weak (weak_a: boolean), and the schema version identifier. The 'ok' field confirms the request was processed successfully.
Example use cases
Cache freshness validation for agent
“I have two ETags from consecutive API responses — '"d41d8cd98f00b204e9800998ecf8427e"' and '"d41d8cd98f00b204e9800998ecf8427e"' — can you check if they match so I know whether the resource changed?”
Conditional request decision making
“Before I make a full HTTP GET, compare ETag '"v2-strong-tag"' against the cached '"v1-strong-tag"' and tell me if they match so I know whether to skip the download.”
Weak ETag equivalence check
“I have two weak ETags from my CDN — 'W/"etag-001"' and 'W/"etag-001"' — do they count as matching under weak comparison rules?”
Technical details
Endpoint
POSThttps://commerce.delx.ai/api/v1/x402/etag-match?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need a standards-compliant, pay-per-use ETag comparison without setting up any infrastructure. Ideal for AI agents performing HTTP cache validation, conditional request logic, or resource identity checks in automated workflows where a lightweight, no-signup utility is preferred over implementing ETag comparison logic inline.
Side effects
- Missing or malformed ETag inputs may return an error or unexpected match result
- Invalid ETag format (not quoted strings) may cause incorrect comparison
- Payment failure via x402 protocol blocks the request from being processed
- Non-string inputs may cause schema validation errors
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| etag | string | Input field: etag. |
| other | string | Input field: other. |
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"mode": "list",
"match": true,
"schema": "delx/util-etag-match/v1",
"weak_a": false
}
}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"