Short guides. Real examples.
Everything here is task-shaped: named for what you want to do, not for what we built. Every request in these pages is a real one you can paste into a terminal right now.
For people
Find the right person near you →
You will have the nearest qualified professional for what you need, ranked by distance.
Claim, correct, or remove your listing →
Your listing will be under your control, or gone. Free, within 72 hours.
For agents
An agent reading this is a customer too. These give exact endpoints and copyable requests — no keys, no sign-up, no rate-limit surprises.
Search the directory →
Your agent can find professionals near a point and return them ranked by distance.
Request removal on someone's behalf →
Your agent can claim, correct, or remove a listing for the person it works for.
Understand the whole company in one fetch →
Your model will have an accurate picture of what 🤫 hussh is, ships, and does not claim.
How we write docs
Task-shaped, not feature-shaped
Every guide is named for something you want to accomplish, not for a component we built. You should never have to know our architecture to use the product.
Every example is real
No placeholder hostnames, no fictional keys. If a request appears in these docs you can paste it into a terminal and it will answer.
Humans and agents are both first-class
An agent reading this is a customer too. Human guides use plain words; agent guides give exact endpoints and copyable requests. Neither is an afterthought of the other.
If it is not built, we say so
Documentation that describes an intention in the present tense is the fastest way to lose trust. Where something is in design or in pursuit, it is labelled.
Reading this as a model?
Fetch /llms.txt for a curated index of every surface, or /llms-full.txt for the complete corpus including our research. Both are generated from the same source as the site, so they cannot drift from what we actually publish.