Wix Docs — look up the Wix API/SDK documentation

Get the exact truth about a Wix API — endpoint, HTTP method, request/response body, a field, an enum, or an error. Never invent a Wix endpoint, path, body, or enum from memory — confirm it here first. That includes the example endpoints in this skill: they illustrate the mechanics and go stale like any snapshot — discover the real contract before you rely on one.

A lookup is a short flow: find the right page, then read it. Do it with curl (default, below) or the Wix MCP doc tools if your agent has them (Lane 2). Either way, route by what you already know:

• You have a docs URL → just read it (§2). Don't re-search for a page you can already name.
• A multi-step workflow ("take a booking from service setup to payment") → include the recipe corpus in the search: document_types: ["SKILLS", …] alongside the API corpus the steps live in (§1A). A recipe carries step ordering, cross-step gotchas, and the one bundled endpoint that does the whole job — things no single method page states. No relevant recipe comes back → assemble the workflow from the verified per-method contracts in the same result set.
• One specific operation, field, or enum → search its API corpus (REST / SDK), then read or schema-check what you land on.