# WOW! Momo

> WOW! Momo Foods Private Limited is a Kolkata, India quick-service restaurant company founded in
> August 2008, operating the WOW! Momo, WOW! China and WOW! Chicken brands across roughly 650 outlets in
> more than 30 Indian cities. It runs no developer programme and publishes no API documentation, portal,
> SDK or pricing. This file is generated by API Evangelist from an independent third-party profile of
> WOW! Momo's publicly reachable machine surfaces — it is not published by WOW! Momo.

Generated: 2026-09-04. Method: generated (WOW! Momo serves no /llms.txt; https://www.wowmomo.com/llms.txt
returned HTTP 404 on 2026-09-04).

## What is actually callable

- [WOW! Momo Content API](https://www.wowmomo.com/wp-json/): the live WordPress REST API behind
  www.wowmomo.com. Anonymous, no key, no registration. 20 operations answer without a credential: the
  site's 6 pages, 98 media items, 5 categories, 15 tags, 1 author, the post-type/taxonomy/status
  registries, a cross-type search index of 7 objects, an oEmbed 1.0 provider endpoint and the Yoast SEO
  head document. Its route index declares 396 routes across 36 namespaces; everything not listed above is
  administrative and returns 401 or 403.
- [WOW! Momo App Backend](https://api.wowmomo.com/): the backend of the Wow Eats consumer ordering app.
  NOT callable. Every path probed anonymously on 2026-09-04, including a control path that cannot exist,
  returned HTTP 200 with the identical body {"data":null,"message":"NO_AUTH","messageType":"FAILED"}.
  Only GET /health answers, with "OK". Note the gate returns 200, not 401 — status-code-based error
  handling will read a rejected call as a success with a null payload.

## Machine-readable descriptions of that surface

- [OpenAPI 3.1 for the Content API](openapi/_ae-authored/wow-momo-content-api-openapi.yml): derived by
  API Evangelist from the server's own route index and per-route HTTP OPTIONS schema documents. WOW! Momo
  publishes no OpenAPI.
- [Route index, verbatim](openapi/wow-momo-content-api-discovery-original.json): the provider-served
  document the contract above was read from.
- [Overlay](overlays/wow-momo-content-api-overlay.yaml)
- [Authentication](authentication/wow-momo-authentication.yml)
- [Conventions](conventions/wow-momo-conventions.yml): pagination, filtering, error envelope,
  idempotency (none), reversibility (n/a — read-only).
- [Error catalog](errors/wow-momo-problem-types.yml)
- [Data model](data-model/wow-momo-data-model.yml)
- [Lifecycle](lifecycle/wow-momo-lifecycle.yml)
- [Conformance](conformance/wow-momo-conformance.yml)
- [Rate limits](rate-limits/wow-momo-rate-limits.yml)
- [Plans and pricing](plans/wow-momo-plans-pricing.yml)
- [Packages](packages/wow-momo-packages.yml)
- [Domain security](security/wow-momo-domain-security.yml)
- [.well-known probe](well-known/wow-momo-well-known.yml)
- [MCP candidate](mcp/wow-momo-mcp.yml): a design sketch. No MCP server exists.

## Agent skills

- [Read the WOW! Momo site through its API](skills/wow-momo-read-the-site.md)
- [Pull WOW! Momo brand and campaign imagery](skills/wow-momo-pull-brand-assets.md)
- [Embed a WOW! Momo page and read its SEO graph](skills/wow-momo-embed-and-describe.md)

## Things an agent will look for and NOT find

- No menu, outlet, nutrition, pricing or ordering data is exposed on any WOW! Momo host. The store
  locator at https://restaurants.wowmomo.com/ is a vendor-operated microsite, not a WOW! Momo API, and
  the ordering domain sits behind the NO_AUTH gate.
- No developer portal, API reference, getting-started guide, changelog, status page, SLA, deprecation
  policy or developer support channel.
- No SDK on npm, PyPI or any other registry, and no WOW! Momo GitHub organisation.
- No /.well-known documents, no security.txt, no apis.json, no agent card, no MCP server, no AsyncAPI and
  no webhooks. Each was probed on 2026-09-04 and each returned 404 (or, on the app host, the same blanket
  gate as a path that does not exist).

## Operating notes

- Send a full browser User-Agent. www.wowmomo.com runs mod_security and answered a request sent with the
  User-Agent "Mozilla/5.0" with HTTP 406.
- Errors use the WordPress envelope {code, message, data.status}, not RFC 9457 problem+json. Branch on
  `code`.
- No rate limit is documented or signalled on the wire. Be conservative.

## Company links

- [Website](https://www.wowmomo.com/)
- [Terms & Conditions](https://www.wowmomo.com/terms-conditions/)
- [Privacy](https://www.wowmomo.com/privacy/)
- [Franchise enquiry](https://www.wowmomo.com/franchise-form/)
- [Outlet locator](https://restaurants.wowmomo.com/)