Check cross-chain bridge transaction status via x402 micropayment — part of a 26-endpoint DeFi intelligence API.
What it does
The `/defi/bridge/status` endpoint on the DeFi Intelligence API at defi.hugen.tokyo returns the current status of a cross-chain bridge transaction given its transaction hash. It accepts an optional `bridge` parameter to narrow the lookup to a specific bridge tool. This is one of 26 DeFi-focused endpoints covering token security audits, rugpull detection, phishing checks, bridge routing, protocol analytics, gas prices, TVL, and more.
The endpoint is gated by the x402 protocol: unauthenticated callers receive an HTTP 402 challenge advertising a price of $0.01 USDC on Base per call. No API keys or rate limits are required — payment is handled per-request via x402. Alternative access methods include a broker API (with a free key providing $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`x402-pay`). The full OpenAPI 3.1 spec is published at `/openapi.json` and a discovery document at `/.well-known/x402`.
Response schemas for individual endpoints are not documented in the OpenAPI spec (the 200 response schema is empty), so the exact shape of the bridge status response must be inferred at runtime. The probe's x402 challenge included `status: "DONE"` and `substatus: "COMPLETED"` fields as a sample, suggesting the response includes at least those fields along with sending/receiving metadata.
Capabilities
Use cases
- —Checking whether a cross-chain bridge transaction has completed, is pending, or failed
- —Monitoring bridge transfers in automated trading or portfolio management bots
- —Building dashboards that track multi-chain asset movements
- —Agent workflows that wait for bridge finality before executing the next step
Fit
Best for
- —AI agents that need programmatic bridge status checks without API key setup
- —Developers building cross-chain DeFi applications who want pay-per-call pricing
- —Automated pipelines that need to poll bridge completion status
Not for
- —Initiating or executing bridge transactions (this endpoint is read-only status)
- —High-frequency polling where per-call costs would accumulate significantly
- —Users who need detailed response schema guarantees (200 response schema is undocumented)
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
response = x402_pay.get(
'https://defi.hugen.tokyo/defi/bridge/status?txHash=0xabc123...&bridge=lifi'
)
print(response.json())Example
Response
{
"status": "DONE",
"sending": {},
"receiving": {},
"substatus": "COMPLETED"
}Endpoint
Quality
The endpoint is live (402 challenge captured) and has a published OpenAPI 3.1 spec with clear parameter definitions, but the 200 response schema is empty for all endpoints. No dedicated docs, examples, or pricing page exist beyond the challenge notice. The sample response in the challenge is minimal.
Warnings
- —Response schema for 200 is not defined in the OpenAPI spec — actual response shape must be discovered at runtime.
- —Root URL returns 404; no dedicated documentation pages (/pricing, /README, /api) exist.
- —Sample response in the x402 challenge shows empty sending/receiving objects — unclear what populated responses look like.
Citations
- —The endpoint accepts txHash (required) and bridge (optional) query parameters.https://defi.hugen.tokyo/openapi.json
- —The API is described as '26 DeFi security and data endpoints — token audits, bridge routing, protocol analytics.'https://defi.hugen.tokyo/docs
- —Price is $0.01 USDC on Base per call, as stated in the x402 challenge.https://defi.hugen.tokyo/defi/bridge/status
- —Alternative access via broker, MCP, and x402-pay SDK is documented in the challenge alternatives.https://defi.hugen.tokyo/defi/bridge/status