Back to Browse
Delx Commerce — EVM Calldata Shape Check
x402
Delx Commerce — EVM Calldata 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 and byte count of EVM calldata without retaining or executing it
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 with the original calldata, byte count, a boolean shape_valid flag, the operation name, a status field ('pass' or 'fail'), and an evidence block confirming no data was retained, no external calls were made, and providing the SHA-256 hash of the input for auditability.
Example use cases
Pre-broadcast transaction calldata sanity check
“Before I broadcast this transaction, can you check whether this calldata is structurally valid — 0xa9059cbb00000000000000000000000012345678901234567890123456789012345678901234 — and tell me the byte count?”
Agent pipeline preflight for EVM transactions
“My agent is about to submit a batch of EVM transactions — can you run a shape check on this calldata first to catch any malformed encoding before it hits the network: 0x23b872dd000000000000000000000000abcdefabcdefabcdefabcdefabcdefabcdefabcd?”
Debugging malformed smart contract calldata
“I think something is wrong with the calldata my app generated — can you inspect this hex string and tell me if it passes the EVM shape check and what the byte count is: 0x70a08231000000000000000000000000deadbeef?”
Technical details
Endpoint
POSThttps://commerce.delx.ai/api/v1/x402/evm-calldata-shape-check?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need a lightweight, stateless, pay-per-call structural validation of EVM calldata before submitting a transaction on-chain. It is ideal for agent pipelines performing preflight checks, since it guarantees no data retention, no external calls, and provides a verifiable SHA-256 evidence trail. Prefer it over general-purpose code execution or on-chain simulation tools when you only need to confirm calldata encoding shape and byte count.
Side effects
- Calldata exceeds 8192 character limit — request rejected
- Non-hex or malformed string input — shape_valid returns false
- Payment failure via x402 — 402 response returned before processing
- Empty calldata field — may return validation error or shape_valid false
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| calldata | string | Calldata supplied to EVM Calldata Shape Check; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"calldata": "0xa9059cbb0000000000000000000000001111111111111111111111111111111111111111",
"byte_count": 36,
"shape_valid": true
},
"schema": "delx/util-evm-calldata-shape-check/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "1048e8d74a53c6ea3249086735deac2cb24ee3dd131a3852df0439253301d8de",
"external_calls": 0
},
"operation": "evm_preflight:evm_calldata_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"