Reference
Documentation
Endpoints, keys, limits, response shapes.
Open docsInsights
Research &
product reading.
Case files, method notes and the newsletter — all in one place, all written after the work rather than before it.
Six surfacesNo paywall
Reference, not opinion
Method and changelog are factual pages: what the tool does and what changed. The opinion lives in the notes.
Files with the failures in
Case write-ups keep the pivots that went nowhere, because a clean story is not a method you can reuse.
Sent, not chased
One monthly email. The archive stays open, so nothing is locked behind a signup.
Everything written down.
Each link opens a different format: reference, investigation log, or diary entry. Nothing is duplicated between them.
01NewsletterProduct news and module drops, once a month.02Case studiesOPSEC-safe investigation write-ups with the dead ends.03MethodHow we structure a lookup narrative.04API docsREST reference for api.inquire.sh.05ChangelogWhat shipped recently, in order.06Field notesShort build entries from the workspace.
Start where the question is.
If you are validating the product, read the method. If you are validating the tooling, open the docs.
The console is the canonical answer.
Whatever a page here claims, you can re-run it against a real subject.