Discover / forgesignals.org

Forge Launch Signals + x402 Verifier

□ No challenge detected

Two paid endpoints, USDC on Base (exact scheme, xpay facilitator). GET /launch-signals ($0.03): live pump.fun launch signals - up to 100 newest memecoin launches with normalized screening verdicts (class + reason + measured holder concentration %), current price multiple, 5-min buy/sell flow, unique buyers, volume, liquidity, dev rug-risk history (prior mints/migrations), and smart-money aggregates (counts + net USD flow, no wallet addresses), plus a market_pulse roll-up; every response disclose

Challenge detected
0 of the last 3 checks
Last checked
16 Oct, 23:40 UTC
In our index since
14 Oct 2026

Endpoint

curl -i https://forgesignals.org
# 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/forgesignals.org

Recent checks

14 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.16 Oct 2026
All 3 checks
When (UTC)ResultHTTPResponse
16 Oct, 23:40 UTCNo challenge detected200465ms
15 Oct, 17:07 UTCNo challenge detected200202ms
14 Oct, 08:45 UTCNo challenge detected200196ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 16 Oct, 23:40 UTC, we detected no payment challenge.

What payment terms does Forge Launch Signals + x402 Verifier advertise?

The listing advertises x402, Base and USDC. Check the seller's current payment challenge and authentication requirements before paying.

Where is Forge Launch Signals + x402 Verifier listed?

In x402-list.com. Superstables first indexed it on 14 Oct 2026.

Something wrong on this page? Tell us.