Discover / stableschedule.dev
StableSchedule
□ No challenge detectedPrepaid cron scheduling for HTTP webhooks with custom methods, headers, and bodies.
- Challenge detected
- 0 of the last 3 checks
- Last checked
- 9 Oct, 21:20 UTC
- In our index since
- 7 Oct 2026
Endpoint
curl -i https://stableschedule.dev/api/schedule/create # 402 Payment Required: pay with a MPP client, then send the request again.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/stableschedule.dev
Recent checks
7 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.9 Oct 2026
All 3 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 9 Oct, 21:20 UTC | No challenge detected | 405 | 192ms |
| 8 Oct, 12:22 UTC | No challenge detected | 405 | 62ms |
| 7 Oct, 03:20 UTC | No challenge detected | 405 | 70ms |
Questions
Did our last probe detect a payment challenge?
No. At our last probe on 9 Oct, 21:20 UTC, we detected no payment challenge.
What payment terms does StableSchedule advertise?
The listing advertises MPP, Tempo and USDC. Check the seller's current payment challenge and authentication requirements before paying.
Where is StableSchedule listed?
In mppscan. Superstables first indexed it on 7 Oct 2026.
Something wrong on this page? Tell us.