--- title: "Agent Surface: connect your website to AI agents | Hyperize" description: "Connect websites, APIs and business data to AI agents. How Hyperize builds pages, WebMCP tools, plugins and connectors with agreed permissions." canonical: https://www.hyperize.ai/en/methodology/agent-surface lang: en last-updated: 2026-10-01 --- # Connect your offer to AI. Methodology · Agent Surface An Agent Surface comprises the pages, data and functions AI agents use to interact with a business. Hyperize builds these connections. Your systems supply facts. You control access and actions. The customer task ## From a question to an enquiry. A customer asks their AI to compare a product and request a quote. We connect your website and systems to that task \[S1\]. At a glance ## One connected surface. Clear facts. Usable functions. Shopping Service Research Recruiting Shopping Service Research Recruiting Agent Surface Reference pages Product facts Answer pages Customer questions Concept pages Defined terms Indexes Linked records Facts Checks Questions Sources Agent tests Facts Checks Questions Sources Agent tests Purpose ## Find. Check. Act. 01 ### Discoverable Help agents find relevant offers. 02 ### Citable Make answers verifiable. 03 ### Usable Enable permitted actions. The content ## Four connected page types. HTML and JSON carry identical facts. 01 ### Answer pages Answer customer questions. 02 ### Reference pages Provide verifiable facts. 03 ### Concept pages Explain specialist terms. 04 ### Indexes Link relevant records. Plugins and connectors ## Choose the access route. Hyperize builds plugins and connectors for customer tasks. Plugins and connectors provide controlled access to business functions. We connect one agreed task. ### In AI assistants: Plugins & connectors Build task-specific plugins and connectors; prepare for platform review. ### On your website: WebMCP Expose tasks through WebMCP in supported browsers. ### From your systems: APIs & MCP Connect business data and functions through APIs and MCP. ### Through checkout: UCP / ACP Connect supported checkout flows with customer approval. ### What does Muse require? Meta reviews connectors before directory listing. \[S2\] Its initial connectors use APIs and task instructions. \[S3\] We prepare the integration and submission evidence. Meta decides on approval. ### Which assistants? ChatGPT / dots, Microsoft Copilot, Claude, Gemini, Muse by Meta, Perplexity, Grok Bot, OpenClaw, Hermes Agent. Potential destinations; access, availability and compatibility require project-specific checks. No certified partnership or universal compatibility is claimed. ### How do we verify it? Test reads, actions and failures before and after implementation. Connectors do not guarantee recommendations or sales. The project ## Test. Build. Verify. 01 ### Test Record successes and failures. 02 ### Build Connect pages, data and functions to your systems. 03 ### Verify Retest. Document results, access routes and limits. Limits Agree permissions first. Reading and submitting need different permissions. The public methodology explains the score; internal evaluation logic and templates remain private. Rankings and citations are not guaranteed. Next step ## Understand. Discuss. Verify. [ Methodology ### How we test. Measurement, scope and evidence. Read the methodology](/en/methodology) [ Audit + implementation ### One task first. Agree scope, access and timing. Discuss my project](/en/founding-program) [ Public evidence ### DAX 40 Index. Results from real brands. Explore the results](/en/dax40-index) Sources ## Evidence and provenance. S1 primary Hyperize methodology Hyperize · 2026-10-01 [https://www.hyperize.ai/en/methodology](https://www.hyperize.ai/en/methodology) Supports: Definition, measurement axes and public score composition. S2 primary Muse Connector Platform Meta · 2026-09-26 [https://muse.ai/platform](https://muse.ai/platform) Supports: Submission, review and directory approval. S3 primary How We Built Safety Into Muse Meta AI Research · 2026-09-26 [https://research.meta.ai/blog/security-and-safety-for-ai-agents-our-approach-with-muse](https://research.meta.ai/blog/security-and-safety-for-ai-agents-our-approach-with-muse) Supports: API connectors, task instructions and permissions. S4 primary Meet dots OpenAI · 2026-10-01 [https://learn.chatgpt.com/docs/dots](https://learn.chatgpt.com/docs/dots) Supports: OpenAI dots and permitted plugin access; availability depends on plan and rollout. S5 primary Upload and submit your plugin OpenAI · 2026-10-01 [https://developers.openai.com/plugins/deploy/submission](https://developers.openai.com/plugins/deploy/submission) Supports: Plugin submission and review; listing is not automatic. S6 primary Introducing the new Copilot Microsoft · 2026-10-01 [https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/](https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/) Supports: Copilot Home, Code and Autopilot announcement; rollout limitations apply. Hyperize defines the approach. Platform providers define their access routes and approval requirements. Last updated 2026-10-01 Next review 2026-12-26 Evidence tier proprietary Confidence A --- Canonical: https://www.hyperize.ai/en/methodology/agent-surface Machine-readable index: https://www.hyperize.ai/llms.txt