Base Withdrawal
by Base Withdrawal Finalizer in Onchain & crypto
๐ Beryl (2026-06-25) cut the single-proof withdrawal window from 7 days to 5, with a dual-proof fast path at ~1 day. Given a Base withdrawal-initiation tx, this decodes the L2ToL1MessagePasser event (the withdrawalHash, target & value needed to prove/finalize on L1) and estimates the finalization windows under the post-Beryl rules. For agents managing cross-chain liquidity.
https://402.com.tr/api/x402/base-withdrawal- Price
- $0.04
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 490 ms
- 852 ms slowest 5%
- Last check
- Passed
- 23 min ago, next in 8 min
Reliability
Status and outage history ยท Atom feed ยท Watch with other listings
How to call it
GET https://402.com.tr/api/x402/base-withdrawal
Each call costs $0.04 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://402.com.tr/api/x402/base-withdrawal?tx=0x311b9d14a7aa412e5c5a404e07c715ba6b25a5a032962785c088c246beeab302Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
tx | string | Yes | Base withdrawal-initiation txHash |
Example response
The provider's example. We can't check it without paying.
{
"initiatedAt": "2026-08-09T13:38:51.000Z",
"isBaseWithdrawal": true,
"sender": "0x4200000000000000000000000000000000000007",
"target": "0x866E82a600A1414e583f7F13623F1aC5d58b0Afa",
"tx": "0x311b9d14a7aa412e5c5a404e07c715ba6b25a5a032962785c088c246beeab302",
"value": "0",
"verdict": "likely_finalizable",
"withdrawalHash": "0xc04c8c0acfc056dc9074c50c81df41a51287d9ce2f006b3627df6a6d55599bfc"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.04.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://402.com.tr/api/x402/base-withdrawal?tx=0x311b9d14a7aa412e5c5a404e07c715ba6b25a5a032962785c088c246beeab302'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://402.com.tr/api/x402/base-withdrawal?tx=0x311b9d14a7aa412e5c5a404e07c715ba6b25a5a032962785c088c246beeab302' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.04 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.04" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.04 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Fbase-withdrawal
const res = await pay("https://402.com.tr/api/x402/base-withdrawal?tx=0x311b9d14a7aa412e5c5a404e07c715ba6b25a5a032962785c088c246beeab302");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.04 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.04"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://402.com.tr/api/x402/base-withdrawal?tx=0x311b9d14a7aa412e5c5a404e07c715ba6b25a5a032962785c088c246beeab302")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 23 min ago | Passed | 402 | 852 ms | $0.04 |
| 5 h ago | Passed | 402 | 521 ms | $0.04 |
| 10 h ago | Passed | 402 | 512 ms | $0.04 |
| 15 h ago | Passed | 402 | 445 ms | $0.04 |
| 19 h ago | Passed | 402 | 452 ms | $0.04 |
Show 10 older checks
| 24 h ago | Passed | 402 | 490 ms | $0.04 |
| 28 h ago | Passed | 402 | 542 ms | $0.04 |
| 32 h ago | Passed | 402 | 468 ms | $0.04 |
| 36 h ago | Passed | 402 | 349 ms | $0.04 |
| 41 h ago | Passed | 402 | 437 ms | $0.04 |
| 45 h ago | Passed | 402 | 607 ms | $0.04 |
| 2 days ago | Passed | 402 | 491 ms | $0.04 |
| 2 days ago | Passed | 402 | 337 ms | $0.04 |
| 2 days ago | Passed | 402 | 468 ms | $0.04 |
| 3 days ago | Passed | 402 | 904 ms | $0.04 |