Back to Browse
EVM Nonce Gap Check
x402
EVM Nonce Gap 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).
Checks whether the gap between a pending and proposed EVM nonce is within a specified maximum budget and whether a replacement is possible.
Price / call$0.001
Success—
StatusUnknown
How this service works
EVM Nonce Gap Check: EVM Nonce Gap Check calculates the gap between pending and proposed transaction nonces from bounded caller-supplied values without an external provider. Call EVM Nonce Gap 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 Nonce Gap Check as versioned deterministic JSON. Price: $0.001 USDC v…
Output
Returns the computed nonce gap between pending and proposed nonces, a boolean indicating whether the gap is within the specified maximum budget, and a boolean for whether a nonce replacement is possible. Also includes evidence metadata confirming no data is retained and no external calls were made.
Example use cases
Preflight check before transaction broadcast
“Before I broadcast this Ethereum transaction, check if a nonce gap of 2 is acceptable — my pending nonce is 3, proposed nonce is 5, and I want a maximum gap of 1.”
Detect stuck transaction nonce issues
“I think my transactions might get stuck — my pending nonce is 10 and I'm about to submit with nonce 14. Can you check if that gap of 4 is within a max budget of 3 and whether a replacement is possible?”
Agent-driven batch transaction nonce validation
“My agent is queuing multiple EVM transactions. Validate the nonce spacing: pending nonce is 8, proposed nonce is 9, maximum gap allowed is 2. Is this safe to proceed?”
Technical details
Endpoint
POSThttps://api.delx.ai/api/v1/x402/evm-nonce-gap-checkWhen to prefer
Use this endpoint when an AI agent or automated system needs to preflight-check EVM transaction nonces before submission to avoid gaps that could cause stuck or dropped transactions. Prefer this over manual calculation when operating in high-frequency or multi-agent transaction environments where nonce management is critical.
Side effects
- Missing required fields (pending_nonce, proposed_nonce, or maximum_gap) may cause validation errors
- Non-integer values for nonce fields will be rejected
- Negative nonce values may produce unexpected results
- Network errors may return 5xx responses
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| maximum_gap | integer | Maximum Gap supplied to EVM Nonce Gap Check; used only for this bounded calculation and processed in memory without retention. |
| pending_nonce | integer | Pending Nonce supplied to EVM Nonce Gap Check; used only for this bounded calculation and processed in memory without retention. |
| proposed_nonce | integer | Proposed Nonce supplied to EVM Nonce Gap Check; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"gap": 2,
"within_budget": false,
"possible_replacement": false
},
"schema": "delx/util-evm-nonce-gap-check/v1",
"status": "advisory",
"evidence": {
"retained": false,
"input_sha256": "b9889d09b1009c8b22542a020475a3b907ede762b24f2fafec69d286c024edfd",
"external_calls": 0
},
"operation": "evm_preflight:evm_nonce_gap_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"