Why We Built It
Because Agents Need More
Than a Post Endpoint
The native WordPress REST API was designed for the block editor and for trusted first-party clients. It assumes a logged-in user, cookies and nonces, and a human deciding what to send. None of those assumptions hold when the caller is an AI agent, a SaaS backend, or a build pipeline running unattended at three in the morning.
Every team that tried anyway ended up building the same missing layer: durable credentials that are not somebody's account password, permissions narrower than an editor role, request signing so a captured call cannot be replayed, block-aware writes so the editor does not choke on generated markup, and a log that answers the question of what actually published that post.
SyncDock is that layer, shipped as a plugin instead of rebuilt per project. It adds its own namespace, hashes its keys, scopes each one, understands Gutenberg blocks well enough to edit a single one, and gives an agent enough context about the site to write something worth publishing — while leaving everything WordPress already does completely alone.
Agent-Ready
An MCP-style surface built for autonomous clients, not browser sessions.
Credentials Done Right
SHA-256 hashed keys, shown once, revocable one at a time.
Least Privilege
Ten scopes so every integration gets exactly its own reach.
Block-Native
18+ core block types in, valid Gutenberg markup out.
Observable
Live metrics and a filterable log of every request the API served.
Additive, Never Disruptive
Its own namespace — existing REST integrations stay untouched.