Basalt Docs

llms.txt is a plain text file you place at the root of your domain (yoursaas.com/llms.txt). It gives AI language models a structured summary of what your product is, who it's for, how it's priced, and how to interact with it. It was proposed to solve a simple problem: LLMs crawl your website and often misunderstand your product because HTML is noisy. llms.txt gives them clean, structured signal. Basalt generates a custom llms.txt based on your actual website content — not a template.

llms-full.txt is the extended version of llms.txt. Where llms.txt is a concise summary, llms-full.txt includes: - Full product description - All pricing tiers with details - Integrations and supported platforms - FAQs - Common use cases - Known limitations - Agent-specific instructions Place it at yoursaas.com/llms-full.txt. AI agents that need deeper context will use this file.

agent.json is a structured JSON manifest for AI agents. It describes your product in machine-readable format, including: - Product name and description - Links to pricing, docs, support - What actions an agent can take (recommend, sign up, purchase) - Permissions (what requires human approval) Place it at yoursaas.com/agent.json. This file is used by agent frameworks to understand your product's capabilities and limitations. Example: { "schema_version": "0.1", "name": "YourSaaS", "llms_txt": "/llms.txt", "pricing_url": "/pricing", "permissions": { "agent_can_recommend": true, "agent_can_purchase": false, "human_approval_required_for_purchase": true } }

After downloading your Agent-Ready Pack, you'll have six files. Here's where each goes: 1. llms.txt → upload to yoursaas.com/llms.txt 2. llms-full.txt → upload to yoursaas.com/llms-full.txt 3. agent.json → upload to yoursaas.com/agent.json 4. agent-docs.md → can live at yoursaas.com/agent-docs or in your /docs folder 5. implementation-guide.md → reference guide, keep internally 6. AgentRank report → keep for your records For most platforms: - Vercel / Next.js: place files in your /public folder - Webflow: upload via Assets - WordPress: upload to root via FTP/SFTP - Framer: use Embed to serve static files Your implementation-guide.md has platform-specific instructions.

After uploading, verify each file is accessible: 1. Open your browser 2. Navigate to yoursaas.com/llms.txt 3. You should see plain text — your product summary 4. Repeat for /llms-full.txt and /agent.json Common issues: - 404 error: File is not in the right location - HTML returned instead of text: Server is routing the path to your app — add a static file exception - agent.json shows as download: Set Content-Type to application/json

Basalt never invents information about your product. Every file is generated from content found on your public website at the time of scan. If a feature, integration, pricing tier, or compliance claim is not clearly stated on your site, Basalt writes "Not clearly listed" — it does not guess or hallucinate. If you want something included that isn't currently on your site, add it to your website first and regenerate.