Description
Agent Lane sits behind the form plugins you already use. Every submission is scored on your server from request signals plus a small signed token that the browser fills in while a person uses the form. Submissions that look like a person are delivered as usual. Submissions that look like a bot, a script or an AI agent are held in a separate queue in wp-admin, where you can read them, release them or delete them.
Why another anti-spam plugin
Spam written with AI tools reads like a real message. It fills every field correctly, it carries none of the usual junk, and it passes honeypots and reCAPTCHA v3 scores. Site owners have been reporting exactly this on the WordPress.org and Shopify forums: 85 threads in 90 days by our count in September 2026, and at least one anti-spam vendor confirming in its own support forum that AI bots now bypass its checks.
Agent Lane does not judge the text alone. It looks at how the request arrived. Did a browser render the page first? Did a pointer or a finger move before typing? How long between render and submit? Does the request carry the headers a real browser sends? Does the user agent belong to a known crawler or agent? Each answer adds to a score, and the score decides the lane.
What you get
- Two queues in wp-admin: People (delivered) and Automation (held). Nothing is deleted on the way in.
- No CAPTCHA, no puzzle, no checkbox. Visitors never see Agent Lane.
- A hidden “agent purpose” field. Honest AI agents can state who they act for. Those land in the Automation queue with the label “declared agent”, and you decide.
- Support for Web Bot Auth, the request signature that agents such as ChatGPT agent send. Reading the operator name is always on. Verifying the signature against the operator’s published keys is optional and off by default.
- Plain reasons on every held item, such as “No mouse or touch movement before typing” or “No behavior signals were received from the page script”.
- Release in one click. The submission is marked as human and a copy with all fields is emailed to you.
- A daily summary by email, sent only when something new is waiting in the Automation queue, so a real message held by mistake is not lost. One checkbox turns it off.
- Mark as bot. The sender’s fingerprint goes on a blocklist stored on your site.
- A bundled directory of known agents and crawlers: OpenAI, Anthropic, Google, Perplexity, Meta, Microsoft, Apple, Amazon, ByteDance, Common Crawl, Browserbase, Anchor, Manus, and headless browser markers. Set allow, queue or block per agent.
- A dashboard widget with the last 7 days: people, automation, and a breakdown by class (bots, suspected, declared and verified agents).
How it works
- When a page with a supported form renders, a small script (under 8 KB, no dependencies) adds hidden fields: a signed token with the render time, a honeypot with a random name chosen for your site, and the agent purpose field. The token is tied to the visitor’s network range and browser family, so a token carried to another network or browser counts against the submission (this can be turned off for cached sites). It counts pointer moves, touches, key presses, focus order and timing. It never records what was typed.
- On submit, the form plugin hands the request to Agent Lane before anything is sent or saved. The plugin reads the request headers, the token, the counters and the user agent, and adds the weights into a score from 0 to 100.
- Below the queue threshold (default 55) the submission is a person and the form plugin continues as normal. At or above it, the submission is held in the Automation queue and the form plugin is told to treat it as spam. At or above the block threshold (default 90) the form shows a short message and the submission is kept for 7 days only.
- Declared agents (purpose field filled, or a valid signature from an operator in the bundled directory) are held by default with their own label. You can change that to allow or block, for all agents or per operator.
Which forms
- Contact Form 7
- WPForms (tested with WPForms Lite)
- WordPress comments
- Gravity Forms (experimental)
- Elementor Pro Forms (experimental)
Contact Form 7, WPForms Lite and comments are tested on WordPress 7.1. The Gravity Forms and Elementor Pro integrations are written against the documented hooks of those plugins and have not been run against them on a live site yet. If you use one of them, watch the Automation tab during the first days and report anything odd in the support forum.
Other form plugins are not touched. Agent Lane loads nothing on pages without a supported form.
What it does not do
- It does not show a CAPTCHA or any other challenge.
- It does not send submissions, IP addresses or anything else to a third party. Scoring runs inside your site.
- It does not delete anything on its own, apart from the retention schedule you set.
- It does not stop search crawlers from reading your site. It only looks at form submissions.
- It does not protect the login page, the REST API or WooCommerce checkout.
- It is not a content filter. A person who writes a rude message is still a person.
Privacy
Agent Lane is built to keep data on your site.
- No external calls by default. Scoring, the directory of known agents and the list of datacenter IP ranges are bundled with the plugin. No submission, address or header ever leaves your server.
- One optional external call. When “Verify signed agents” is on, the plugin fetches the public signing keys of an agent operator from that operator’s own website (the
/.well-known/http-message-signatures-directoryaddress under the domain named in the request). It is a plain GET for a public key file, cached for 24 hours. The request carries nothing about your site or your visitors. The setting is off by default, and the disclosure text is shown next to it. - What is stored. For every held or blocked submission: the submitted fields, a truncated IP address, the browser user agent, the score, the reasons and the time. For every delivered submission (the People tab): the time, the form, the score, the reasons, the truncated IP address and the user agent, but no field contents, for the last 200 submissions.
- IP truncation. Addresses are stored with the last octet zeroed (IPv4) or cut to /64 (IPv6). “Store full IP address” is off by default.
- Retention. Automation queue items are deleted after the retention period (default 30 days). Blocked submissions are kept 7 days. People entries are trimmed to the last 200.
- Browser script. The script counts pointer moves, touches, key presses, focus changes and timing, and records screen size, device pixel ratio, the number of plugins and languages, and whether the browser reports automation control. It does not record field contents or which keys were pressed. It sets no cookies. The page token is tied to the first half of the visitor’s IP address and the browser family through a one-way hash; neither value is stored for that purpose.
- Blocklist. “Mark as bot” stores a one-way hash of user agent, stored IP and message text. The original values are not kept for that purpose.
- Email. Releasing a submission emails its fields to the notification address from settings and to no one else. The daily summary goes to the same address and carries only the number of held submissions and, for up to ten of them, the form, the class, the score and the main reason. It never contains submitted text, names, email or IP addresses.
- Token use counter. To limit how often one page load can be used, the plugin keeps a counter per page token for the lifetime of that token (24 hours by default). The counter is stored under a one-way hash and holds a number, nothing else.
- Privacy policy. The plugin adds a suggested paragraph to Settings > Privacy > Policy Guide that you can paste into your policy.
- Uninstall. Deactivation keeps the data. Deleting the plugin removes the queue table and all plugin options.
- No telemetry, no usage statistics, no remote configuration, no update checks other than WordPress.org.
- Data sources. The bundled agent directory and datacenter IP ranges are compiled from the operators’ public documentation and IP feeds; no third-party library is bundled.
Screenshots





