For developers and agents.
The public catalogue is open to crawlers, language models and browser agents. These are the supported ways in; everything else is the website itself.
- llms.txt
- Agent-oriented overview of Watch Anchor with when-to-use guidance: what the product does, which jobs it is right for, and how agents should call it.watchanchor.com/llms.txt
- Sitemaps
- Main sitemap at /sitemap.xml plus a dedicated sitemap for individual watch pages at /watch/sitemap.xml.watchanchor.com/sitemap.xml
- robots.txt
- Crawling policy. AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended and friends) are welcome on public pages.watchanchor.com/robots.txt
- Markdown content negotiation
- Public pages honour the Accept: text/markdown request header and respond with Content-Type: text/markdown and Vary: Accept, following the acceptmarkdown.com convention. Appending .md to a page URL (/about.md, /watch/<slug>.md, /brand/<slug>.md, or /index.md for the homepage) returns the markdown variant directly. Each page names its markdown version in a link tag, each markdown response names its page in a canonical Link header, and nonexistent paths return a markdown 404 with recovery links.Any public page
- Public catalogue
- Search thousands of watches by brand, model or reference at /browse, filter at /explore, read individual specification pages under /watch/<slug> and sourced facts about each watchmaker under /brand/<slug>. No account is required.watchanchor.com/browse
- WebMCP tools
- Every page registers in-browser WebMCP tools for agents that drive a browser session. Catalogue search, explore filters, movement search and watch details are there for any visitor. Collection, wishlist, archive, warranty and notes tools are added once the user is signed in.Every page
There is currently no public REST API or API-key programme.
Building an integration with Watch Anchor? Email hello@watchanchor.com or see the contact page.