iProov puts a human face check in the path of high-risk AI agent actions

iProov wants an AI agent’s most consequential actions to wait for a real person’s approval, backed by a face-presence check and a credential tied to the exact action. The company announced its hosted HAPS approval service on October 22, naming solo.io’s agentgateway and authorization platform Cerbos as its first integrations.

The announcement is an iProov press release distributed by Business Wire and carried by Yahoo, which labels it paid promotional material. It establishes what the company is launching and claiming; it is not an independent security evaluation.

Approval is tied to an action

In the company’s described flow, a Cerbos policy first determines that human approval is necessary. The agent action is held while iProov’s hosted service shows a named approver the action and its scope. After approval and a genuine-human-presence check, the service issues a signed, single-use credential bound to that action.

iProov says changing a payment amount or destination would invalidate the match and block execution. It also describes an auditable certificate for later logging and reference. Those are the vendor’s stated properties, not results AITrending has tested against impersonation, altered displays or replay attempts.

The division of work matters: the policy system decides when approval is required, while the approval service supplies evidence for a particular operation. That is more specific than giving an agent broad permission to act as a user for the rest of a session.

The open draft and hosted service are different products

The release builds on the Human Approval and Presence Specification published in September. The public HAPS README calls the specification an experimental draft and its reference implementation partial and not production-ready. It says the reference code implements canonicalization, hashing and a test adapter; credential-signature verification is not implemented there.

That limitation describes the public reference implementation. It does not establish that the proprietary hosted service has the same implementation gap, or independently validate the hosted service’s security.

The specification also says a presence assertion does not confer authorization. Audience, expiry, challenge and single-use identifiers need relying-party checks, and replay protection depends on atomic, persistent consumption state. Matching a presentation hash alone does not prove what a person actually saw or understood.

The open specification is Apache-2.0 licensed, but its notice excludes rights to iProov’s proprietary liveness technology, models and services. Enterprises should therefore distinguish implementing HAPS from purchasing or integrating iProov’s biometric approval service.

The announcement does not provide a public price or a complete self-service deployment recipe. AITrending verified the English announcement and public specification’s stated limits; it did not integrate or test the service.