Documentation

Public data, captcha and runtime information

Checked against PoolNode routes, controllers, DTOs and authentication middleware in Rust revision 655097d2a5 (2026-11-02). Upstream response fields not defined locally are not guaranteed by historical examples; only confirmed request contracts are listed here.

API	Authorization and result
`GET /api/network/mergemining`	Public, no parameters; merged-mining data in standard envelope, upstream-defined data
`GET /api/quotes`	No user JWT, no parameters; requires node CODE, standard envelope with upstream data
`GET /api/project/info`	User JWT, no parameters; standard envelope, adds `node`, `version`, `start_time` to upstream configuration
`GET /api/version`	Public, no parameters; raw release-repository origin.json, not the running local version; no standard envelope
`GET /api/runtime/debug`	Public, no parameters; raw booleans `debug` and `shadow`, Cache-Control: no-store
`POST /api/captcha/image`	Public, no parameters; raw captcha-service JSON
`POST /api/captcha/check`	Public; JSON payload generated by the captcha widget, forwarded unchanged; raw captcha-service JSON

In project/info, version is the running program version and start_time is the local startup time. node contains a random prefix and is not a stable node ID. runtime/debug reads diagnostics; it does not change settings.

Captcha verification fields belong to the widget protocol; Rust accepts JSON without a fixed DTO. Prefer the documented widget to obtain a success token for email requests. Do not assume captcha responses use the standard status/data envelope.