# ScoreStory > ScoreStory combines KPI scores (NPS, CSAT, Customer Effort Score) with an > AI-led conversation, so customer feedback comes with the "why" behind the > score, not just the number. ScoreStory is a self-service satisfaction research tool built by the founders of MWM2, a market research agency, together with AI specialist Steven Heijtel. When a customer submits a score, ScoreStory starts a natural-language conversation to find out what went well, what could be better, and what shaped that rating. The site is available in English (default), Dutch (`/nl/`), German (`/de/`), French (`/fr/`) and Spanish (`/es/`). Pages: - [Homepage](https://www.scorestory.eu/) ([Dutch](https://www.scorestory.eu/nl/), [German](https://www.scorestory.eu/de/), [French](https://www.scorestory.eu/fr/), [Spanish](https://www.scorestory.eu/es/)): what ScoreStory does and how the score-plus-conversation approach works. - [Product](https://www.scorestory.eu/product) ([Dutch](https://www.scorestory.eu/nl/product), [German](https://www.scorestory.eu/de/produkt), [French](https://www.scorestory.eu/fr/produit), [Spanish](https://www.scorestory.eu/es/producto)): everything the product does, step by step — the AI survey builder, six ways to invite participants, the AI interviewer (typed or spoken answers, eight interview languages), automatic theme and sentiment analysis, the written conclusion and results assistant, notifications, sharing, export, the API, and privacy features such as anonymous surveys. - [Why ScoreStory](https://www.scorestory.eu/why-scorestory) ([Dutch](https://www.scorestory.eu/nl/waarom-scorestory), [German](https://www.scorestory.eu/de/warum-scorestory), [French](https://www.scorestory.eu/fr/pourquoi-scorestory), [Spanish](https://www.scorestory.eu/es/por-que-scorestory)): an introduction video of under two minutes (in every language of the site) and why a conversation surfaces more than a questionnaire does. - [Pricing](https://www.scorestory.eu/pricing) ([Dutch](https://www.scorestory.eu/nl/prijzen), [German](https://www.scorestory.eu/de/preise), [French](https://www.scorestory.eu/fr/tarifs), [Spanish](https://www.scorestory.eu/es/precios)): subscription tiers by number of participants per month, monthly and annual rates, a free tier with up to 10 participants, and an Enterprise tier for higher volumes. - [Blog](https://www.scorestory.eu/blog) ([Dutch](https://www.scorestory.eu/nl/blog), [German](https://www.scorestory.eu/de/blog), [French](https://www.scorestory.eu/fr/blog), [Spanish](https://www.scorestory.eu/es/blog)): articles on satisfaction research — which questions to ask, and what to do with the results. So far: - [The biggest blind spot in customer research? Your own questions](https://www.scorestory.eu/blog/the-biggest-blind-spot-in-customer-research): the richest insights sometimes lie in what nobody asked. - [You want my opinion? Then act like it](https://www.scorestory.eu/blog/you-want-my-opinion-then-act-like-it): why long questionnaires put customers off, and what to offer instead. - [Web analytics is not enough. Start a conversation with your visitors](https://www.scorestory.eu/blog/talk-to-your-website-visitors): analytics show what visitors do; a conversation tells you why. Each article is also available in the other four languages, linked from the article itself. - [About](https://www.scorestory.eu/about) ([Dutch](https://www.scorestory.eu/nl/overons), [German](https://www.scorestory.eu/de/ueber-uns), [French](https://www.scorestory.eu/fr/a-propos), [Spanish](https://www.scorestory.eu/es/sobre-nosotros)): the team and company background. - [Developers](https://www.scorestory.eu/developers) ([Dutch](https://www.scorestory.eu/nl/developers), [German](https://www.scorestory.eu/de/developers), [French](https://www.scorestory.eu/fr/developers), [Spanish](https://www.scorestory.eu/es/developers)): the public REST API — reference, OpenAPI schema, authentication and how to get started. - [Help centre](https://www.scorestory.eu/help) ([Dutch](https://www.scorestory.eu/nl/handleiding), [German](https://www.scorestory.eu/de/hilfe), [French](https://www.scorestory.eu/fr/aide), [Spanish](https://www.scorestory.eu/es/ayuda)): the complete user manual, one page per chapter: getting started, creating and configuring a survey, the six ways to invite participants, the interview as participants see it, managing participants (including GDPR requests), reading results, organisation settings, subscriptions, a glossary and how to get help. The same manual the in-app assistant answers from, published after every release. - [Video course](https://www.scorestory.eu/course) ([Dutch](https://www.scorestory.eu/nl/cursus), [German](https://www.scorestory.eu/de/kurs), [French](https://www.scorestory.eu/fr/cours), [Spanish](https://www.scorestory.eu/es/curso)): five short videos, about a quarter of an hour in all: setting up and testing a survey, reading and sharing results, importing participants, email invitations and templates, and links, popups and the API. Each language has its own recording. - [Guides](https://www.scorestory.eu/guides) ([Dutch](https://www.scorestory.eu/nl/gidsen), [German](https://www.scorestory.eu/de/ratgeber), [French](https://www.scorestory.eu/fr/guides), [Spanish](https://www.scorestory.eu/es/guias)): what eNPS, NPS, CSAT and the Customer Effort Score measure and how to calculate them, with free calculators (eNPS, NPS, CSAT), example question sets (employee survey, customer satisfaction survey, exit interview), and guides on anonymous employee surveys under the GDPR, response rates and conversational surveys. - [Comparisons](https://www.scorestory.eu/compare) ([Dutch](https://www.scorestory.eu/nl/vergelijken), [German](https://www.scorestory.eu/de/vergleich), [French](https://www.scorestory.eu/fr/comparatifs), [Spanish](https://www.scorestory.eu/es/comparativas)): how ScoreStory compares with SurveyMonkey, Typeform, Google Forms, Microsoft Forms, Qualtrics, Effectory, Culture Amp and Mopinion (Netigate Digital), and a conversational survey with a traditional one. Facts about other products come from their own public pages, with sources and the date they were checked. Company: ScoreStory B.V., Generaal Vetterstraat 82, 1059 BW Amsterdam, the Netherlands. KVK 42132130. Contact: welcome@scorestory.eu. The product itself runs at https://app.scorestory.eu (sign-up and the application are not part of this marketing site). ## For AI agents and integrations ScoreStory has a public REST API and an MCP server. Everything the interface can do with surveys, invitations, respondents, results and mailings, an agent can do too — without a person at the keyboard. - Reference (human-readable): https://app.scorestory.eu/api/public-api/v1/docs - OpenAPI 3 schema (machine-readable): https://app.scorestory.eu/api/public-api/v1/openapi.json - Base URL: https://app.scorestory.eu/api - MCP server (Streamable HTTP): https://app.scorestory.eu/api/mcp - Getting started page: https://www.scorestory.eu/developers Authentication, two ways — both a bearer token in `Authorization`: - **API token**, for a backend or script: `Bearer scorestory_pk_...`. Created by a workspace admin inside the app under Organisation → API tokens. A token belongs to one workspace and carries explicit scopes. - **OAuth 2.1**, for an AI assistant or integration acting for a signed-in person; this is also how the MCP server is reached. Authorization code with PKCE (S256), dynamic client registration, rotating refresh tokens. The person picks a workspace and scopes on a consent screen and can disconnect the client under Organisation → API tokens → Connected apps. Access tokens look like `scorestory_at_...`. Metadata: https://app.scorestory.eu/api/.well-known/oauth-authorization-server Scopes: `surveys:read`, `surveys:write`, `invitations:read`, `invitations:write`, `respondents:read`, `respondents:write`, `results:read`, `mailings:read`, `mailings:write`. Call `GET /api/public-api/v1/me` first: it returns the workspace, the scopes and any survey restriction of the token, so you never have to guess. Errors are `{"error": {"code": "...", "message": "..."}}`; branch on `code`, never on `message`. Rate limits are per token; a `429` carries `Retry-After`. There are no webhooks yet: poll the results endpoints. Typical flow: create a survey (`POST /api/surveys` with `name`, `metric_type` one of nps/enps/csat/ces/scale, and `interview_locale` one of auto/en/nl/de/fr/es/it/pl/pt), add properties and theme categories (`/topic-categories`), create invitations (a shared link or personal ones), then poll the results endpoints.