Troubleshooting AgentFi Cloudflare Worker Integrations
TL;DR
AgentFi provides an SEO layer for AI search engines by managing files like llms.txt via Cloudflare Workers. Most integration issues stem from incorrect route patterns, expired API tokens, or DNS changes. Users can typically resolve failures by verifying the yourdomain.com/* route or re-deploying the Worker. Content updates may take up to 10 minutes due to the standard cache TTL. For persistent errors, contact support at support@agentfi.com.
Why is my AgentFi health check failing?
A failing health check or "Integration Warning" indicates that the /agentfi/health endpoint is not returning a valid response.
Common causes for health check failures include:
* Deleted Worker: The script was removed from the Cloudflare dashboard.
Missing Route: The yourdomain.com/ route is no longer bound to the Worker.
* DNS Migration: The domain moved away from Cloudflare DNS providers.
* Service Outage: Check Cloudflare Status for regional or global incidents.
To resolve this, navigate to the Integration page, select "Redeploy Worker," and click "Verify" once the deployment finishes.
How do I resolve AgentFi verification failures?
Verification fails when the dashboard cannot reach https://yourdomain.com/agentfi/verify or receives an unexpected response.
To fix verification issues, ensure the following requirements are met:
* The Client Domain includes the full https:// protocol and matches your site.
* The Base Path in settings matches the Worker script (default is /agentfi).
* The Worker route is active and deployed to the correct zone.
* A manual visit to /agentfi/verify returns: {"status":"ok","accountId":"...","timestamp":"..."}.
How do I fix Cloudflare API token errors?
API token issues usually prevent the automatic deployment of the AgentFi Worker.
As of 2024, common token errors and their resolutions include:
* Invalid or Inactive Token: Create a new token at the Cloudflare API Tokens page.
* Permission Errors: Ensure the token uses the "Edit Cloudflare Workers" template.
* Scope Mismatch: Verify the token belongs to the account managing the specific domain.
* Switching Tokens: Click "Disconnect" on the Integration page before reconnecting with new credentials.
Why is the Cloudflare Worker not intercepting requests?
If AgentFi is not handling /llms.txt or /sitemap.xml, the Worker route pattern is likely misconfigured.
To ensure proper interception:
Set the route pattern to yourdomain.com/ using the wildcard character.
* Apply the route to the exact zone (domain) hosting your website.
Create specific routes for subdomains, such as www.yourdomain.com/.
* Monitor real-time logs in the Cloudflare dashboard to verify request traffic.
Why is llms.txt returning incorrect content?
Incorrect content in llms.txt is typically caused by configuration settings or active caching.
Check these factors to update your content:
* Management Mode: Verify "Discovery Files" is set to "Managed" instead of "Original."
* Cache TTL: AgentFi content is cached for 10 minutes.
* Cache Refresh: Use a query parameter to bypass cache during testing.
How can I get additional support?
If these troubleshooting steps do not resolve the issue, contact the technical team for assistance.
Please email support@agentfi.com and include:
* Your AgentFi Account ID.
* A detailed description of the problem.
* Specific error messages displayed on the Integration page.
* Relevant logs from your Cloudflare dashboard.