Your customers are sending AI agents
Let the right agents in.
A customer’s agent and a scalper’s bot send the exact same request. Signet tells them apart, and you never learn who.
| Request | What Signet checked | Your rule says |
|---|---|---|
| A customer’s AI agent“Buy 2 tickets.” | a verified person behind it · #7A91… | proof of a personALLOW |
| Her second AI agent“Buy 2 more.” | same person · #7A91… · already holds 2 | over your limitDENY |
| Another AI agent“Buy 2 tickets.” | a person behind it · #C04E… · not yet verified | verify, then ask againSTEP UP |
| A bot farm’s AI agent“Buy 2 tickets.” · 23 of 47 | nobody behind it | no personDENY |
Four requests: ALLOW, DENY, STEP UP, DENY.
Why now
Agents are becoming customers.
People hand their errands to software now. The person never opens your website. Their AI agent does.
The problem
To your servers, all of them look the same.
A customer’s agent, a scalper’s bot and a scraper arrive as the same request. Bot defenses were built to stop all of them. Block, and you turn away buyers. Allow, and you let in everyone.
From the field
Reservation bots are already turning trust into an operational problem. Resy found bookings tied to bots and brokers had 4× the no-show rate and 2× the late-cancellation rate of regular users. The New York State Restaurant Association said bots were hoarding high-demand tables for unauthorized resale, leaving restaurants with empty seats and disrupting staffing and inventory planning.
Sources: Resy · New York State Restaurant Association
How it works
A real person behind every agent you let in.
The person proved themselves to Signet once and delegated to their agent. At your door, the agent proves a real person stands behind the request, to the bar you set. You receive a decision and a pseudonym. Never a name, a passport or a phone number.
- For
- #7A91… ✓ verified person
- Can
- buy tickets · 2 each
- Valid
- 30 days · set by you
- Proof
- fresh · just now
- Your rule
- a verified person · 2 tickets each ✓ met
Per person
Rules per person, not per account.
Every agent Sarah sends shows you the same pseudonym, so you count her once, however many agents she runs. To another business she is a stranger.
Sees her as
Your rule · 2 tickets per person · holds 2
Sees her as
Its own rule · its own count
Your rule says
You set the bar. The gate decides.
Each business sets its own bar per action, in plain words, from its dashboard. Signet checks it and answers in one word: ALLOW, STEP UP or DENY.
At a verified person: ALLOW, STEP UP, DENY.
Questions
What people ask first.
Five answers, each from the product as it ships. For the rest, book a call.
Does Signet see the passport?
No. Verification is secured cryptographically, so neither Signet nor you ever holds the passport data. Only derived state is kept: verified, at what level, since when, until when.
What exactly reaches me?
One word and a pseudonym. ALLOW, STEP UP or DENY, and a pseudonym for the person that is the same for every agent they send you. Never a name, a phone number or a passport.
Who enforces my limits?
You do, on the pseudonym. Two tickets each, one spot at the drop, ten agents per person: your rule, in your dashboard. Signet tells you it is the same person; it never counts for you.
What does STEP UP mean?
Verified, but not to this bar. The person behind the agent is verified, just not to the level this action needs. The agent tells them what to complete; once done, it asks again.
What about an agent with no verification at all?
Your call, per action. Turn it away, let it through with a notice to verify, or let it through. Northstar turns it away; a catalogue page might not.
Book a call
Let agents in. Keep bots out. Never see a passport.
Private beta coming October 2026, an SDK on your side of the door and an MCP integration on the agent’s. Our engineers set up your first policies with you.
Not a CAPTCHA. Not bot detection. Not KYC.