Free store auditFeaturesAgent RevenueHow detection worksStrategiesPricingFor agenciesBlogSign inStart free
Tactical docs · Gate

Personal Agent Protocol

What Tactical does with the Personal Agent Protocol (Poppy) 1.0: how it verifies a personal agent's session, attributes the order, applies your Gate rules, and publishes your discovery file. What it stores, and what can't be done on Shopify.

Status, 18 November 2026: beta. The WooCommerce plugin 1.6.0, on WordPress.org since 18 November, does what this page describes; it has passed on our own test store, not yet on a merchant's. Update the plugin to 1.6.0 first. Tactical Gate, whose rules this page refers to, is in private beta: Observe mode first, enforcement with design partners (join the beta).

The Personal Agent Protocol (Poppy) is an open standard for how a person's AI assistant works with a business. Version 1.0 gives a personal agent two things a store can use: a signed session on every request it makes without a browser, and a discovery file, /.well-known/poppy.json, where the store says how agents should work with it.

What Tactical does with a session

A personal agent sends a Poppy-Session header: a JWT signed by a short-lived key, with a delegation from a key the agent publishes at its own address (its client_id). When a request to your store carries one, Tactical checks it the way the spec says a business must (§5.3):

  • The delegation is signed by a key listed at the agent's client_id (ES256 or PS384), lasts at most 24 hours, and names no user.
  • The session is signed by the delegated key, is for your store (aud), for this exact request (method and URL), and was signed within the last two minutes.
  • A session ID can't be replayed on a cart or checkout request.

A verified session makes the visitor that agent, wherever it's checked: the WooCommerce plugin, the Connect-Cloudflare worker, and the demo store.

  • Your Gate rules see it. The agent has protocol pap and a session kind (guest, or signed_in when it also sends an access token). A rule can name it by its client_id, match protocol: pap or session_kind: guest, or target the personal_agent category.
  • Only a registry agent is "verified". Anyone can publish client metadata, so an agent whose client_id isn't in Tactical's agent registry is identified but not trusted: Declared and verified agents are welcome doesn't let it through, and a drop rule still applies to it (a verified session is at the high tier). An agent asked to identify itself at checkout passes once it has.
  • The order is attributed to it. An order placed in a verified session is tagged with the session on your store (order meta _tactical_pap) and attributed Agent order (protocol session): deterministic, with an evidence record naming the agent, its session and the time the checkout request was verified.
  • An invalid session changes nothing. It is never trusted and never punished: the request is decided as if it carried no header, and the decision log says why. A request without the header is never looked at. People don't send one.

A session is accepted only for your store's own address (your WordPress site address, https:// and its host). If your store also answers on another domain, add it with the tactical_poppy_hosts filter, for example add_filter( 'tactical_poppy_hosts', fn() => array( 'shop.example.com' ) );. The request's own Host header is never trusted for this: a site that answers any host name would otherwise accept a session made for someone else's store.

The agent's metadata and keys are fetched from its own site with no redirects, a 64 KB cap and a timeout, cached for an hour, and only from public HTTPS addresses. On WooCommerce a registry agent's keys may be fetched during the request (one-second timeout); any other agent's are fetched in the background, at most ten new agents every ten minutes, and its first requests are decided as unverified until they arrive.

Your discovery file

From Personal agents in your dashboard you can publish /.well-known/poppy.json on a WooCommerce store. It holds your store's name and domain and a tasks endpoint. That endpoint is the protocol's one place for your policy: your Gate rules, written as tasks agents are asked not to do, each with what to do instead. For example, a Drop protection window becomes:

{
  "excluded_tasks": [
    {
      "task": "Automated add-to-cart and checkout on the collection \"autumn-drop\" between 2026-11-21 10:00 UTC and 2026-11-21 11:00 UTC",
      "alternative": {
        "instructions": "Browse and share the product with the person; they add it to the cart and check out themselves.",
        "references": [{ "type": "web", "url": "https://yourstore.example/product-category/autumn-drop" }]
      }
    }
  ],
  "feedback": { "endpoint": "https://tactical-app.work/api/poppy/feedback/yourstore.example" }
}
  • The file asks; the Gate enforces. An agent that ignores the file still meets your rules.
  • Only rules that would apply to a personal agent are listed: not rules for crawlers, for named agents, or for agents that haven't identified themselves.
  • The tasks update with your policy, within about five minutes of a change.
  • web.disabled asks agents not to browse your site with a browser. The spec allows it only when the file lists an API or your own agent for them to use instead, so the dashboard won't publish it otherwise. Nothing enforces it.
  • Feedback: agents can report a task they couldn't complete. Tactical keeps a report only from a verified session, with the agent's client_id, and shows it on the Personal agents page.
  • Nothing is served until you publish, from a host the file doesn't name (a staging copy, for example), or on a WordPress site installed in a subdirectory, where the file can't be at the domain's root.

What Tactical stores

  • The person: never their identifier. An agent's session names the person it acts for with an ID for your store (sub); Tactical keeps only a hash of it, salted for your store, so their sessions link on your store and nowhere else.
  • The agent's client_id and session ID on Gate decisions and on the order's evidence record. A session ID is a random value the agent chooses for that session, not personal data.
  • No JWT and no access token, ever.

On Shopify

Shopify serves a discovery file for every Online Store, and passes the session to no app, so on Shopify Tactical can't verify these sessions, attribute orders to them, or publish your policy. In Shopify's own words, from our developer-forum thread, November 2026:

  • "Nothing documented today marks an order as coming from a Personal Agent Protocol session, whether that's a channel, a note attribute or an order field." Shopify's admin shows orders from personal AI agents attributed to the agent, without the protocol.
  • "There's no documented way for apps to get it through webhooks, the Admin API or Customer Events" (the session ID).
  • The Sales channels > Agentic settings don't cover a personal agent arriving through the protocol, "so those settings don't give merchants a way to control it individually today."

Tactical doesn't read Shopify orders yet: that waits on Shopify's review of the app's order access. What it shows on Shopify today is agent browsers, scored on behaviour, and the visitors AI assistants send. See Using Tactical with Shopify's Agentic channels and what this means for a Shopify store.

Headless stores

The npm middleware doesn't verify sessions yet: it runs on your own servers, where fetching an address an agent supplies needs network safeguards it doesn't have yet. Until it does, it never receives rules that depend on the protocol. The Connect-Cloudflare worker verifies sessions and applies those rules; it doesn't stamp orders.

[email protected]
How detection worksDrop WatchReadiness scannerAgent revenuePricingStrategies comparedPerformancePrivacyTerms