Skip to content
Hussh
Connect MCP

Agent Connect — open-door agent and enterprise SSO surface

Agent Connect is Hussh's one-login SSO surface at /agent-connect, providing mobile-first onboarding for enterprise, government, and provider partners alongside the llms.txt agent index.

Product

TL;DR: Agent Connect (/agent-connect) is Hussh's one-login SSO surface providing mobile-first onboarding for enterprise, government, and provider partners with an open-door agent handshake in llms.txt.

Status as of 2026-07-27: see body.

Relations

Architectural Overview

Agent Connect is the front-door onboarding surface (/agent-connect) designed for enterprise, government, and professional service partners to connect their identity, agents, and workforce into the Hussh network in a single, mobile-first login pass.

Built as an open-door handshake, Agent Connect brings together single sign-on (SSO) identity federation, provider logo verification, and an open agent index published via llms.txt.

Core Features & Capabilities

1. Unified One-Login SSO Surface (/agent-connect)

The /agent-connect route provides a mobile-first, zero-friction authentication portal supporting standard enterprise SSO protocols (OIDC / SAML) alongside government agency onboarding registries.

2. Broadened Enterprise & Government SSO Registry

Supports day-0 agency and enterprise onboarding across healthcare, legal, financial, and government service providers, enabling automated organizational context setup and role-based consent scoping.

3. Open-Door Handshake via llms.txt

Agent Connect exposes machine-readable agent capabilities in the public llms.txt index. AI agents and autonomous systems can discover endpoint routes, authentication requirements, and open-door handshake protocols programmatically.

4. Healthcare & Specialty Directory Resolution

Integrated directly with the healthcare white pages finder, enabling specialty search (across 616k NPI-1 and NPI-2 individual providers across a 1024-ZIP ladder) with verified provider logos and instant connect triggers.

Core Features & Capabilities

1. Unified One-Login SSO Surface (/agent-connect)

The /agent-connect route is a mobile-first sign-in surface. A person signs in with an identity they already carry rather than creating a new password, and phone verification runs as a second factor afterwards through the shared account-setup routing.

2. Enterprise & Government SSO Registry

The registry spans the major workforce identity providers, the two US government identity providers used for public-sector onboarding, and the built-in consumer providers. A provider becomes a working button only once it is configured in that environment's Identity Platform project and enabled for that environment; anything not enabled is deliberately not rendered, so no button dead-ends on a person mid-sign-in. The registry is a compatibility surface, not a statement of any commercial relationship.

3. Organisational context — in design, not running

Establishing which employer a person works for is a materially stronger claim than establishing who they are, and Agent Connect does not yet make it. The brand registry that would map a verified directory or domain assertion to an organisation is deliberately empty, and the adapters that would read those assertions are written and covered by tests but not yet called by any live path. So today a successful enterprise sign-in yields an authenticated person with no organisational context attached. That is the intended fail-closed outcome rather than a gap: treating "authenticated" as "authorised" is the specific failure this design refuses, because an employer claim carries directory-listing claim rights.

Role-based consent scoping depends on that employer link and follows it. The identity model it will build on — a handle that belongs permanently to the person, plus a time-boxed, revocable affiliation that belongs to the employer to assert and to withdraw — is written and covered by tests, and is likewise not yet wired to a live signup path.

4. Open-Door Handshake via llms.txt

Agent Connect exposes machine-readable agent capabilities in the public llms.txt index, live in production. AI agents and autonomous systems can discover endpoint routes, authentication requirements, and open-door handshake protocols programmatically.

5. Healthcare & Specialty Directory Resolution

Integrated with the healthcare white pages finder, enabling specialty search over the published NPI-1 and NPI-2 provider index with verified provider logos and instant connect triggers.

Sources