Back to Browse
Delx EVM Chain Match Check
x402
Delx EVM Chain Match Check is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).
Validates whether a transaction's chain ID matches an expected EVM chain ID, returning a boolean match result and audit evidence.
Price / call$0.001
Success—
StatusUnknown
How this service works
EVM Chain Match Check: EVM Chain Match Check compares transaction and expected chain identifiers from bounded caller-supplied values without an external provider. Call EVM Chain Match Check before signing, submitting, replacing, or accepting an EVM/Base transaction assembled from caller-owned data. Returns normalized transaction evidence, calculated budget or shape findings, and a fail-closed preflight status for EVM Chain Match Check as versioned deterministic JSON. Price: $0.001 USDC via x402…
Output
A JSON object containing a 'matched' boolean, the actual and expected chain IDs, a pass/fail status, and an evidence block with a SHA-256 hash of the inputs and confirmation that no external calls were made and no data was retained.
Example use cases
Preflight check before token transfer
“I'm about to send tokens and I want to confirm the transaction chain ID 137 matches my expected chain ID 137 — can you verify there's no chain mismatch before I proceed?”
Catch wrong-network transaction
“A user submitted a transaction with chain ID 1 but our app expects chain ID 8453 (Base). Can you run a chain match check to confirm they're on the wrong network so I can warn them?”
Audit log for multi-chain agent
“My agent just processed a transaction with chain ID 42161 and expected chain ID 42161 — run the EVM chain match check so I have a signed audit record with the input hash confirming the chains matched.”
Technical details
Endpoint
POSThttps://api.delx.ai/api/v1/x402/evm-chain-match-checkWhen to prefer
Use this endpoint when an AI agent needs a lightweight, auditable, privacy-preserving preflight check to confirm EVM chain ID consistency before executing a blockchain transaction — especially when a tamper-evident SHA-256 input hash and a no-retention guarantee are required for compliance or audit trails.
Side effects
- Missing required fields (expected_chain_id or transaction_chain_id) causes a validation error
- Non-integer chain ID values may be rejected
- Chain IDs that don't match return matched: false with status indicating failure, not an HTTP error
- Payment failure or insufficient USDC balance prevents execution
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| expected_chain_id | integer | Expected Chain Id supplied to EVM Chain Match Check; used only for this bounded calculation and processed in memory without retention. |
| transaction_chain_id | integer | Transaction Chain Id supplied to EVM Chain Match Check; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"matched": true,
"actual_chain_id": 8453,
"expected_chain_id": 8453
},
"schema": "delx/util-evm-chain-match-check/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "2cce3c222210e72942db98539fb969bde594c631c42bd033610c69b74484ac8c",
"external_calls": 0
},
"operation": "evm_preflight:evm_chain_match_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"