Skip to main content
Choose the company surface your customer’s agent uses, not the framework the agent itself was built with. The customer does not install Epode on any path.

HTTP API

Add relevant context requests and a same-origin answer relay to selected JSON responses.

Server-rendered website

Use the server or edge that owns the response; never put the product key in browser JavaScript.

MCP server

Register company-owned permission and customer-context tools alongside product tools.

Static site or hosted docs

Use the advanced trusted-edge proxy when your team controls the public response route.

AXG edge activation

Preview and activate temporal freshness plus closed task intent through Cloudflare, Vercel, or CloudFront.

​
Supported adapters

Static-site integration requires a trusted reverse proxy controlled by your team. Never add AGENT_FEEDBACK_KEY to a static bundle. If the platform cannot route its public hostname through your edge, direct integration remains unsupported.