Documentation
Mark AI
Last updated
Mark is the operator assistant inside the Marktspan app. Unlike the MCP server, which brings read-only data into Claude or ChatGPT, Mark works where your team already operates: it runs skills, drafts changes, and asks for confirmation before anything touches live marketplace data.
Marktspan's pattern for sensitive paths is propose → review → apply, aligned with Ad Pilot approvals and role-based visibility. Public documentation intentionally avoids internal prompt trees, scoring code, or database layout; signed-in operators get procedural detail via Get Help → Documentation.
When to use Mark
Write skills in Mark — repricing suggestions, campaign tweaks, listing improvements — should wait until costs and connection health are stable. AI credits and plan entitlements matter for heavy Mark usage; see Pricing and Plans and getting help.
Security and procurement teams often ask whether customer data trains public models. Use the FAQ in sales cycles; escalate bespoke DPAs through Contact.
If your organization is not ready for AI governance, you can run Marktspan successfully without Mark. The core value remains margin, Pulse, and Manage modules. Add Mark when you have an owner who will audit proposals weekly — the same discipline as Ad Pilot.
Where to go next in the docs
Stay on this public guide for outcomes and rollout planning. For click-by-click operator procedures, sign in and open Get Help → Documentation.
Honest marketplace scope
Live seller operations emphasize Bol.com, Kaufland, and Pigu (PHH Group) today. Mirakl remains connect-first until your rollout confirms ingest for your operator. Ad Pilot applies to Bol Sponsored Products only; Pigu advertising uses Martailer separately from Ad Pilot. Retailers shown as coming soon on marketing surfaces are not described here as shipped product.