Cite Files

Check whether AI assistants can reach, read and cite a public website. Returns a citation-readiness score out of 100, the category breakdown, and the specific problems found — crawler blocks, missing llms.txt/ai.txt/sitemap, thin or JavaScript-only content, missing structured data. Use this before changing a site for AI visibility, and again afterwards to check the change worked. Scans of the same site within six hours are reused.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The public website address, e.g. example.com or https://example.com"
    }
  },
  "required": [
    "url"
  ]
}

Get a task list for making a website readable and citable by AI assistants, derived from a real scan of it. Returns the findings with the evidence behind each, and the rules to follow while fixing them — most importantly that you must not invent facts about the business, and must leave a visible TODO instead. Use this to plan the work after citefiles_scan.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The public website address."
    },
    "style": {
      "type": "string",
      "enum": [
        "claude",
        "codex"
      ],
      "description": "Prose instruction (claude) or a task list with acceptance criteria (codex). Defaults to claude."
    }
  },
  "required": [
    "url"
  ]
}

Check which AI-facing discovery files a website actually serves: llms.txt, llms-full.txt, ai.txt, robots.txt, sitemap.xml, AGENTS.md, .well-known/mcp.json and others. Distinguishes a real file from a single-page app returning its HTML shell for every unknown path, which is the usual reason a file appears to exist but does not. Use this to verify a file you just published is being served correctly.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The public website address."
    }
  },
  "required": [
    "url"
  ]
}

Test how a website answers requests that carry the user-agent strings of four AI crawlers — GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot — by requesting its homepage as a browser and again as each, then comparing. The requests come from our server, not the vendors' networks, so a rule that checks the sender's address is not tested. Catches CDN and WAF rules that block assistants without the owner knowing. Use when a site looks correct but is not being cited.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The public website address."
    }
  },
  "required": [
    "url"
  ]
}

Requires an API token (Authorization: Bearer cf_…). Read the stored Agent Commerce Readiness audit for a scan on your citefiles account: whether an AI agent can authenticate without a human's password, discover an API, read prices as text, and be offered a machine-payable challenge — as a tier from T0 to T5. Create a token at https://citefiles.com/account. Only returns audits for scans your account owns. This tool never runs a new audit — run it from the scan's report page first, then call this tool to read the result.

{
  "type": "object",
  "properties": {
    "scan": {
      "type": "string",
      "description": "The scan's public id, from a citefiles.com/report/<id> URL."
    }
  },
  "required": [
    "scan"
  ]
}