Agentsfeed setup, endpoints, and operations

• Domain-locked license activation and validation from the module settings screen.
• Catalog feeds for product, category, and CMS resources with predictable JSON and markdown output.
• Product JSON-LD improvements for Product, Offer, and Breadcrumb signals.
• Policy routes for `robots.txt`, `llms.txt`, and `llms-full.txt`.
• Well-known discovery metadata, API catalog, service descriptor, MCP metadata, and status output.
• Admin readiness scoring, route diagnostics, exposure controls, token controls, audit logging, and cache purge.

• PrestaShop 8.x is the primary supported target.
• PrestaShop 8.2.5 is the local development and QA target in this repository.
• PrestaShop 1.7 is supported.
• Expired licenses keep runtime behavior available but remove update entitlement; disabled, refunded, and cancelled licenses disable premium surfaces.

1. 1Download the latest `agentsfeed` module ZIP from the Agentsfeed dashboard.
2. 2Open PrestaShop Back Office and go to `Modules > Module Manager`.
3. 3Choose `Upload a module` and upload the ZIP.
4. 4Open the `Agentsfeed` module configuration screen.
5. 5Paste the license key and confirm the License API base URL.
6. 6Save settings, then select `Activate license`.

The first successful activation locks the key to the normalized production host. Localhost testing is allowed for development, but production usage should be verified from the public storefront URL that buyers and agents will use.

• `active`: module features work and updates are included.
• `expired`: module features work and updates are no longer included.
• `disabled`, `refunded`, or `cancelled`: premium routes and admin controls are disabled.
• Temporary validation failures use a network grace period rather than immediately breaking runtime behavior.

• The update server publishes the latest eligible module release to the update panel.
• Use the update panel when it reports a newer version for the current license.
• Download the ZIP from the dashboard when you need to reinstall or move through the standard Module Manager upload flow.
• After the update, open Agentsfeed settings and confirm the version, license state, route coverage, and readiness score.
• Clear the feed cache when validating endpoint changes against a live catalog.

1. 1Confirm the default AI feed setting is still appropriate for this store.
2. 2Review module-managed `robots.txt` and choose the AI crawler policy.
3. 3Review the default `llms.txt` and `llms-full.txt` output.
4. 4Check JSON-LD replacement against the theme's current structured data output.
5. 5Review exposure rules for products, categories, CMS pages, manufacturers, and locale behavior.
6. 6Open the module readiness checker and use its browser links to inspect failing route or policy checks.
7. 7Enable Agent Actions only after catalog discovery routes are stable.

1. 1Open the Agentsfeed module dashboard in Back Office.
2. 2Use the readiness checker and route coverage cards to open the feed, agent markdown, policy files, and API catalog in the browser.
3. 3Confirm each opened page matches the enabled module settings.
4. 4Fix failed checks from the module screen, then rerun readiness.

• Dashboard overview shows license state, module version, route health, and readiness status.
• License panel activates, revalidates, and displays update entitlement.
• Update panel checks the current release metadata and points eligible stores to the latest ZIP.
• Readiness diagnostics separate setup health from license activation state.
• Cache purge clears feed output when catalog, visibility, or route settings change.

• Product, category, CMS page, and manufacturer-safe filtering determine which resources can appear in agent-facing output.
• Locale settings choose deterministic fallback behavior for multilingual storefronts.
• `llms.txt` controls publish model-facing guidance and policy summaries.
• `llms-full.txt` adds richer store references, locale metadata, and expanded guidance.
• Bot rules and robots settings control crawler posture and Content-Signal output.
• Structured data controls replace or clean unreliable Product, Offer, and Breadcrumb JSON-LD from the theme.

• Agent Actions enables authenticated cart creation while keeping checkout, shipping, and payment in PrestaShop.
• Public token issuance controls whether compatible clients can request short-lived `cart:write` Bearer tokens.
• Quantity limits, token lifetime, and cart boundaries reduce accidental overreach.
• Audit log records request IDs, endpoint, token metadata, product details, cart ID, response status, and error code.
• Rate limiting tracks token or caller windows for cart-related actions.

