llms.txt, agent.md and agent.json explained simply
llms.txt, agent.md and agent.json are different entry points for AI systems. Together they help understand a business more clearly and contact it more cleanly.
Why several files make sense
AI systems don't always read the same formats. Some benefit from compact Markdown, others from clearly structured JSON, others start from a general orientation file.
anewera combines these formats so a company profile becomes understandable from several angles: editorial, structured and action-oriented.
The role of llms.txt
llms.txt is a well-readable orientation for AI systems. It explains what the website is about, which resources matter and which rules apply when using the information.
For anewera, llms.txt points to the directory, knowledge base, Agent API, MCP, OpenAPI, the webMCP manifest and public company profiles.
The role of agent.md and agent.json
agent.md is deliberately human- and LLM-readable. It summarizes profile, services, sources and contact rules in Markdown.
agent.json is more machine-oriented. It contains structured profile fields, available functions, contact rules and technical endpoints. Agents can parse this data more reliably than free-form text.
Checklist
- llms.txt points to the most important public resources
- agent.md explains the business in clear language
- agent.json contains services, sources, regions and functions
- Private emails and internal notes stay excluded
- All files are reachable at stable URLs
Frequently asked
Do these files replace classic SEO?Answer
No. They complement classic SEO. Good titles, content, internal links, structured data and technical indexability still matter.
Are agent.md and agent.json public?Answer
Yes, at anewera they are meant as public profile resources. Private routing data, internal notes and recipient addresses are not published in them.