Builder Platform FAQ
What does it cost?
Nothing extra. Builder Platform access is included with your MixShift subscription.
What data can I reach?
Your whole MixShift warehouse over SQL (advertising, DSP, Seller and Vendor Central revenue and orders, inventory, catalog), the pre-shaped /v1 endpoints (accounts, advertising performance, pacing, search terms, ASIN performance, retail sales and traffic, Search Query Performance, brand context and change log), and live operations against Amazon for the accounts you are authorized on.
Can my app read the brand context and change log?
Yes, and this is the part most people do not realize is there. Your brand context documents and the brand change log (including stakes: the launches, promotions, stockouts, and price tests that explain a move) are on /v1 and MCP with the same credential. Reads are included in the default read scopes; appending to the change log is an opt-in write scope, and so is retiring or restoring a brand. See Work with brand memory.
Can I get MixShift Intelligence through the API?
Yes. MixShift Intelligence, the Operational Bridge, the Advertising Bridge, the Combined Read, Lost Sales, and the Monthly Read, is open to every account and reachable through the REST endpoints and the MCP tools under the intelligence:read scope. It is not part of the documented /v1 partner contract: its result shape is versioned by the engine itself. See mcp.mixshift.io/developers#intelligence for the endpoint and tool reference, and the MixShift Intelligence knowledge base for the plain-language walkthrough.
Can I enter forecast corrections through the API?
Yes. With the corrections:write scope you can enter your own forecast corrections, such as a month's sales, ad spend or budget. They are saved under your name in the same place the forecasting app reads, so a correction made in one place shows up in the other. Interactive sign-ins have the scope by default, and a tenant admin can grant it to a service credential. See mcp.mixshift.io/developers#forecast-corrections for the endpoints.
Can my app write to my ad accounts?
Yes, if the credential was minted with the write permission. Writes default to a dry run that previews the exact change, and commits are capped and audit-logged with a pre-write snapshot. Listing content writes use a stricter two-call preview and commit contract. Read-only credentials cannot write at all.
Do I need to register with Amazon as a developer?
No. That is most of the point. Your accounts are already authorized through MixShift, so you skip the developer applications, and the token plumbing is handled server-side.
I already query the warehouse over MySQL. Why switch?
The HTTPS endpoint runs the same SQL without database passwords, driver quirks, or IP allowlists, and it works from anywhere (serverless included). Direct MySQL access is the legacy path; new builds should start on /api/query.
Do I have to use the MCP?
No. MCP is one of three doors. If you are writing code, the REST endpoints are probably what you want; MCP exists so AI tools can connect without you writing anything.
Which AI tools can connect over MCP?
Claude, ChatGPT, Cursor, Codex, and any MCP-compatible client, all against the same server with one credential. See Connect AI tools over MCP.
Can a multi-user application sit on one credential?
Yes for internal tools, where the credential represents your organization. Partner software with per-customer sign-in should use the registered-app path instead, so each customer consents and gets their own tokens. See Get access.
How do I get access?
Get in touch and we will set you up, or your MixShift admin can mint a service credential directly. Details in Get access.
Related
Shifty is the MixShift docs assistant. Pick a question or open the chat for anything else.