llms.txt
Compare with other sites' llms.txt files →# Spectersync
> A write layer for Ghost, WordPress, Shopify and Webflow content. Read any post, page, article or product as markdown with the same frontmatter on every platform, and write it back through one contract — with a dry-run diff, an optimistic lock and a snapshot before every publish.
Spectersync is a hosted web app at https://app.spectersync.com, a REST API, a hosted MCP server, and an open-source sync daemon. The product it sells is not the reading: it is the guarantee that an automated write cannot silently overwrite a human's edit and cannot be published without a reversible snapshot.
There are two routes to a live write, and both end in the same code.
The review link is the free plan's only route, and is available on every plan. The agent stages its edits into working copies, then calls `create_review` (MCP, live) or `POST /v1/reviews` (REST, which ships with the rest of `/v1` and returns 404 in production today — see the OpenAPI note below). Everything staged becomes one page of before/after cards at `https://app.spectersync.com/r/<token>` — no login — where a person accepts, rejects with a note, or skips each change. Only an accept reaches the CMS, and it runs the ordinary publish path: revision lock, mandatory pre-publish snapshot, credit reservation. The link is a bearer capability and expires within a day (24 hours by default, 1 to 24 on request). A decision can cover one FIELD of a page rather than the whole card — "accept all SEO descriptions" publishes that field on those pages and nothing else on them — and a card stays PENDING until every changed field has been ruled on, including a field whose publish attempt failed or hit the revision lock: that field can still be retried, rejected or skipped, and the rest of the card is never blocked by it; `review_status` / `GET /v1/reviews/{id}` report `accepted_fields`, `rejected_fields` and `pending_fields` per card. What an accept sends the CMS is the document as it was frozen when the link was made, plus the approved fields, so edits staged after the link went out are never published under that approval. At expiry the batch is deleted and every field that was never accepted — pending, skipped, rejected-already-restored, or one a publish attempt failed or conflicted on — is rolled back out of the working copy to what it was before the batch; a field an accept already published stays live. Doing nothing publishes nothing, in every state a field can be in. Creating reviews is capped at 10 an hour per workspace — shared by every API key in it, because the mailbox each one lands in is the workspace owner's, not the key's — because each one emails the workspace owner; over that the call is `429 rate_limited`. Rejections carry a comment, which the agent reads back through `review_status` / `GET /v1/reviews/{id}` so it can redo the edit — except on Pro, where a reject with a comment regenerates the field itself (one credit, capped per page and per batch) and requeues it as a new card in the same batch, marked with `regenerated_from`, so there is nothing left for the agent to redo. A free key that calls `publish` with `confirm: true`, or `PUT` with `dryRun: false`, is refused with `402` and `error.type: "use_review_url"` naming that flow; its dry runs, reads and reverts are unaffected.
Publishing straight from the client is the Pro path, and it always takes two steps: a dry run that returns the exact field-level diff and writes nothing, then an explicit publish carrying the version stamp that was read and the id of that dry run. The id is bound to the whole document that would go live — not merely the fields in the request, so content staged through any other route in between voids it — and it works once. The change that reaches the site is therefore the change that was approved. A page changed in the CMS in between produces a conflict, not an overwrite.
## For agents and developers
- [API and MCP](https://spectersync.com/api): endpoints, auth, error codes, credit cost, and the complete MCP setup block for each supported client.
- [OpenAPI 3.1 contract](https://app.spectersync.com/api/v1/openapi.json): generated from the schemas the endpoints validate against. Not deployed yet — this URL and the rest of `/v1` return 404 today, while the MCP endpoint below is live.
- [Hosted MCP endpoint](https://app.spectersync.com/api/mcp): Streamable HTTP, authenticated with a workspace API key.
- [MCP setup](https://spectersync.com/api#install): a complete block for nine clients — Claude Code, Claude Desktop, Cursor, Windsurf, Gemini CLI, Antigravity, Devin, VS Code Copilot and Codex CLI — plus where ChatGPT stands. Claude Code, Claude Desktop and Cursor have been run against the live endpoint; the other six were written from each client's current docs and are tagged "Not yet verified" on the page. ChatGPT has no block: its custom connectors take OAuth or no auth, never a bearer key.
- [Source](https://github.com/gospecter/specter): the sync engine and CMS adapters, AGPL-3.0.
## Product
- [How it works](https://spectersync.com/how-it-works): pull, edit, diff, publish, revert.
- [Capabilities matrix](https://spectersync.com/capabilities): exactly which fields each platform can read and write, including the gaps.
- [Recipes](https://spectersync.com/recipes): the prewritten content operations that run across a whole archive.
- [Pricing](https://spectersync.com/pricing): 400 credits once at signup, $29 for another 400, Pro $99/month with unlimited credits within fair use (5,000 documents a month), additional users $49/month each on the same Pro workspace. Free and credit packs are the safe execution layer only: they publish through the review link, and recipes, bulk runs and the site index are Pro.
## Platforms
- [Ghost](https://spectersync.com/ghost)
- [WordPress](https://spectersync.com/wordpress)
- [Shopify](https://spectersync.com/shopify)
- [Webflow](https://spectersync.com/webflow)
## Optional
- [Spectersync Core](https://spectersync.com/local): the desktop app and daemon that sync a CMS to a local markdown folder.
- [FAQ](https://spectersync.com/faq)
- [Changelog](https://spectersync.com/changelog)
- [Privacy](https://spectersync.com/privacy) · [Terms](https://spectersync.com/terms)