Don't block the agents. Give them a lane.
Agents will soon outnumber people on your site 1000 to 1. Some are customers. Some are abuse.
Heedic tells them apart.
The problem
Right now you get two options.
Open to every agent, or to none.
Firewalls and CAPTCHAs were built for a web of people. They treat every agent as an attack.
- 01
You open your product to agents.
- 02
Someone points a script at it and abuses that access.
- 03
You turn the firewall back on. Real agents get blocked too.
1000×
more agent traffic than human traffic, soon
Agents will do a lot of the buying. They'll compare plans, sign up and check out for someone.
Block them and you block your customers.
So you need a way to let the right ones in. That's what we're building.
What you get
Stop the abuse. Keep the agents that bring you customers.
01 / identify
Know who sent it
See which agent is on your site, who runs it, and who it's acting for.
02 / decide
Set the rules per route
Verified agents can sign up. Unknown ones can read your docs. You decide, in code.
03 / observe
See it live
Humans, trusted agents and abuse, side by side, as it happens.
04 / transact
Let agents buy
Give the agents spending money on someone's behalf a clean path to checkout.
Set it up in your middleware.
Your rules live next to your code. They keep working when the abuse changes tactics.
API preview. Will change as we build with early teams.
import { heedic } from "@heedic/next";
export default heedic({
"/signup": {
humans: "allow",
agents: {
verified: { allow: true, perPrincipal: "5/day" },
unknown: "challenge",
},
},
"/checkout": { agents: { verified: "allow", unknown: "block" } },
"/docs/*": { agents: "allow" },
});From us to you
If you opened your product to agents and got burned, you weren't wrong. You were early.
We're building the tools you didn't have.
Tell us what's hitting your site. The first teams on the list help shape what we build.
— The Heedic team
Let agents back
in.
Join the waitlist.