See how Hush secures AI agents
Acme's employees ask an AI assistant for help. Watch every token and every decision, live.
You ask โ ๐ค the assistant hands the work to other ๐ค agents โ ๐ก๏ธ Hush issues each token โ ๐ฆ the IGW or your API checks it
Sign in as an Acme employee
๐Avery AnalystAcme Analystsโ Support ticketsโ Read CRMโ Update CRM
๐งญMorgan ManagerAcme Managersโ Support ticketsโ Read CRMโ Update CRM
๐งฐCasey ContractorAcme Contractorsโ Support ticketsโ Read CRMโ Update CRM
Signs in with Okta. Passwords: AWS Secrets Manager demos/acme-assist (dev account, eu-central-1).
๐ก๏ธ Hush Registry ยท gives every agent an identity, decides who may act for whom, and issues each token. ๐ฆ Hush IGW ยท checks every call to the apps behind it
๐งโ๐ผ
Employeesigns in with Okta
Your IdP: Okta, Entra, Pingโฆ
โ
๐ค
AssistantAWS AgentCore; its AWS role is its identity
Any agent platform
โ
๐ฆ through the Hush IGW
๐ค Researchโ๐ฆ Hush IGWโ๐ซ Acme Support
The IGW checks the agent, the user and the tool on every call, and holds the app's key.
๐๏ธ direct to your API
๐ค Opsโ๐๏ธ Acme CRM
The CRM checks the Hush token itself. It could be any service, an API gateway (Kong, Apigee, AWS API Gateway) or a SaaS that accepts JWTs.
No agent holds a secret. Each proves who it is with its cloud identity and gets short-lived Hush tokens naming the user it acts for and the agents in between.