For AI agents · Early access

An agent asks.
The human taps.
Anyone can verify.

Any AI agent can ask a person to approve an action and get back a signed credential any business can check. The person taps once on their phone, with nothing to install to start.

1tool call for the agent
1tap for the person
$0for businesses to check a credential

Why now

Agents can pass a text code. They can’t pass Face ID.

Agents read texts and email, so a code or tapped link only proves inbox access, not that a person agreed. Businesses are starting to block agents they can’t attribute, and new agent protocols assume a human approval step someone else provides. Verified Approval is that step: neutral, for any agent and any person, and checkable by anyone.

How it works

Ask, approve, verify.

One approval engine behind REST, MCP and OAuth. The approval binds to the exact action, so if the action changes, the approval is void.

1Agent

Ask

The agent calls request_approval with the action, an optional amount and counterparty, a hash of the exact payload, and the identity level and approval strength it needs. It gets back an approval link right away.

2Person

Approve

The person opens the link, sees which agent is asking and exactly what for, and taps 1-Click Approve: with a passkey in any browser, in our iPhone App Clip, or in our app. First time takes under a minute. After that, one tap.

3Anyone

Verify

The agent receives a signed credential and attaches it to the action. The business checks it offline against Verified’s public keys and applies its own policy. Checking is free.

Agent brief

For agents: start here.

Plain text, written for agents and the people who build them. Interfaces are planned and not live yet.

verified-approval.mdCopy
# Verified Approval · agent briefstatus: early access. Not live yet. Request access below.what: ask a person to approve one action; get a signed credential any business can verify offline.send: human (phone, email, or none to show a link to a person who is present),action {type, description, amount?, currency?, counterparty?, payload_hash},identity: human | contact | identity,strength: passkey | attested | biometricperson: opens the link and taps 1-Click Approve (web passkey, iPhone App Clip, or our app). Nothing to install to start.receive: credential (SD-JWT VC) with the decision, action hash, identity level and approval strength met.rest (planned): POST /v1/approvals · GET /v1/approvals/{id} · webhooks · JWKSmcp (planned): request_approval · get_approval · verify_approval at mcp.verified.incalso (planned): OAuth CIBA · A2A agent card · Mastercard Verifiable Intent and AP2 mappingsidentity_in: RFC 9421 HTTP message signatures (Web Bot Auth) or an API key. Unsigned calls work; the credential says so.rules: a link is transport, never proof. The credential states exactly what was checked.access: email agents@verified.inc with an email your operator reads, what you need approved and expected monthly volume.

What the credential proves

Who approved, and how hard it is to fake.

Businesses set a minimum for each. The credential states exactly what was checked and never claims more.

Identity level: who approved

human

A person approved

An approval from the enrolled person, with no claim about who they are.

contact

Plus a verified phone or email

Control of the phone number or email was checked at enrollment, with a silent carrier check where available.

identity

Plus a government ID

A government-issued ID presented from a digital wallet, such as a mobile driver’s license, where available.

Approval strength: how hard it is to fake

passkey

Passkey

Any device, nothing to install. The device may accept its passcode instead of a biometric.

attested

Attested iPhone

Approved in our iPhone App Clip or app, with Apple’s App Attest proving a genuine device running our code. Blocks emulators and cloud agents.

biometric

Biometric only

Approved in our app with Face ID or Touch ID and no passcode fallback, so an agent can’t approve even if it controls the phone.

Built for the emerging agent standards

SD-JWT VCMastercard Verifiable IntentGoogle AP2OAuth CIBAMCPA2AWeb Bot AuthW3C Digital Credentials

Careers

Join team human.

Help build critical infrastructure for the 21st century. We’re hiring senior people in sales, product, solutions engineering and legal.

See open roles

For businesses

Want proof before an agent acts?

Ask agents for a Verified Approval credential before purchases, account changes or data access, and set the identity level and approval strength you need. Checking credentials is free.

Talk to us

Early access

Get early access.

Agents and the people who build them are both welcome. A person at Verified reads every message and replies.

Email

agents@verified.inc

Include an email your operator reads, what you need a person to approve, and your expected monthly volume.

Email agents@verified.inc

An early-access MCP server and REST endpoint are coming soon. The agent brief above will list them.

FAQ

Questions, answered.

Is Verified Approval available now?

Not yet. It’s in early access. Request access on this page and we’ll reply to the email you give us.

Does the person need to install an app?

Not to start. The first approval works in any browser with a passkey or, on iPhone, in an App Clip that opens without installing. For biometric-only approvals, the person installs our app once.

How is this different from a text code or email link?

Agents can read texts and email, so a code or tapped link only proves access to an inbox. An approval is a signature from the person’s own device, bound to the exact action.

Can an agent fake an approval?

Not at the strongest level. A web passkey can accept the device passcode, so an agent that controls the device and knows it could approve. Attested approvals prove a genuine iPhone, and biometric-only approvals need Face ID or Touch ID with no passcode fallback. Businesses choose the minimum.

Does it prove who the person is?

Only at the identity level. The human level proves a person approved, and the contact level adds a verified phone number or email. The credential always states which level was met.

Which standards does it support?

The credential is an SD-JWT VC, with planned mappings to Mastercard Verifiable Intent, Google’s AP2 and OAuth CIBA, and interfaces over REST, MCP and A2A.

What will it cost?

People never pay, and we plan to keep checking credentials free for businesses. Agents will pay per approval, with a free tier.

Does it work outside the US?

It’s designed to work worldwide. The identity level depends on which digital ID wallets are available in each country.