Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Architecture: The Request Path

This page is the long form of How It Works. It uses the same figure, with one section per region, and links to the pages that configure each one.

Agents on the left reach guards or the Agent Portal, which route them into the HYPR Agent Gateway; the gateway applies identity, policy, record, and tools governance, asks a supervisor's mobile app where a person is needed, and forwards to LLM providers, MCP servers, REST APIs, and provider-managed cloud agents on the right

Agents​

Agents arrive from a workstation or from a managed cloud platform:

  • A local agent runs on a workstation, such as Claude Code, Codex CLI or Cursor.
  • A provider-managed cloud agent is hosted by the provider itself, such as Microsoft 365 Copilot, AWS Bedrock AgentCore or Anthropic Managed Agents.

Each agent carries an identity the gateway can attribute. See Agents.

Guards and Portal​

An enforcement point makes sure governed traffic reaches the gateway. Endpoint Guard applies supported controls on workstations. The Agent Portal sits in front of provider-managed agents, and applies the same gateway policies to their conversations. See Enforcement Points.

Gateway​

The HYPR AgentPass™ gateway is the control point. It applies four controls:

  • Identity makes every agent attributable.
  • Policy allows a request, blocks it, or asks a person.
  • Record keeps the Request Log, and applies retention.
  • Tools governance applies role-based access, scope and lineage.

Connectors describe what the gateway forwards to. See The Four Controls.

Identity​

Three identities appear on the path:

  • The agent's own token
  • The supervisor's identity, when an agent uses it directly
  • A scoped session token, issued on a supervisor's behalf

Identity and Token Model explains what each proves and can reach. You configure them under Identity.

Supervision​

Where policy requires a person, the gateway holds the request, and asks the supervisor on the HYPR mobile app. The supervisor answers on the phone or in the console. With Require signed approvals set to Required (production), every approval carries the supervisor's passkey signature.

Agents and supervisors also communicate over two channels: a two-way chat channel, and a one-way notification channel from agent to supervisor. See the Supervisor Guide.

Providers and Tools​

On the far side are the LLM providers, MCP servers, REST APIs and managed cloud agents the gateway reaches on the agent's behalf. See Connectors.