Your clients edit. Your static site rebuilds.

Building with AI agents? Blue is a plain HTTP API with a discovery document — one request returns every endpoint and the auth rule. See what that looks like →

Wire it up in a few lines

No SDK, no plugin, no adapter — it's a plain HTTP API. Your exact URL is shown when your site is created.

---
const res = await fetch(
  'https://your-site.wp.cms.blue/wp-json/wp/v2/posts'
);
const posts = await res.json();
---
{posts.map(p => <h2 set:html={p.title.rendered} />)}

export default async function () {
  const res = await fetch(
    'https://your-site.wp.cms.blue/wp-json/wp/v2/posts'
  );
  return res.json();
}

export default async function Page() {
  const res = await fetch(
    'https://your-site.wp.cms.blue/wp-json/wp/v2/posts'
  );
  const posts = await res.json();
  return posts.map(p => <h2 key={p.id}>{p.title.rendered}</h2>);
}

# Add a CMS connector pointing at
https://your-site.wp.cms.blue/graphql

# Design visually, publish to GitLab Pages.

For agents

One request returns every endpoint and the auth rule. No key needed to read, so an agent can start before anyone signs up.

# Discovery
curl -H "Accept: application/json" https://your-site.wp.cms.blue/

# Writing needs an Application Password, made in the WordPress profile
curl -u USER:APP_PASSWORD -X POST \
  https://your-site.wp.cms.blue/wp-json/wp/v2/posts \
  -H "Content-Type: application/json" \
  -d '{"title":"Hello","status":"draft"}'

The honest part: WordPress exposes about 750 GraphQL types and 260 kB of REST routes — far more than an agent should ingest. Query what you need, don't introspect the lot. A smaller view and a ready-to-use MCP endpoint are what we're building next; the Abilities API they rely on is already installed. Tell us how you'd want it shaped — that decides what we build.

Open source, and you can check

Everything we run is stock WordPress plus GPL plugins. Export whenever you want, reinstall elsewhere, and it all keeps working.