[WordPress] 外掛分享: Nexez Agent-Ready

首頁外掛目錄 › Nexez Agent-Ready
WordPress 外掛 Nexez Agent-Ready 的封面圖片
全新外掛
安裝啟用
尚無評分
13 天前
最後更新
問題解決
WordPress 5.5+ PHP 7.2+ v1.0.0 上架:2026-08-31

內容簡介

Nexez Agent-Ready 外掛可將您的 WordPress 網站與 Nexez 列表連接,讓 AI 購物代理能夠理解並交易您的報價,無需維護。它自動注入結構化數據,確保代理能夠獲取最新資訊。

【主要功能】
• 自動注入 JSON-LD 結構化數據
• 301 轉向代理路徑至 Nexez 列表
• 提供網站所有權驗證檔案
• 本地驗證 JSON 響應
• 不需編輯 DNS 即可驗證網站

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Nexez Agent-Ready」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

AI shopping agents read structured data on your server, not your design. Nexez Agent-Ready connects your WordPress site to your Nexez listing so agents can understand and transact with your offers, with nothing to maintain.
Paste your Nexez listing slug and the plugin will:

Inject your listing’s JSON-LD (schema.org offers) and a manifest into every page , server-side, so agents that read your HTML see your offers.
301-redirect the agent artifact paths on your domain (/.well-known/agent.json, /agent.json, /llms.txt, /openapi.json, and /mcp.json when enabled) to your live Nexez listing, so an agent probing yoursite.com/.well-known/agent.json always gets your current offers.
Serve the file ownership proof (/.well-known/nexez-verify.txt) so you can verify your site on Nexez without editing DNS.

Everything reflects your live Nexez listing. The plugin validates the public JSON response, encodes the JSON-LD locally, and constructs the manifest link locally. It never prints remote HTML into your site.
Privacy / network: this plugin depends on the external Nexez service at https://nexez.app/. After an administrator saves a listing slug, the plugin makes a server-side request to https://nexez.app//embed.json when its local cache is empty or expired. Full details, including the data sent and legal links, appear in the External services section below.
External services
This plugin depends on Nexez, an external software service that hosts merchant listings and their public agent-discovery artifacts.

Service website: Nexez
When a request is made: after an administrator saves a Nexez listing slug, the plugin sends a server-side GET request to https://nexez.app//embed.json when the one-hour local cache is empty or expired. This can occur while a public page is rendered, while one of the supported agent-artifact paths is requested, or while the plugin settings page checks the connection. A failed request is cached for five minutes. Saving the settings clears the cache.
Data sent: the configured public listing slug appears in the request URL. The request also necessarily exposes the WordPress server’s IP address and sends the User-Agent Nexez-Agent-Ready/; WordPress. The plugin does not include the WordPress site URL, page content, administrator details, visitor details, cookies, form values, or analytics data.
Why it is sent: Nexez uses the slug to return that listing’s public structured data, artifact URLs, and redirect map. The plugin needs this response to add JSON-LD and discovery links and to route the supported agent-artifact paths.
Data received: the configured listing’s public name, structured data, artifact URLs, and redirect rules. The plugin validates this data and constructs all WordPress output locally.
No browser requests or tracking: requests originate from the WordPress server. The plugin does not make Nexez requests from visitors’ browsers and does not send analytics or telemetry.
Administrator choice: saving a listing slug is the action that connects the site to Nexez and enables these requests. Clearing the slug disables them.
Terms of service: Nexez Terms of Service
Privacy policy: Nexez Privacy Policy

延伸相關外掛

文章
Filter
Mastodon