Skip to content
Hussh
Connect MCP

PCHP brand-side endpoint

Phase 2 monetization protocol-tier. Brands and publishers request consented attention via PCHP handshakes; Hussh charges subscription/per-receipt; no inventory, no marketplace, no Hussh ad cut on impression spend.

Concept

TL;DR: The PCHP brand-side endpoint is a future Phase 2 protocol lane where brands or partners request consented outcomes through PCHP handshakes. It is not a v1 surface, not a data marketplace, and not a path for partners to receive broad user memory.

Status as of 2026-05-19: Future-state protocol lane; map partner claims to current Developer API/MCP consent/export contracts until implementation proof expands it.

Relations

  • PCHP — the protocol surface
  • One Lens — the consumer-facing complement
  • Internal Hussh operating rules — no-marketplace constraint and tagline sequencing.

What it is

The PCHP brand-side endpoint is the proposed Phase 2 monetization protocol-tier. It allows brands and publishers to request a user's consented attention via cryptographically auditable PCHP handshakes — without Hussh ever publishing inventory, matching buyers/sellers, or taking a cut on impression spend.

How it differs from One Lens

One Lens is the consumer-facing curator agent that mediates ads and content on the user's terms. The PCHP brand-side endpoint is the protocol-facing surface where brands stage requests that One Lens may or may not surface to the user.

  • One Lens sits with the user. It acts on the user's behalf. It is free.
  • PCHP brand-side endpoint sits at the protocol layer. Brands pay to call it (subscription or per-receipt). Hussh's revenue.

Why this is the right monetization shape

It threads three constraints simultaneously:

  1. Fixed rule: no Hussh ad marketplace. This is enforced by the brand/tagline sequencing and the One Lens decision that rejected the Marketplace path explicitly. The brand-side endpoint is infrastructure, not inventory.
  2. "Your data, your business" doesn't break. The user pays nothing. Brand requests carry consent receipts; users see and audit every one in their Transparency Log.
  3. Hussh actually gets paid. Subscription / per-receipt pricing on the brand side, ideally tiered by volume and feature surface (audience-precision, real-time vs batch, etc.).

Phase 2 gating

As of 2026-05-10 the brand-side endpoint is deferred. Three preconditions before it ships:

  1. 10K+ engaged users on One.
  2. Legal review on consent-receipt enforcement and brand-side compliance.
  3. PCHP RFC stable and adopted by at least one external partner so the receipt format isn't Hussh-only.

What it is not

  • Not a v1 surface. Hussh ships One + iBrokerage first. Monetization waits until trust earns it.
  • Not a marketplace. Period. (See One Lens decision.)
  • Not the same as Kai Ads; that older glossary framing contradicts the One Lens / Curator decision and remains tracked in private verification notes.

Enterprise architecture status refresh

  • Current repo truth: partner-facing PCHP endpoint language must map to existing Developer API/MCP consent/export contracts unless implementation proof expands it.
  • North-star direction: brands and partners can request consented outcomes through PCHP rather than receiving broad user memory.
  • Not shipped / not implied: partner endpoints do not replace Hussh consent, vault, PKM, or audit authority.

Sources

  • PCHP — protocol surface.
  • One Lens — consumer-facing complement.
  • Internal Hussh source note — PCHP brand-side endpoint deferred post-launch.