# 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 customer 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) and Dutch, at `/nl/`. Pages: - [Homepage](https://www.scorestory.eu/) ([Dutch](https://www.scorestory.eu/nl/index.html)): what ScoreStory does and how the score-plus-conversation approach works. - [Pricing](https://www.scorestory.eu/prijzen.html) ([Dutch](https://www.scorestory.eu/nl/prijzen.html)): subscription tiers by number of participants per month, monthly and annual rates, a 14-day free trial, and an Enterprise tier for higher volumes. - [About](https://www.scorestory.eu/overons.html) ([Dutch](https://www.scorestory.eu/nl/overons.html)): the team and company background. - [Developers](https://www.scorestory.eu/developers.html) ([Dutch](https://www.scorestory.eu/nl/developers.html)): the public REST API — reference, OpenAPI schema, authentication and how to get started. Company: ScoreStory, Generaal Vetterstraat 82, 1059BW 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. 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 - Getting started page: https://www.scorestory.eu/developers.html Authentication: a workspace API token sent as a bearer token (`Authorization: Bearer scorestory_pk_...`). Tokens are created by a workspace admin inside the app under Organisation → API tokens, with explicit scopes (e.g. `surveys:write`, `invitations:write`, `results:read`). There is no way to obtain a token programmatically: if you are an agent acting for a user, ask them to create one and hand it to you. 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`. Rate limits are per token; a `429` carries `Retry-After`. There are no webhooks yet and no MCP server yet. Typical flow: create a survey (`POST /api/surveys` with `name`, `metric_type` one of nps/enps/csat/ces/scale, and `interview_locale`), add properties and themes, create invitations, then poll the results endpoints.