Back to Browse
Delx Commerce — X402 Settlement Network Check
x402
Delx Commerce — X402 Settlement Network 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 whether a given settlement network matches the accepted network in an x402 payment flow, returning a pass/fail result with verifiable evidence.
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 a 'result' field containing the matched boolean, actual and expected network strings; a 'status' field ('pass' or 'fail'); and an 'evidence' object with a SHA-256 hash of the input, confirmation that no data is retained, and a count of external calls made (always 0).
Example use cases
Pre-payment network compatibility check
“Before I send the x402 payment, verify that the settlement network 'eip155:8453' matches my accepted network 'eip155:8453' so I know the routing is correct.”
Debugging mismatched x402 network
“My x402 payment is failing — can you check whether settlement network 'eip155:137' actually matches the accepted network 'eip155:8453' and show me what the mismatch looks like?”
Agent payment pipeline validation
“As part of my automated payment pipeline, confirm that the x402 settlement network 'eip155:8453' aligns with the accepted network 'eip155:8453' and return the verification evidence hash.”
Technical details
Endpoint
POSThttps://commerce.delx.ai/api/v1/x402/x402-settlement-network-check?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need a lightweight, verifiable, pay-per-call check that two x402 settlement network identifiers agree before committing to a payment flow. Prefer it over manual string comparison when you need cryptographic evidence (SHA-256 input hash) and a structured audit trail that no data was retained or external calls were made.
Side effects
- Mismatched networks return status 'fail' with matched=false
- Malformed or missing network strings may cause validation errors
- Overly long input strings (beyond 8192 chars) may be rejected
- Invalid network format strings may not parse correctly
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| accepted_network | string | Accepted Network supplied to X402 Settlement Network Check; used only for this bounded calculation and processed in memory without retention. |
| settlement_network | string | Settlement Network supplied to X402 Settlement Network Check; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"actual": "eip155:8453",
"matched": true,
"expected": "eip155:8453"
},
"schema": "delx/util-x402-settlement-network-check/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "3f67bde369ab9e2fa887e91c329b545b0ab55c7e5f31ec07cec47e8c94798178",
"external_calls": 0
},
"operation": "delivery_contract:x402_settlement_network_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"