Framer Server API by Framer

# Fix list: Framer Server API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/framer, the October 2026 research run, assessed 1 October 2026. Grade D, 52.8 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Framer Server API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 43 out of 100, up to 11.4 more on the total

Why it scored 43: Better Stack status page at framerstatus.com with App, Editor, API, Hosting, Sites, Website and Community components (20). The history we could read showed one incident since July, elevated errors in the Editor's AI tools for 1 hour 15 minutes on 22 September 2026, so minor only, read from a page that may not show every month (20 of 30). No rate limits published for the Server API (0). No 429 or retry guidance. The FAQ says the API 'is not in any way transactional' and scripts must handle partial failures themselves (3 of 15). No SLA found (0). The Server API is in open beta (0 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Payments & pricing, 25 out of 100, up to 9.4 more on the total

Why it scored 25: No machine payment protocol (0). The Server API is free during beta and Framer says it'll 'likely charge for this API on a per-use basis, with a monthly free allowance', with no price set. Site plans are public (5 of 20). Free on every plan during the beta, including the Free site plan (20). A person creates the key in Site Settings or approves `@framer/agent` in a browser (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 3. Security & auth, 50 out of 100, up to 8.8 more on the total

Why it scored 50: One API key per project, created under Site Settings, that can't reach other projects. We didn't find rotation or revocation documented for Server API keys. `@framer/agent` grants access per project in the browser and Framer says it can be revoked at any time (20 of 30). No read-only key. The key can publish and deploy directly, while `@framer/agent` keeps changes on a branch until someone merges or publishes (12 of 20). CMS content and code files come back as they are, mostly the customer's own, with no injection guidance (5 of 15). We found no API call log for operators (5 of 15). A Trust Center at trust.framer.com, and framer.com's security.txt expired on 1 August 2026 per the 30 September check. Certifications and a disclosure policy weren't checked (8 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Agent ergonomics, 47 out of 100, up to 8.6 more on the total

Why it scored 47: There's no plain HTTP request an agent can send. A script opens a WebSocket session through the SDK and calls Plugin API methods, and results are whole node or collection objects (12 of 25). Node queries by type and CMS item access exist, but we found no documented page or field controls (10 of 20). No documented error codes, and a dropped connection can stop a run halfway (8 of 20). Calls aren't transactional, but `@framer/agent` puts every change on a branch and `publish` makes a preview before `deploy` promotes it (10 of 20). JavaScript and TypeScript only, Node 22 or later (7 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Schema & documentation, 69 out of 100, up to 5 more on the total

Why it scored 69: No OpenAPI or REST contract. The contract is the TypeScript types in the `framer-api` SDK over a WebSocket (12 of 25). llms.txt at framer.com per the 30 September check (10). The Plugin API reference documents each method, and `@framer/agent` installs skills that tell coding agents how to use it (12 of 20). Typed TypeScript inputs with union types for node and field kinds (12 of 15). Quick-start examples and a REST-wrapper example on GitHub. No error reference found (8 of 15). A dated changelog with semver and breaking changes flagged, v4.1.0 on 4 August, v5.0.0 on 8 September and v5.1.0 on 24 September 2026 (15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 6. Maintenance & community, 77 out of 100, up to 2 more on the total

Why it scored 77: Plugin API v5.1.0 on 24 September 2026, which the Server API exposes. `framer-api` on npm is at 5.0.0 (30). Three changelog releases since 3 July (20). Closed service with a public changelog and a community forum. We didn't test support (10 of 15). No MCP registry entry, which Framer says isn't needed. One official SDK, current (10 of 15). `framer-api` 5.0.0 declares Node 22 or later and two runtime dependencies (7 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 77 out of 100, up to 2 more on the total

Made of editorial 58, provenance 95.

Why it scored 77: Closed service under published terms. `framer-api` is MIT on npm (18 of 30). Privacy statement version 1.7 of 12 June 2026 names Framer B.V., gives retention periods (transaction data 7 years, account data up to 2 years after closure) and links a DPA. Its AI line only covers training 'third-party general-purpose AI models' on personal data (22 of 30). Breaking changes are flagged by major version, such as the v4.0.0 package rename and v5.0.0 CMS array fields, with no deprecation policy or notice period (8 of 20). Transfer countries are listed in the Trust Center per the privacy statement. We didn't confirm a subprocessor list (10 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- security.txt: published but past its Expires date (5 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- Rate limits and the eventual price of the Server API; neither is published.
- Whether Server API keys can be rotated or revoked without regenerating the project's settings.
- Framer's certifications and disclosure policy; the Trust Center wasn't read.
- Whether the status page history shows every incident from July and August; the page we read listed only one.

## Weaknesses

- No REST endpoints and no official MCP server. You need Node 22 and the `framer-api` package
- Open beta with no published rate limits, price or SLA
- Not transactional, so failures can leave partial edits
- API keys can publish and deploy directly, with no read-only option
- framer.com's security.txt expired on 1 August 2026

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- `connect(projectUrl, process.env.FRAMER_API_KEY)` then call Plugin API methods, and close the connection when done
- Publish creates a preview deployment. Promote it with `deploy()` only after checking it
- Keep batches small and idempotent, since a dropped connection can stop a run halfway
- For interactive work from a coding agent, `npx @framer/agent setup` is the supported route and keeps changes on a branch
- Check the changelog before upgrading. v5.0.0 changed CMS array fields and requires stable `id` values

## What the review panel asked for

- Plain HTTP or MCP surface
- Publish the rate limits
- Add an error reference

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.