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. For changes to NeuroPage itself, see the product 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
/mdURL or withAccept: text/markdown, and/about/documentation/api.mdnow answersAccept: text/markdowntoo. 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_runfor each;generate_assetsis quoted withdry_run: truefirst. - Credits and limits lists what every action costs, when credits are refunded and every request and size limit, with a worked example. Error
typelinks still open their code, andcampaign_not_eligibleis documented as409. - 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 | Connect your AI agent | Credits and limits.
Event subscriptions over MCP, quotes for generate_assets
18 November 2026 | MCP, Webhooks, Credits
subscribe_eventsregisters an https URL forpage.readyandjob.failed;list_event_subscriptionsandunsubscribe_eventsmanage them. Each delivery is signed with anX-NeuroPage-SignatureHMAC-SHA256 header, and the signing secret is shown once.generate_assetswithdry_run: truenow returns a quote and starts nothing.- A tool called with an argument it does not have is refused with
422instead of ignoring the argument. generate_messagesrefuses 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 | 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_runand 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 | 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_requireduntil the workspace has a paid plan or a trial with a card on file;GET /workspaceshows the state inplan. create_workspacemakes 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 | Authentication.
Create templates, error links, webhook events documented
9 November 2026 | REST, MCP, Webhooks
POST /templatesandcreate_templatemake a template from built-in sections and a call to action;GET /templates/{id}andget_templateread one. A brand is the look and a template is the layout, so link one to the other withbrand_id.- The
typeURL in an error response opens the documentation for that code. - The webhook events
lead.ready,page.viewed,cta.clicked,form.submittedandmeeting.bookedare documented with their payloads, including how a job reacheslead.ready. - Setup steps for ChatGPT, Codex and the OpenAI Responses API.
See Concepts | Webhooks | 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),
401responses carry aWWW-Authenticateheader, unknown paths return a JSON404, 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 | 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_workspaceslists them, and every other tool takes an optionalworkspaceslug.- An API key can have a monthly credit cap; a job that would pass it is refused with
402 spend_cap_reached. POST /jobsanswers202straight away, every response carriesRateLimitheaders, and reusing anIdempotency-Keywith a different body is409 idempotency_conflict.
See Authentication | Connect your AI agent.
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 /jobsmakes 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 abrand_idand atemplate_id. - The MCP server at
/api/mcplaunched 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 | Connect your AI agent.