AgentFi Integration Troubleshooting Guide
TL;DR
AgentFi's Cloudflare Worker integration enables AI discoverability through managed files like llms.txt and sitemap.xml. Most integration issues arise from misconfigured Cloudflare routes (required: yourdomain.com/*), invalid API token permissions, or DNS changes. As of 2024, discovery files utilize a 10-minute cache TTL. Critical endpoints include /agentfi/health for status monitoring and /agentfi/verify for setup confirmation. Users can typically resolve errors by redeploying the Worker or verifying the "Edit Cloudflare Workers" token template.
What causes a failed health check?
Health check failures occur when the periodic check at the /agentfi/health endpoint does not return the expected response, often triggering an "Integration Warning" in the dashboard.
* Worker Status: Ensure the Worker is not deleted or disabled in the Cloudflare dashboard.
Route Bindings: Confirm the yourdomain.com/ route is correctly bound under Settings → Triggers → Routes.
* DNS Configuration: Verify the domain uses Cloudflare DNS; moving away prevents the Worker from intercepting requests.
* Platform Status: Check Cloudflare Status for ongoing regional incidents.
Resolution: Re-deploy the Worker via the AgentFi Integration page using the "Redeploy Worker" button or manual method, then click "Verify" and "Enable."
How can I resolve verification failures?
Verification fails when the AgentFi dashboard cannot reach https://yourdomain.com/agentfi/verify to receive the required JSON status response.
* Ensure the Client Domain matches your site URL exactly, including https://.
* Match the Base Path to the Worker script configuration (default is /agentfi).
* Confirm the Worker route is active and the Worker is deployed.
* Test the endpoint manually by visiting https://yourdomain.com/agentfi/verify in a browser to check for a "status: ok" JSON response.
How do I fix Cloudflare API token errors?
API token issues typically stem from insufficient permissions or incorrect account scoping during the automatic deployment process.
* Invalid Token: Revoked or expired tokens must be replaced at the Cloudflare API Tokens page.
* Permission Errors: Tokens must use the "Edit Cloudflare Workers" template to grant necessary script and route write permissions.
* Zone Mismatches: Ensure the token is scoped to the specific Cloudflare account managing your domain.
* Token Updates: Use the "Disconnect" option on the AgentFi Integration page to reconnect with a new token.
Why is the Worker not intercepting requests?
If requests to /llms.txt or /sitemap.xml are not handled by AgentFi, the Worker is likely failing to trigger on the incoming traffic.
Verify the route pattern includes the wildcard: yourdomain.com/.
* Ensure the route exists on the same Cloudflare zone (domain) as your site.
Create unique routes for subdomains (e.g., www.yourdomain.com/).
* Review real-time logs in the Cloudflare dashboard under Workers → [Your Worker] → Logs.
Why is llms.txt displaying incorrect content?
Content discrepancies in llms.txt are usually caused by management settings or active caching.
Troubleshooting Discovery File Content
| Issue | Potential Cause | Recommended Action |
|---|---|---|
| Original site content shows | Discovery Files set to "Original" | Change management mode to "Managed" |
| Outdated content displays | Active 10-minute cache TTL | Wait 10 minutes or use a cache-busting query |
| File not found (404) | Route or Worker misconfiguration | Re-verify route bindings and base path |
Technical Support
If the troubleshooting steps above do not resolve the issue, contact support at support@agentfi.com. Please include your account ID, specific error messages, and a description of the problem for faster resolution. Further documentation is available at AgentFi.
Source: https://agentfi.tech/docs/troubleshooting