You have reached api.quovadit.org, the machine-facing surface of quovadit. This host speaks JSON, not HTML. Everything served from here exists for exactly one consumer: the quovadit application. If you were expecting a website, you are holding the wrong endpoint; the interesting parts of quovadit live in the app, and the app knows where to knock.
Behind this address runs the API layer that keeps quovadit supplied with data. It answers requests, resolves identifiers, aggregates what needs aggregating, and otherwise keeps quiet. There is no sign-up form, no dashboard, no changelog, and no feed to subscribe to. It is infrastructure: deliberately boring, deliberately narrow, deliberately good at its one job.
It is not a public data service, not an open platform, and not a place to scrape. The API is provisioned for the quovadit app and its legitimate operational traffic. Requests that arrive without a good reason will receive exactly what they deserve: nothing of interest. Automated visitors are kindly invited to close the connection and spend their entropy elsewhere.
Yes, something is listening. Yes, it is healthy. No, that is not an invitation. The observable state of this service — up, boring, and quietly doing its work — is the entire amount of information this page will ever disclose. Anything beyond that lives one authentication boundary further, and that boundary is not on this page.
service: operational · uptime: unremarkable · vibes: excellent