Works wherever your site does.
Vercel, Netlify, Fastly, AWS, your own servers. No DNS change, no proxy, and no moving your traffic onto someone else’s network.
- Vercelworks
- Netlifyworks
- Fastlyworks
- Cloudflareworks
- AWSworks
- Your own serversworks
Keep your CDN for DDoS and caching. Add Shirimlabs for the AI agents that get past it, with no change to how your traffic flows.
Vercel, Netlify, Fastly, AWS, your own servers. No DNS change, no proxy, and no moving your traffic onto someone else’s network.
Each request is checked as it arrives, including calls to your API, and the session is watched from the first page to the last. An agent caught on the page stays caught on the API behind it.
Some agents are worth letting in, for a price. Set a price, and blocked agents get a standard payment request instead of a wall. They pay by card or stablecoin and come back in, all from the same console.
HTTP/1.1 402 Payment Required
{
"price": "$0.50",
"scope": "/reports/*",
"accepts": [ x402, card ]
}| Compared | Shirimlabs | Cloudflare |
|---|---|---|
| Setup | Works on any host. Your DNS and traffic stay where they are. | Move your DNS to Cloudflare so traffic runs through its network. |
| How it decides | Every request as it arrives, including calls to your API, and behavior across the whole session. | A bot score per request at the edge, plus session behavior (Precursor) since July 2026. |
| What you can do with an agent | Allow, challenge, block or charge, set per site. | Block or challenge. |
| Charging agents | Built in, over HTTP 402 and x402. | Pay per crawl, a separate product for crawlers. |
| Getting started | Sign up online and start on the free plan. | Sign up online; Bot Management is an Enterprise add-on. |
Keep Cloudflare in front for DDoS and caching, and add Shirimlabs for the agents that pass it.
| Compared | Shirimlabs | Akamai |
|---|---|---|
| Setup | Works on any host. Your DNS and traffic stay where they are. | Traffic runs through Akamai’s edge. |
| How it decides | Every request as it arrives, including calls to your API, and behavior across the whole session. | Mostly network signals at the edge, such as TLS and connection timing. |
| What you can do with an agent | Allow, challenge, block or charge, set per site. | Allow, block or challenge by agent. |
| Charging agents | Built in, over HTTP 402 and x402. | Through partners (TollBit, Skyfire). |
| Getting started | Sign up online and start on the free plan. | Sales-led, on enterprise contracts. |
Akamai handles the network layer; Shirimlabs watches what agents do on the page.
| Compared | Shirimlabs | DataDome |
|---|---|---|
| Setup | Works on any host. Your DNS and traffic stay where they are. | A script plus a server or CDN integration. |
| How it decides | Every request as it arrives, including calls to your API, and behavior across the whole session. | Request and session behavior, with a trust score per agent. |
| What you can do with an agent | Allow, challenge, block or charge, set per site. | Allow, block, rate-limit or charge. |
| Charging agents | Built in, over HTTP 402 and x402. | Yes. |
| Getting started | Sign up online and start on the free plan. | Sales-led, priced for enterprises. |
Already on DataDome? Shirimlabs runs alongside it, so you can compare what each one catches on your own traffic.
| Compared | Shirimlabs | HUMAN |
|---|---|---|
| Setup | Works on any host. Your DNS and traffic stay where they are. | A script plus a server or CDN integration. |
| How it decides | Every request as it arrives, including calls to your API, and behavior across the whole session. | Session behavior plus network reputation. |
| What you can do with an agent | Allow, challenge, block or charge, set per site. | Allow or block by agent (AgenticTrust). |
| Charging agents | Built in, over HTTP 402 and x402. | Not part of its public product. |
| Getting started | Sign up online and start on the free plan. | Sales-led, priced for enterprises. |
Already on HUMAN? Shirimlabs runs alongside it, so you can compare what each one catches on your own traffic.
| Compared | Shirimlabs | AWS WAF |
|---|---|---|
| Setup | Works on any host. Your DNS and traffic stay where they are. | Runs in front of AWS: CloudFront, load balancers or API Gateway. |
| How it decides | Every request as it arrives, including calls to your API, and behavior across the whole session. | Request signals, matched against a catalogue of 650+ known bots and agents. |
| What you can do with an agent | Allow, challenge, block or charge, set per site. | Allow, block, challenge or CAPTCHA. |
| Charging agents | Built in, over HTTP 402 and x402. | Yes, over x402. |
| Getting started | Sign up online and start on the free plan. | Turn it on in your AWS account, billed per request. |
Keep AWS WAF for rules at the edge, and add Shirimlabs to watch behavior in the browser.
From each vendor’s public documentation and announcements, reviewed October 2026. Products change quickly; if something here is out of date, tell us and we’ll fix it.
Yes. Shirimlabs doesn’t touch your DNS or routing, so it works behind any CDN or firewall you already have.
A CAPTCHA asks every visitor to prove they’re human. Shirimlabs works quietly in the background, and only agents ever see a challenge, if you choose to show one.