integrations
Drop it beside what you already run.
about-us.md verification is HTTP + JSON + ed25519. That means it fits inside your existing helpdesk, auth stack, API gateway, or marketing stack without replacing anything. Here are the shapes it takes.
Helpdesks & support inboxes
Zendesk
Inbound webhook verifies the envelope, tags the ticket with the verified handle + scope, and surfaces a "verified" badge in the agent view. Rejects with 401 on invalid signatures.
Freshdesk / Intercom
Same shape as Zendesk. Adds a custom field for handle and a private note carrying
the full receipt for audit.
FreeScout
First-class module (we run FreeScout too) — verified handle appears on the customer sidebar with a link to their username.md profile.
Auth & account recovery
Auth0 / Cognito
Custom social connection. Handle verification acts as a strong second factor + recovery path that survives SIM swaps and email compromise.
Keycloak
Custom Identity Provider using OIDC-shaped bridge. We run Keycloak on-prem — reference config available to design partners.
Passwordless flows
Handle verification is the passwordless factor. No magic link email, no SMS. The user proves handle ownership cryptographically.
API gateways & the agent firewall
Kong / Envoy
Filter that verifies X-Handle-Intent at the edge and injects
X-Verified-Handle downstream. Rate-limit per-handle, not per-IP.
Traefik middleware
ForwardAuth to a tiny verify service (10-line Go). Reference container in the developer docs.
Bring-your-own gateway
Any gateway that can call a verify sidecar works. The verify service is public-key-only — it's stateless and safe to horizontally scale.
Consent & marketing
- Marketing opt-in. Replace "we swear you checked the box" with a signed opt-in envelope. Passes GDPR/CCPA audit without a paper trail hunt.
- Preference sync. Customer edits preferences at preferences.sh; you receive a signed diff. No custom preferences UI in your product.
- Revocation. Customer revokes a scope; your JWKS cache expires within TTL and the next verification fails. No email loop to the compliance inbox.
Procurement & B2B
- Vendor onboarding. Replace a PDF NDA with a signed scope-of-access envelope from the vendor's business handle at about-us.md.
- Automated buyer flows. When the buyer's LLM agent (e.g. via Operator/Claude) signs a purchase intent, you know it's authorized — and by whom.
- Cross-vendor identity. The same customer handle works at your business, your reseller, and your competitor. Identity is portable; commerce is friction-free.
Custom integrations
The wire format is small enough to integrate anywhere. If you have a hook, we have an integration.