For developers.

The site connector

One plug–in pairs a member’s own WordPress site to their workspace over a signed channel, so the platform can read and change the site without anybody handing over a site password. It is one plug–in with one download door, whichever of its two names you arrived by.

The render plug–in

A companion plug–in that puts the platform’s own modules into WordPress pages as blocks and shortcodes — the render channel beside the connector’s control channel.

Sign in with your account

A first–party identity plug–in, so a member’s own site can use their platform account as its sign–in, with the modern authorization–code flow and proof of possession.

The agent door

The governed door itself, speaking the open agent protocol, with a full catalogue and a smaller curated set for clients that do better with fewer choices. Any compliant client on the internet can register, get consent and drive a workspace.

Your own model key

Under Provider Keys a member adds their own model provider key, tests it without storing anything, and pays that provider directly instead of spending platform credits. It is a premium–plan road.

The connections page

One place inside the product where third–party accounts are attached. Cards for providers whose keys are not yet in place say so plainly rather than pretending to be connected.

Captured from a demo business on a live account, in a browser kept apart from anyone’s own. No token, key or secret of any kind appears on this page or in any capture on it — not a value, not a prefix, not a shortened one.