Discover / boulder-api.j-a-nakagawa.workers.dev

Boulder — LingBot-Map Scene Reconstruction

□ No challenge detected

Feed-forward 3D scene reconstruction from video. Powered by lingbot-map (Apache-2.0) on a self-hosted GPU. Async wire protocol: enqueue → poll → fetch.

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://boulder-api.j-a-nakagawa.workers.dev/v1/reconstruct
# 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/boulder-api.j-a-nakagawa.workers.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)ResultHTTPResponse
9 Oct, 21:20 UTCNo challenge detected404353ms
8 Oct, 09:20 UTCNo challenge detected404258ms
7 Oct, 00:22 UTCNo challenge detected404270ms

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 Boulder — LingBot-Map Scene Reconstruction advertise?

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

Where is Boulder — LingBot-Map Scene Reconstruction listed?

In mppscan. Superstables first indexed it on 7 Oct 2026.

Something wrong on this page? Tell us.