GrayPass checks who is in control before an agent moves money or exports data

A session cookie proves one thing: a person signed in. It does not prove who is sending the next request. An AI agent handed a human session can move money with the same cookie the person held. It can export records or change permissions the same way. GrayPass tries to answer who is acting, before the sensitive action goes through.

GrayPass launched on Y Combinator Fall 2026 on 29 October. The company says it has processed 900,000 sessions across its customers' apps. GrayPass says it reached $50,000 in revenue this month. The YC launch page had seven votes in its first hours.

What the product does

GrayPass sits beside the existing login system, the launch page says. It does not replace it. Before a sensitive action, the app asks GrayPass what to do. Sensitive actions include moving money, exporting customer data and changing an admin permission. GrayPass answers one of four things: allow, ask for more proof, hold, or deny. The app enforces the decision.

The signals GrayPass reads are typing rhythm, cursor movement and scrolling, plus device and session information. Each app sets its own rules on how those signals combine. The idea is that these signals tell a person apart from a script. They also tell a trusted script apart from one the app did not expect.

The agent angle

More apps are now called by AI agents, the launch page says. A service needs to know when an agent is acting on a user's behalf. It also needs to know whether that agent has permission for the action. GrayPass sits as a check at that line. The founders write that knowing who logged in is a different question from knowing who is taking the next action.

The numbers to notice, and the numbers to wait for

The 900,000 figure is sessions processed. The launch page gives no false-positive rate. $50,000 in a month is enough revenue to show paying customers exist. It does not yet show how its cost compares to the fraud losses it prevents. Nor does it show the cost against the sign-up friction it adds.

A buyer should ask two questions behind the pitch. First, on a batch of real sessions, how often does GrayPass stop a real person? How often does it let a shared account through? Second, when an agent is acting with the user's permission, does GrayPass tell the app that is what is happening? Or does it flag the agent as something wrong? Those numbers decide whether this is a security layer or a friction layer.

Source

• Primary source: GrayPass on Y Combinator.
• Company site: GrayPass.