# API and MCP changelog

> What changed in the NeuroPage REST API and MCP server, by release date, with an RSS feed.

Changes to the REST API and the MCP server that are live, newest first. Subscribe: [RSS](https://docs.neuropage.io/changelog/rss.xml). For changes to NeuroPage itself, see the [product changelog](https://neuropage.io/changelog).

## Developer docs: Welcome, MCP, Credits and limits, changelog

19 November 2026 | REST, MCP, Credits

- The single API page is now a developer docs section: Welcome, Quickstart, Authentication, Sandbox and plans, MCP, Concepts, Webhooks and Errors, next to the API reference. Every page has a Markdown copy, at its `/md` URL or with `Accept: text/markdown`, and `/about/documentation/api.md` now answers `Accept: text/markdown` too. The pages are set up to be served from docs.neuropage.io; until that host is on they stay under /about/documentation/developers.
- The MCP page has a connect block per client and the tool tables for all 45 tools, with access, credit cost and `dry_run` for each; `generate_assets` is quoted with `dry_run: true` first.
- Credits and limits lists what every action costs, when credits are refunded and every request and size limit, with a worked example. Error `type` links still open their code, and `campaign_not_eligible` is documented as `409`.
- This changelog has an RSS feed, and llms.txt lists the OAuth sign-in first for MCP and has a How to automate block. The personality profile is called DISC throughout, and the docs say "Contact us for sandbox access".

See [Welcome](https://docs.neuropage.io) | [Connect your AI agent](https://docs.neuropage.io/mcp) | [Credits and limits](https://docs.neuropage.io/credits-and-limits).

## Event subscriptions over MCP, quotes for generate_assets

18 November 2026 | MCP, Webhooks, Credits

- `subscribe_events` registers an https URL for `page.ready` and `job.failed`; `list_event_subscriptions` and `unsubscribe_events` manage them. Each delivery is signed with an `X-NeuroPage-Signature` HMAC-SHA256 header, and the signing secret is shown once.
- `generate_assets` with `dry_run: true` now returns a quote and starts nothing.
- A tool called with an argument it does not have is refused with `422` instead of ignoring the argument.
- `generate_messages` refuses while pages are still being built for the same leads. Settings, API & MCP also has a copy-prompt that starts an AI agent on NeuroPage.

See [Webhooks](https://docs.neuropage.io/webhooks) | [Credits and limits](https://docs.neuropage.io/credits-and-limits).

## Run a whole campaign from a chat

16 November 2026 | MCP, Credits

- The MCP server grew from 14 to 42 tools. An agent can now read and update the company profile and tone of voice, edit templates, upload media and pin it to sections, and create and update campaigns.
- It can import leads, list them, add columns and run research, then generate pages and messages and check which template variables have a column.
- It can list Instantly campaigns, import one into NeuroPage, and send leads back to Instantly with their page URLs.
- The tools that spend credits take `dry_run` and count towards a key's monthly credit cap. The campaign tools are MCP only; there is no REST endpoint for them.

See [Connect your AI agent](https://docs.neuropage.io/mcp) | [Credits and limits](https://docs.neuropage.io/credits-and-limits).

## Reads without a plan, create_workspace, starter credits

9 November 2026 | MCP, REST, OAuth, Credits

- Reads work on any workspace, with or without a plan. Every write returns `403 plan_required` until the workspace has a paid plan or a trial with a card on file; `GET /workspace` shows the state in `plan`.
- `create_workspace` makes a workspace from an MCP client signed in with OAuth, at most 3 a day. It is read-only until you start a plan in the app.
- Only the first workspace a user creates starts with 250 credits; later ones start at 0.

See [Sandbox and plans](https://docs.neuropage.io/sandbox-and-plans) | [Authentication](https://docs.neuropage.io/authentication).

## Create templates, error links, webhook events documented

9 November 2026 | REST, MCP, Webhooks

- `POST /templates` and `create_template` make a template from built-in sections and a call to action; `GET /templates/{id}` and `get_template` read one. A brand is the look and a template is the layout, so link one to the other with `brand_id`.
- The `type` URL in an error response opens the documentation for that code.
- The webhook events `lead.ready`, `page.viewed`, `cta.clicked`, `form.submitted` and `meeting.booked` are documented with their payloads, including how a job reaches `lead.ready`.
- Setup steps for ChatGPT, Codex and the OpenAI Responses API.

See [Concepts](https://docs.neuropage.io/concepts) | [Webhooks](https://docs.neuropage.io/webhooks) | [Errors](https://docs.neuropage.io/errors).

## Protocol fixes, exact quotes, checked brand values

3 November 2026 | REST, MCP, OAuth, Credits

- Browser-based clients can call the API and MCP server (CORS), `401` responses carry a `WWW-Authenticate` header, unknown paths return a JSON `404`, and OAuth tokens are checked for the right audience. The error codes are documented.
- A page is charged exactly its quote, refunds come back in the same response, and an invalid LinkedIn URL is refused before anything is charged.
- Brand values set over MCP (logo, colours) are validated before they are saved; an unusable value is refused with a reason.

See [Errors](https://docs.neuropage.io/errors) | [Credits and limits](https://docs.neuropage.io/credits-and-limits).

## Sign in with OAuth, list_workspaces, spend caps

28 October 2026 | OAuth, MCP, REST, Credits

- The MCP server accepts a NeuroPage sign-in (OAuth) as well as an API key, so claude.ai connectors work without a key. A signed-in agent acts as you in every workspace you belong to.
- `list_workspaces` lists them, and every other tool takes an optional `workspace` slug.
- An API key can have a monthly credit cap; a job that would pass it is refused with `402 spend_cap_reached`.
- `POST /jobs` answers `202` straight away, every response carries `RateLimit` headers, and reusing an `Idempotency-Key` with a different body is `409 idempotency_conflict`.

See [Authentication](https://docs.neuropage.io/authentication) | [Connect your AI agent](https://docs.neuropage.io/mcp).

## REST API and MCP server

28 October 2026 | REST, MCP

- Create API keys under Settings, API & MCP; one key belongs to one workspace.
- Over REST, `POST /jobs` makes a landing page for each LinkedIn profile, `GET /jobs/{id}` follows the job, and assets, brands, templates and stats can be read. A job can take a `brand_id` and a `template_id`.
- The MCP server at `/api/mcp` launched with 10 tools and the same key. Pick your AI tool in the app to get its setup steps.
- OpenAPI 3.1 and the API reference are public.

See [Quickstart](https://docs.neuropage.io/quickstart) | [Connect your AI agent](https://docs.neuropage.io/mcp).
