Developer & Agent Resources
Developer & agent resources for momoChef
Machine-readable surfaces, content negotiation, and structured data for developers and AI agents working with momoChef. Everything below is served from the same URLs browsers use — no separate API keys required.
Machine-readable files
Indexes and metadata that describe the whole site. llms.txt curates the product surface for LLM agents; the sitemap lists every public URL with hreflang alternates; robots.txt states the crawl policy.
Markdown content negotiation
Every public page serves a clean Markdown representation from the same URL. Request it with an Accept header that prefers text/markdown — for example: curl -H "Accept: text/markdown" https://momochef.com/about. HTML and Markdown responses both declare Vary: Accept so caches never cross-serve the two representations.
Support and legal articles serve their Markdown source, localized per URL locale with English fallback. Marketing pages serve hand-maintained Markdown mirroring the page copy.
curl -H "Accept: text/markdown" https://momochef.com/aboutStructured data & embeds
Shared recipe pages (/r/<token>) carry full schema.org Recipe JSON-LD. Recipe cards can be embedded with /embed/<token>. The site also publishes Organization and WebSite JSON-LD on every page.
Public API
There is no public REST API today. The product API is an internal tRPC surface used by the first-party iOS, Flutter, and web clients. If you need an integration (export, embeds, bulk import), tell us what you are building.