I help people make their websites and APIs work with AI agents. I run turva.dev, where I test what an agent can access and work out what needs changing when it gets stuck.
I also build the tools below. The code is open source so you can try it on your own site or see how mine works.
| Project | What it does | Try it |
|---|---|---|
| llms-txt-validator | Checks llms.txt structure from the command line or Node, with JSON output for CI. | Hosted validator |
| turva-worker | Runs my website, serving HTML and Markdown from shared content sources. It also publishes the site's discovery metadata. | Live site |
| turva-mcp | Gives MCP clients read-only access to turva.dev's published information and evidence. | Connect your client |
To try the validator, replace the domain with one you want to check:
npx turva-llms-txt-validator example.comI use turva.dev as a reference implementation. Its source code and verification instructions are public, along with dated measurements and their limits. You can inspect the implementation and repeat the checks.
I write about what I build and what happens when agents try to use websites.
- llms.txt explained.
- The /.well-known directory for agents.
- What an agent-readiness audit is.
- The twin is the page.
- Thirty days after the brief: 210 sites rescanned, four moved.
- What four AI assistants call an agent readiness audit.
- Website agent readiness, measured on 567 company sites.
I'm based in Tampere, Finland. I work in writing and explain the findings so the people maintaining a site can follow the reasoning and test the changes themselves.
Send me your website and tell me what you're trying to do. That's enough to start: info@turva.dev.