UCPtools - AI Agent Discovery for WooCommerce
| 开发者 | nolpak14 |
|---|---|
| 更新时间 | 2026年8月14日 21:53 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
/.well-known/ucp to understand what a store sells and how to buy from it. Shopify
generates one automatically. WooCommerce does not - so to an AI agent, most Woo stores
return a 404 and simply do not exist.
This plugin serves that profile from your own origin, built from your WooCommerce store,
and then records what agents do next: browse, open a checkout, pay, order.
It works with no account and transmits nothing until you enter a key.
Because you run your own server, a WooCommerce store can see the whole agent funnel. On
hosted platforms the agent talks to the platform, not to you, so nobody can show you that
traffic at all.
How it works
Your server answers the agent. UCPtools is never in the request path, so this plugin
cannot become a point of failure for your storefront.
- Free, no account: generates and serves your UCP profile, and records agent activity into a table in your own database. wp-admin shows which agents came, how many requests they made, what they did, how many orders they placed and what those orders were worth. Nothing is sent anywhere.
- Connected (optional): paste an analytics key from your UCPtools dashboard. Your profile stays in sync with the dashboard, and the recorded history is sent there for long-term history, trends, multi-store views and break alerts. History captured before you connected comes with you.
/.well-known/ can be defeated by a physical .well-known folder, an nginx
rule denying dot-directories, or a subdirectory multisite install - and every one of those
fails silently, leaving you invisible while you believe you are discoverable. So the plugin
fetches its own profile over the network and tells you exactly what an agent would get.
常见问题:
Do I need a UCPtools account?
No. Serving the profile - the part that makes agents able to find you - is free and needs no account, and so is the full local record of what agents did, including what their orders were worth. An account adds long-term history, trends, multi-store views and break alerts.
What data is recorded, and what is sent?
Recorded locally: which AI agent made a request, when, which endpoint, the HTTP status, and - for agent checkouts - the order total, currency and number of line items. Never recorded: card or payment details, customer names, emails, addresses, or any other personal data. The plugin reads commerce totals out of API responses; it does not touch customer records. With no key entered, none of it leaves your server. When you connect a key, that recorded history is sent to your UCPtools dashboard.
Where is the local data kept, and does it grow forever?
In a table in your own WordPress database. It is capped: roughly 30 days, and a maximum number of rows. Whichever limit is reached first, the oldest entries are removed.
Will this slow down my store?
No. Ordinary visitors are unaffected - a request that is not from an AI agent is ignored immediately. For agent requests the record is written after your response is composed, and sending to UCPtools happens on a scheduled background job, never during a page load.
I use a page cache. Does that break it?
Possibly, and the plugin will warn you. The profile still serves, but if your cache answers
/.well-known/ucp without running PHP, agent reads cannot be counted. Exclude that path
from caching.
更新日志:
- The two links from the settings screen to ucptools.dev now carry a campaign tag, so we can tell how many people arrive from the plugin. No data is sent from your site - the tag is part of the link, and only travels if you click it.
- Order values are now read from the REST response object rather than from a copy of the response bytes. The plugin no longer opens an output buffer at all, so it cannot interleave with a buffer opened by core, by the theme or by another plugin. Agent requests that are not served through the REST API are still recorded, without the order values.
- Declares WooCommerce as a required plugin, so WordPress checks for it before activation.
- Records the full agent funnel - browse, checkout, payment, order - not just discovery. This previously required hand-placing a separate file in wp-content/mu-plugins/.
- Agent activity is now recorded locally from install, with no account and no network call, so connecting later brings your history with you.
- wp-admin shows the full local picture - which agents came, what they did, and what their orders were worth. The plugin does not withhold anything it works out; a UCPtools account is for the hosted service around it (long-term history, trends, multi-store, alerts).
- Sending to UCPtools moved from fire-and-forget to a scheduled, acknowledged batch sync. wp-admin now reports whether events are actually arriving instead of only whether the key is valid - a valid key with nothing arriving used to be indistinguishable from success.
- Fixed: reports were rejected by the API and silently discarded, so connected stores recorded nothing at all.
- Serves /.well-known/ucp from the WooCommerce origin
- Agent detection and local "last agent seen" record, free and account-less
- Optional connected mode: canonical profile sync + agent read reporting
- wp-admin self-check and page-cache warning