Begin with the state the site should reach
A Wix integration may cross a site, app, member, content, or commerce context. An agent should start with one user or operator action and state which record changes, which identifier connects the steps, and what the application should show afterward. This keeps the plan focused on behavior rather than a list of endpoints.
Name the Wix API surface, site or app context, environment, authentication model, and records in scope. Ask for cited request fields, permissions, response values, event behavior, errors, and limits. Secrets and real customer data stay out of examples.
Validate the request sequence with Postman
Wix supplies the API contract and resulting site state. Postman supplies environments, chained requests, captured identifiers, fixtures, and assertions. A combined agent can exercise the documented plan against an approved test context before application code changes.
Any request that creates, publishes, charges, messages, or changes production data requires explicit review and cleanup instructions.
