Everything Phoenix knows about your quizzes, shoppers and results is yours to use from your own code or from the AI assistant you already work in.
Quizzes, versions, publishing, analytics, shopper profiles, exports, experiments and webhooks, all behind scoped API keys you manage in the developer dashboard.
REST API, webhooks and JS API are on Plus and Enterprise.
Ten events cover the quiz, the shopper, publishing, experiments and exports. Every delivery carries an HMAC signature, and failed deliveries are retried.
Webhooks guidewindow.octaneai fires 17 events in the browser and gives you methods to read state, move the shopper, prefill answers, set who they are, and open or close the quiz.
window.octaneai.on('quiz.finished', (e) => {
console.log(e.result.title, e.profile.email);
});
window.octaneai.prefill({ skin_type: 'dry' });
window.octaneai.open();Octane AI has an MCP server. Add it to Claude, ChatGPT, Cursor or Codex, sign in and pick which store it can reach and what it can do: quizzes, analytics, experiments, profiles. No API keys.
18 tools cover stores, quizzes, publishing, analytics questions, people and profiles, exports, experiments, and starting, checking or stopping an AI quiz build.
Octane AI has an MCP server. Add it to Claude, ChatGPT, Cursor or Codex, sign in and pick which store it can reach and what it can do. No API keys. Then ask in plain language.
Worked examples for the REST API, webhooks, the JS API and the MCP server, so the first version of your integration is a copy and paste away.
You don't need a perfect plan to begin. Start small, and let Phoenix help you improve from there.