Agent Connect — open-door agent and enterprise SSO surface
Agent Connect sign-in and agent index, with July 2026 verified limits on organizational context and role-based scoping.
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-30: dated source and runtime review; current deployment should be rechecked before making a live-availability claim.
Relations
Architectural Overview
Agent Connect is designed as a 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.
Capability status at the 2026-07-30 review
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
The July 30 review recorded machine-readable agent capabilities at the public /llms.txt index in production. Its current deployed response has not been rechecked for this update. AI agents and autonomous systems can discover endpoint routes, authentication requirements, and open-door handshake protocols programmatically.
5. Healthcare & Specialty Directory Resolution
The July review described integration with the healthcare white pages finder for specialty search and connect actions. Current index coverage and logo verification need a fresh source check before being stated as live capabilities.
Sources
- July 2026 Agent Connect code and environment review; current deployment not rechecked in this update.