Discover / bridge-api.argosbot.io

bridge-api.argosbot.io

■ Challenge detected

Look up Arc/Base original and wrapped token addresses, bridged supply and ownerless verification. Arc Gateway or direct Base USDC: 0.005 USDC.

Challenge detected
1 of the last check
Median response
362 ms
Last checked
3 Oct, 17:05 UTC
In our index since
3 Oct 2026

Endpoint

curl -i https://bridge-api.argosbot.io/v1/lookup
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/bridge-api.argosbot.io

Recent checks

3 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.3 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
3 Oct, 17:05 UTCChallenge detected402362ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 3 Oct, 17:05 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What payment terms does bridge-api.argosbot.io advertise?

The listing advertises x402, Base, EVM chain 5042 and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is bridge-api.argosbot.io listed?

In x402 Bazaar. Superstables first indexed it on 3 Oct 2026.

Something wrong on this page? Tell us.