For developers
Build on hussh. Ask first.
Add consent to your site with one script tag, or connect your agent to Agent One over MCP. Either way, people choose what you get.
<script src="https://hushh.ai/pchp.js"
data-subscriber="your-site.com"
data-scopes="privacy.analytics"></script>
<script>
addEventListener("pchp:consent", (e) => {
const s = e.detail.scopes;
if (s["privacy.analytics"]) startAnalytics();
});
</script>
Example. startAnalytics stands in for your own code.
How it works
How your agent asks for data.
- 1
Look
Your agent checks which scopes the person has. No guessing from a fixed menu.
- 2
Ask
It asks for one scope, with a plain purpose and an end time.
- 3
They decide
The person sees the request in Agent One and says yes or no.
- 4
You get it
On a yes, you receive only that scope, encrypted. Both sides keep a receipt.
- Consent embed
- One script tag for any site: plain HTML, Shopify, WordPress, Tag Manager or React. Setup guide
- MCP server
- Connect OpenClaw, Hermes or any MCP agent. Use the remote server with a developer token, or run
npx -y @hushh/mcp. On npm - Scope registry
- Every scope name, versioned, in one JSON file. Build against the names. scopes.json
- Agent registry
- Kinds of agents that ask, and the exact scopes each one needs. agents.json
- Blueprints
- Small, useful agents to build for Agent One, each written up end to end. Browse
- People choose what your agent gets.
- Access ends when they said it would.
- Every yes leaves a receipt.
Building something on hussh? Talk to us. We'd like to help you ship it.
Frequently Asked Questions
Is it free?
Yes. The consent embed and the registries are free and open.
What's live, and what isn't yet?
Live: the web embed, the scope and agent registries, and the consent event. Not yet: native iOS and Android SDKs. Until then, the embed runs inside an app's web view.
Does the MCP server need a token?
Yes, a developer token. Keep it on your machine, not in your code. Talk to us if you need one.
Is PCHP an open standard?
It's an open draft. You can read the spec.