ToolVet
77trust / 100

Bridge Status

by Bridge Status Tracker in Onchain & crypto

x402 APIPassing, checked 3 h ago

The other half of bridge-route. A bridge takes minutes with funds in flight, and from the source chain alone an agent cannot tell if it completed. Tracks a transfer by its source tx hash via the LiFi status API: completed (with the receiving tx), pending (poll again), failed (with the reason), or not-found (not a bridge tx, or too early to index). Pass from/to/bridge for a faster lookup. not-found reads as 'not indexed yet', never 'failed'. Not financial advice.

GET
https://402.com.tr/api/x402/bridge-status
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
501 ms
635 ms slowest 5%
Last check
Passed
3 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://402.com.tr/api/x402/bridge-status

Each call costs $0.01 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/bridge-status?from=base&to=arbitrum&txHash=0x68fdf10f8eb842afcddf79b2a779ed78e5be35d698e95cee1966f1787eb02b5e

Parameters

ParameterTypeRequiredDescription
fromstringNoFrom chain (optional)
tostringNoTo chain (optional)
txHashstringYesSource-chain tx hash

Example response

The provider's example. We can't check it without paying.

{
  "checkedAt": "2026-10-09T11:06:26.575Z",
  "txHash": "0x68fdf10f8eb842afcddf79b2a779ed78e5be35d698e95cee1966f1787eb02b5e",
  "verdict": "not_found"
}

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.01.

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/bridge-status?from=base&to=arbitrum&txHash=0x68fdf10f8eb842afcddf79b2a779ed78e5be35d698e95cee1966f1787eb02b5e'

# 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/bridge-status?from=base&to=arbitrum&txHash=0x68fdf10f8eb842afcddf79b2a779ed78e5be35d698e95cee1966f1787eb02b5e' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Fbridge-status
const res = await pay("https://402.com.tr/api/x402/bridge-status?from=base&to=arbitrum&txHash=0x68fdf10f8eb842afcddf79b2a779ed78e5be35d698e95cee1966f1787eb02b5e");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
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/bridge-status?from=base&to=arbitrum&txHash=0x68fdf10f8eb842afcddf79b2a779ed78e5be35d698e95cee1966f1787eb02b5e")
    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

WhenResultHTTPTimePrice
3 h agoPassed402597 ms$0.01
7 h agoPassed402532 ms$0.01
12 h agoPassed402530 ms$0.01
17 h agoPassed402743 ms$0.01
21 h agoPassed402478 ms$0.01
Show 10 older checks
26 h agoPassed402474 ms$0.01
30 h agoPassed402385 ms$0.01
34 h agoPassed402394 ms$0.01
38 h agoPassed402487 ms$0.01
42 h agoPassed402505 ms$0.01
47 h agoPassed402624 ms$0.01
2 days agoPassed402534 ms$0.01
2 days agoPassed402339 ms$0.01
2 days agoPassed402477 ms$0.01
3 days agoPassed402459 ms$0.01