• `GET /module/agentsfeed/feed` returns the feed index and paging policy.
• `GET /module/agentsfeed/feed/products` returns paginated product records.
• `limit` defaults to `250` and caps at `500`.
• `after_id` advances the cursor from the previous response.
• `updated_since` accepts an ISO8601 timestamp for incremental reads.
• Continue while `paging.has_more` is `true`, using `paging.next_after_id`.

• `lang` requests a storefront locale.
• Unsupported locales fall back to the configured default language.
• Inactive, hidden, or explicitly excluded entities are omitted before JSON or markdown output is built.
• Variant records are included only when combinations and attribute labels are reliable for the selected locale.

• Product and index responses include `ETag` and `Last-Modified` headers.
• Conditional requests using `If-None-Match` or `If-Modified-Since` can return `304`.
• Server-side feed cache TTL is 4 hours.
• `Accept: text/markdown` can request markdown output where supported.
• Homepage markdown negotiation uses `Vary: Accept` and `x-markdown-tokens`.
• The module readiness checker opens the relevant feed and policy pages in the browser so merchants do not need command-line checks.

• `/.well-known/mcp/server-card.json` advertises the MCP server identity and tool metadata.
• `/mcp` accepts MCP JSON-RPC requests for compatible clients.
• Catalog tools can remain read-only when cart handoff is disabled.
• Cart tooling is advertised only when Agent Actions and token flow are enabled.

1. 1Compatible clients discover OAuth metadata from `/.well-known/oauth-authorization-server` and protected resource metadata when Agent Actions and public token issuance are enabled.
2. 2Client requests a short-lived Bearer token from `/oauth/token` with `grant_type=client_credentials&scope=cart:write`.
3. 3Client sends selected products and quantities to `/module/agentsfeed/cart` or the MCP cart tool.
4. 4Module validates license state, token scope, quantity boundaries, product availability, and rate limits.
5. 5Module creates an anonymous cart and returns a checkout URL for human approval.

• Agents may prepare a cart but do not create orders or complete payment.
• The shopper reviews cart contents, shipping, and payment in normal PrestaShop checkout.
• Missing scope, expired token, disabled public issuance, disabled Agent Actions, invalid product, rate limit, and license failure all stop cart creation.
• Each attempt records a request ID so support can match storefront behavior to the admin audit log.

• Feed returns disabled or invalid: check license status, feed toggle, and production domain lock.
• Domain lock mismatch: the key has already been activated on another normalized host.
• Discovery routes missing: confirm the module is enabled, feature is usable, and route rewriting is active.
• `llms-full.txt` unavailable: confirm both `llms.txt` and `llms-full.txt` are enabled.
• Unsupported locale fallback: verify the selected PrestaShop languages and module locale settings.
• Stale product output: clear feed cache, then retry without conditional request headers.
• Token issuance unavailable: enable Agent Actions and public token issuance, then check readiness guidance.
• Temporary validation outage: wait for the license validation grace window and revalidate from admin.

1. 1Open Agentsfeed settings in PrestaShop Back Office.
2. 2Run the readiness diagnostics and review route coverage.
3. 3Open each route from the module checker: API catalog, service descriptor, status, agent card, skills index, MCP card, feed index, products page, robots policy, `llms.txt`, and `llms-full.txt`.
4. 4Confirm browser output matches the feature toggles and public token settings.

1. 1Run the admin readiness diagnostics after saving module settings.
2. 2Use the public readiness checker against the production storefront URL.
3. 3Treat pass as route or signal confirmed, warn as review needed, and fail as a setup issue to fix before launch.
4. 4Verify discovery documents only advertise routes that are truly enabled.
5. 5If Agent Actions are enabled, verify token issuance, rate limits, cart creation, checkout URL, and audit log entries.