Hosted Files

Hosted Files stores your AI visibility files on Cloudflare R2 and serves them at stable, permanent URLs. On Standard and Agency plans, a Cloudflare Worker also runs at your domain to route AI crawlers to structured summaries and inject meta tags into every page response — no server required.

Plans

Basic — $2.99/mo or $28.99/yr

• Host 1 file (your choice of llms.txt or robots.txt)
• Stable Cloudflare/R2 URL
• Works with Cloudflare auto-deploy or CNAME subdomain

Standard — $9.99/mo or $95.99/yr

• Host your full AI Visibility Kit — all 12 files at stable Cloudflare URLs
• AI crawler routing — GPTBot, ClaudeBot, PerplexityBot, and others receive a structured summary instead of your full HTML
• Auto-updated when you use AI Content Refresh

Agency — packages of 10/25/50/100 domains, from $3.99/domain/mo

• Everything in Standard across your whole client portfolio (10-domain minimum)
• Edge HTML injection — meta tags, schema markup, and canonicals injected into every page response via Cloudflare Worker
• Separate file sets and AI crawler routing per client domain

DNS setup — one CNAME record

Hosted Files uses Cloudflare for SaaS to serve your files at your domain — no Cloudflare account required on your side. After subscribing, add one CNAME record at your existing DNS provider (GoDaddy, Namecheap, Google Domains, Route 53, etc.):

your domain → serve.indexora.app

DNS changes typically propagate in under 10 minutes. Once active, your files are served directly from Cloudflare's global edge at your domain — no server management, no maintenance.

If you are on Cloudflare and prefer the full auto-deploy (Worker installed directly in your account), see the Cloudflare auto-deploy method instead.

Request limits

Every hosted file request — whether from an AI crawler, an agent fetching your llms.txt, or a direct browser visit — counts against your monthly limit. Limits reset automatically on the 1st of each month.

What counts as a request? Any HTTP fetch to a file served by the Indexora Worker at your domain — e.g.yourdomain.com/llms.txt, yourdomain.com/robots.txt, yourdomain.com/ai-index.json, etc. Cached responses at the CDN edge do not consume quota. Only requests that reach the Worker are counted.

80% warning

When your monthly usage reaches 80% of the limit, Indexora fires a one-time alert for that month:

• Dashboard badge — a usage bar on your subscription card turns amber and displays how many requests remain.
• Email notification — off by default. Enable it per-domain in your dashboard using the "Email me at 80% usage" toggle. You will receive one email per month, per domain, when the threshold is crossed.

The 80% warning does not affect file serving — your files continue to be delivered normally.

At 100% — what happens

Once the monthly limit is reached, your hosted files stop being served. Any request to a hosted file returns HTTP 429 with a plain upgrade page until the counter resets on the 1st of the following month.

AI crawlers receiving a 429 will typically back off and retry the following month. They do not penalise your site — they simply cannot read the file until quota is restored.

To restore service immediately, upgrade your plan. The new limit takes effect within seconds of the subscription update — no redeployment required.

Usage in the agentic era

AI agents increasingly fetch llms.txt before every LLM call to build context. A single automated workflow running 100 times per day generates 3,000 requests/month on its own — before any crawler traffic. If your domain is referenced in multiple agent pipelines or RAG systems, usage can compound quickly.

Rule of thumb: if your site is actively used as a data source for AI workflows, or if you are an agency hosting files for clients with high-traffic domains, Standard or Agency tier is strongly recommended.

Setting up Hosted Files

1. Subscribe via indexora.app/start or indexora.app/inject
2. After checkout, go to indexora.app/deploy
3. Choose Cloudflare auto-deploy, CNAME, or bash script
4. Follow the steps for your chosen method