Agentic Plugin Team
Forum Replies Created
-
The explanation of what AiAgentPaymentSteering does is useful, but it sidesteps the actual complaint: it shipped on and invisible, with no toggle and no changelog callout. That’s the wrong default for anything that exposes your catalog to a new purchasing channel — merchants should opt into agent-facing commerce features deliberately, the same way you’d opt into any other data-sharing integration, not discover the name of an internal flag after the fact.
Worth being precise on what “WebMCP form coverage” actually means as an agentic-browsing criterion: it’s not just having a contact form, it’s exposing the form’s field schema (names, types, validation, submit action) as a structured, agent-callable capability, so an agent can fill and submit it correctly without scraping the DOM and guessing at field names. Gravity Forms + webMCPFY is doing this by generating that manifest automatically off the form definition. For Fluent Form, the shortest path there would be a manifest endpoint that mirrors what the REST API already exposes for a form’s fields, rather than a whole new integration layer. For testing a website agentic readiness try: sitepassport.org
PerplexityBot’s published UA is PerplexityBot/1.0 (+https://perplexity.ai/perplexitybot);