Discover / shared-hold-api.onrender.com

shared-hold-api.onrender.com

□ No challenge detected

Store payload to Shared Hold boundary - 0.005 USDC per successful hold

Challenge detected
0 of the last check
Last checked
2 Oct, 17:03 UTC
In our index since
2 Oct 2026

Endpoint

curl -i https://shared-hold-api.onrender.com/hold
# 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/shared-hold-api.onrender.com

Recent checks

2 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.2 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
2 Oct, 17:03 UTCNo challenge detected200535ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 2 Oct, 17:03 UTC, we detected no payment challenge.

What payment terms does shared-hold-api.onrender.com advertise?

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

Where is shared-hold-api.onrender.com listed?

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

Something wrong on this page? Tell us.