Back to Browse
Delx Commerce — EVM Event Log Shape Check
x402
Delx Commerce — EVM Event Log Shape Check 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).
Validates the structural shape of an EVM event log object, confirming it has the expected fields and format without retaining any input data.
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 containing: a `shape_valid` boolean indicating whether the log is structurally valid, the echoed log fields (address, topics, data), a status of 'pass' or 'fail', an evidence block with a SHA-256 hash of the input (for verifiability), a flag confirming no data was retained, and the count of external calls made (always 0).
Example use cases
Pre-index EVM log validation
“Before I store these Ethereum event logs in my indexer, can you check each one to confirm it has a valid shape — correct address, topics array, and data field?”
Smart contract event preflight
“I'm about to decode a batch of Transfer events from my smart contract — can you validate the shape of this event log object first to make sure it won't break my parser?”
Agent pipeline EVM log gate
“My agent just picked up this EVM event log from a webhook — can you do a quick shape check on it to verify it's structurally valid before passing it downstream?”
Technical details
Endpoint
POSThttps://commerce.delx.ai/api/v1/x402/evm-event-log-shape-check?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a fast, cheap, verifiable preflight check on an EVM event log's structure before decoding, indexing, or passing it to downstream processing. It is ideal for agent pipelines that ingest blockchain events from untrusted sources and need a lightweight structural gate. Prefer it over custom validation logic when you want an auditable, pay-per-use check with cryptographic input hashing and no data retention guarantees.
Side effects
- Malformed or non-object log input may return shape_valid: false
- Missing required log fields (topics, address) may cause validation failure
- Exceeding the 128-property limit on the log object may be rejected
- Payment failure via x402 will prevent the call from being processed
- Network timeout may cause no response
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| log | object | Log supplied to EVM Event Log Shape Check; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"data": "0x",
"topics": [
"0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
],
"address": "0x1111111111111111111111111111111111111111",
"shape_valid": true
},
"schema": "delx/util-evm-event-log-shape-check/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "c99f1364b981ec0522babeb968bdf09d84b11ac29a90633dd29159f232349caf",
"external_calls": 0
},
"operation": "evm_preflight:evm_event_log_shape_check"
}
}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"