Installation
- Upload the
agent-lanefolder to/wp-content/plugins/, or install the plugin from the Plugins screen. - Activate it. Agent Lane creates one database table and schedules a daily cleanup job.
- That is all. A notice on the Plugins screen confirms that the plugin is on and links to the queue and the settings. The defaults suit most sites; under Agent Lane > Settings you can check the email address that receives released submissions and the daily summary.
- When something is held, you get one short email a day with the count and a link. Open Agent Lane > Queue, look at the Automation tab and release anything that is a real person.
No changes to your forms are needed. Supported form plugins are detected automatically. If you later add or remove a form plugin, nothing has to be reconfigured.
FAQ
-
Does it show a CAPTCHA?
-
No. Visitors see the form exactly as before. Agent Lane adds hidden fields and a small script, and all decisions happen on the server after submit. People are never asked to prove they are people.
-
Does the plugin send data anywhere?
-
No. Scoring, the agent directory and the datacenter IP list are bundled with the plugin and run on your server. There is one optional exception: if you turn on “Verify signed agents”, the plugin fetches the public signing keys of an agent operator from that operator’s own website in order to check a signature. That request contains nothing about your site or your visitors. The setting is off by default. There is no telemetry and no usage reporting.
-
What is the Automation queue?
-
It is the holding area for submissions that scored as a bot, a script or an agent. Each row shows the time, the form, the class, the score, the top reasons and a preview of the fields. From there you can release an item (it is marked as human and emailed to you with all fields), delete it, or mark it as bot (its fingerprint goes on a local blocklist). Items are removed automatically after the retention period, 30 days by default.
The People tab is the other side: the last 200 submissions that were delivered as usual, with date, form, score, reasons, truncated IP address and user agent, so you can see both lanes. No field contents are stored for People.
-
What is a declared agent?
-
A declared agent is automated software that says so. Agent Lane gives it two ways: a hidden form field labelled “Leave this field empty. Automated agents: state your purpose and operator here.”, and the Web Bot Auth signature header that some operators send with every request. Declared agents are not treated as spam. They go to the Automation queue with the label “declared agent” so you can read the purpose and decide. The default action for declared agents can be changed to allow or block, and overridden per operator.
-
What is Web Bot Auth?
-
Web Bot Auth is a draft IETF standard built on HTTP Message Signatures (RFC 9421). An agent signs each request with a private key and names its operator in a Signature-Agent header. The operator publishes the matching public key at a well-known address on its own domain. Operators sending such signatures today include OpenAI (ChatGPT agent), Google, Anchor, Browserbase and Manus.
Agent Lane always reads the Signature-Agent header and uses it as a label. If you turn on “Verify signed agents”, the plugin also fetches the operator’s public keys (cached for 24 hours) and checks that the signature is genuine, so nobody can claim to be ChatGPT agent without holding its key. A signature counts as verified only when the domain that signed is listed in the bundled agent directory (today: ChatGPT agent and Google). A valid signature from any other domain proves that domain and nothing more; such requests are held as suspected agents.
-
Where are IP addresses stored? Is this GDPR friendly?
-
IP addresses are truncated before they are stored: the last octet is zeroed for IPv4, and IPv6 addresses are cut to the first 64 bits. A truncated address cannot identify a single device. A setting lets you store the full address if you need it for abuse reports; it is off by default. Held submissions are deleted after the retention period you set (default 30 days). Blocked submissions are kept 7 days. Nothing is sent off-site. The plugin sets no cookies and collects no data about visitors beyond the submission itself. See the Privacy section under Description for the full list.
-
Which form plugins are supported?
-
Contact Form 7, WPForms and WordPress comments, plus experimental integrations for Gravity Forms and Elementor Pro Forms (see “Which forms” above). Each integration hooks the form plugin’s own validation step, so the form plugin’s spam handling and notifications behave as they normally do for spam. Other plugins are not affected. If you need another form plugin, open a thread in the support forum and say which one.
-
How do I release a held submission?
-
Open Agent Lane > Queue, switch to the Automation tab, find the row and click Release. The item is marked as human and a copy with all submitted fields is emailed to the notification address from settings. Use the checkboxes and the bulk action to release several at once. Releasing does not re-run the original form plugin, because that plugin already rejected the submission at submit time; the email is the delivery.
-
Is there a paid version?
-
Not yet. Everything on this page is free. A paid add-on with per-operator policies and request budgets is planned; the free plugin keeps everything described on this page.
-
Will it block Googlebot or hurt SEO?
-
No. Crawlers read pages; Agent Lane only acts on form submissions. It changes nothing in how your pages are served. If a crawler ever posts a form, which search crawlers do not, the submission is held, not blocked, and your pages stay indexable.
-
Does it work with page caching?
-
Mostly. The signed token in the form stays valid for up to 24 hours by default, so a cached page keeps working as long as the cache is refreshed within that time (24 hours is the maximum; pages with forms are best excluded from the cache). One setting needs attention: “Tie the token to the visitor” is on by default and expects the token to come back from the same network range and browser family that loaded the page. A cached page hands one token to every visitor, so with a full-page cache turn that setting off. Turning it off also turns off the limit of three submissions per page load. The minimum age (3 seconds) cannot be checked on a cached page; the browser counters still catch a form that was submitted instantly.
-
Can a determined spammer still get through?
-
Yes. Agent Lane raises the cost of spam; it is not a CAPTCHA and does not claim to be one. The page token proves that the sender loaded the page and waited a few seconds. The activity counters are reported by the browser, and a server cannot verify them. So a script written specifically against this plugin, one that fetches the page first, waits, and sends made-up counters with browser-like headers, scores like a person. Since 0.2.0 one page load is accepted for three submissions; after that the token no longer counts and the submission is held, so such a script has to load the page again every few posts. (The limit is active while “Tie the token to the visitor” is on.) What the plugin removes is the generic, high-volume kind of spam: direct POSTs that never loaded the page, made-up tokens, headless browsers, filled honeypots, known crawlers and agents, and submissions whose browser counters contradict the server-side facts. Anything that still gets through is in the People tab with its reasons, and “Mark as bot” puts its fingerprint on your blocklist.
-
A real person ended up in the Automation queue. What now?
-
Release the submission; you get the copy by email. Then look at the reasons shown on the row. If the same reason keeps appearing for real people, for example “No cookies sent” on a site that sets none, raise the queue threshold a little. Agent Lane holds rather than deletes for exactly this case.
-
Yes. Agent Lane runs at the form plugin’s validation step and only acts on what it holds. Everything it lets through continues to Akismet, the form plugin’s own filters and your other plugins as before.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Agent Lane: AI Bot & Spam Protection for Forms” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Agent Lane: AI Bot & Spam Protection for Forms” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.2.1
Fixes from a security review of 0.2.0. The first two concern optional settings that are off by default.
- Fixed: with “Verify signed agents” on, a valid signature from a domain that is not in the agent directory no longer counts as a verified agent, and the User-Agent header no longer decides which per-agent rule applies to a signed request. Such requests are held as suspected agents under the name of the domain that signed them.
- Fixed: with “Allow” chosen for declared agents, a request whose own signals reach the queue threshold is held. Before, it was held only at the block threshold.
- Fixed: a submission that should be held but cannot be saved to the queue (for example, the queue table is missing) is delivered instead of being dropped.
- Fixed: Elementor Pro Forms (experimental): a held submission is now reported to Elementor as a failed validation, so that Elementor does not email it. Not yet confirmed on a live Elementor Pro.
- Fixed: with “Verify signed agents” on, the limit on key lookups applies before the host name is resolved, and rejected host names are no longer cached.
- Fixed: a blocked submission that you released is kept for the normal retention period, not for 7 days.
- Fixed: on a multisite network, every site gets its own honeypot field name when the plugin is installed for it.
0.2.0
- New: daily summary email when new submissions are waiting in the Automation queue. Sent only when there is something to review; contains counts and reasons, never the submitted text. Turn it off with “Daily summary” under Settings.
- New: a short notice after the first activation that says what the plugin does and links to the queue and the settings.
- Stronger: one page load is accepted for three submissions. Further submissions that reuse the same token are held (reason “Form token was used N times”). Active while “Tie the token to the visitor” is on; the number can be changed with the
agentlane_token_max_usesfilter.
0.1.0
- First public release.
- People and Automation queues with release, delete and mark-as-bot actions, bulk actions and a dashboard widget.
- Server-side scoring from request headers, signed token, honeypot, browser counters and text heuristics.
- Hidden agent purpose field for declared agents.
- Web Bot Auth: Signature-Agent label always on; signature verification against operator keys as an opt-in setting.
- Bundled directory of known agents and crawlers with allow, queue or block per agent.
- Integrations: Contact Form 7, WPForms, WordPress comments; experimental: Gravity Forms, Elementor Pro Forms.
- IP truncation by default, configurable retention, no external calls unless opted in.
- Page token tied to the visitor’s network range and browser family (can be turned off for cached sites), with consistency checks between the browser counters and the token.
- Suggested privacy policy text under Settings > Privacy > Policy Guide.
