This article describes common use cases and flows for the Dynamic Site Context API.
To provide an AI agent with a comprehensive understanding of a user's Wix ecosystem:
To inject site context directly into an LLM prompt without post-processing:
include_account_context and include_partner_context set to true.markdown field with a ready-to-use report ("# My Wix Sites Context" with per-site sections).WixREADME and GetSiteContext tools.When calling as an installed app (OAuth client_credentials token) rather than a user:
POST /oauth2/token with grant_type: client_credentials, your app's client_id/client_secret, and the instance_id of the installation.To retrieve context for a single known site:
site_id set to the target site's GUID.To find a site when you only know its name:
site_name set to the exact display name.To fetch all sites for a user with many sites:
query.paging.limit set to your preferred page size (e.g., 50).paging_metadata.has_next field in the response.has_next is true, call GetDynamicContext again with query.paging.cursor set to the paging_metadata.cursors.next value from the previous response.has_next is false.To determine whether a site has Velo (Wix Code) enabled:
site_id.velo_enabled field on the returned site.velo_enabled is true, the site supports custom Velo code. If absent, the status could not be determined.To check which Wix Stores catalog version a site uses:
site_id.installed_apps for an entry with the Wix Stores app ID.catalog_version field on that entry will be "V1" or "V3".Last updated: 27 July 2026