Setting the file. One moment.
Subchapter 9.7
references/DOC_DISCOVERY.mdMarkdown3 KBView on GitHub
You’re here because a pinned page or recipe didn’t cover what you need — a field, an endpoint, an error, or an unpinned method. Doc discovery is the fallback for both tracks, never the first move:
inline-recipes/setup-*.md, mapped in
SEED.md § “What to seed per capability”. Each built capability is a self-contained local recipe that inlines the calls
and supersedes the REST doc pages — seed from it alone. Only a capability with no inline
recipe (e.g. coupons) discovers from the live docs (below).astro.md / non-astro.md + inline-recipes/*.The wix-docs skill is the full playbook (../wix-docs/SKILL.md when co-installed). The short
version:
1. Find a page — semantic curl search (no MCP required):
curl -sS -X POST 'https://www.wixapis.com/mcp-docs-search/v1/docs/search/markdown' \
-H 'Content-Type: application/json' \
--data-raw '{"search_term":"<what you need, in natural language>","document_type":"WIX_HEADLESS","maximum_results":3}'document_type: SDK / WIX_HEADLESS for code-writing, REST / BUSINESS_SOLUTIONS for seeding,
and SKILLS for a multi-step workflow no pinned recipe covers — it searches the dedicated recipe
corpus (step ordering, cross-step gotchas), which a REST search does not return (also VELO ·
WDS · BUILD_APPS · CLI · OVERVIEW). Drop /markdown for JSON hits. Found a recipe → resolve
its individual calls against SDK/REST docs; no recipe → assemble the flow from verified
per-method contracts.
2. Read a page — append .md to its docs URL. For an SDK shape, append .md?apiView=SDK —
the SDK view shows _id (what the frontend calls), the bare view shows id.
3. Exact structured schema / enums (no MCP) — POST https://mcp.wix.com/api/code-mode/search
with getResourceSchemaByUrl(docsUrl) (see wix-docs‘s API_SPEC_SEARCH.md).
If the host has the Wix MCP, its SearchWix* / SearchWixAPISpec → getResourceSchemaByUrl
tools are the same backends without the curl boilerplate — prefer them when present, per wix-docs
Lane 2. getResourceSchemaByUrl scopes to the URL: a method URL → that method’s contract; a
resource URL → the whole resource (fetch that for sibling operations).
A page that IS pinned → read it directly; don’t re-search for it.