Reading the API surface…
ChoonDevelopPlayground
demoThis build is a demo. The catalog and detections are a fixed sample.Scopereading…Sound is used for one thing: a short tone when a long scan finishes while this tab is in the background. The A/B listening check plays audio either way, because there the sound is the evidence.Reading the API surface…
What does this endpoint actually return, right now, from this browser?
Reading the service's route table…
{param} can be filled in and a query string added. It is sent verbatim.curl -s '$CHOON' \ -H 'accept: application/json'
The same call, as curl. It goes through this origin’s proxy, which signs the request with your gcloud identity — no API key is involved, on this page or in the curl.
Nothing has been sent yet.
This is an empty console, not an empty result: no request has been made, so there is nothing to report about the endpoint. Press Send and whatever comes back — including a failure — appears here verbatim.
Reads made here are appended to the request log, which holds this browser session and nothing else.
Writes made from this page are not in that log.
lib/devlog.ts types an entry’s method as the literal 'GET'. A write could be appended only by widening that type — the file is another surface’s — or by recording a POST as a GET, which would put a false row in the one record on this page that is supposed to be true. So a write is issued, measured and shown above, and it is absent from the log rather than misrepresented in it. Server-side request logging does not exist either: nothing records a call made with curl, from another tab, or by anyone else.