What agents can do
Rubikc is built so that an agent can do the work. Admin is one way into your Space; an agent is another, with almost the same reach.
That is a design decision rather than a side effect. The things a merchant spends their time on — building cubes, writing content, arranging feeds, importing, checking analytics — are all available to an agent.
What an agent can change
Section titled “What an agent can change”| Area | What it can do |
|---|---|
| Cubes | Create, update, search, publish, and set relations between them |
| Blocks | Write and edit content, including per-language versions and overlays. An agent can look up every block type — its purpose, schema, and where it can be placed — before writing. |
| Versions | Arrange which blocks appear, and in what order, including shared blocks, surveys, and generated blocks. Agents can insert, move, or remove one block without replacing the whole version, including across every language at once. |
| Shared blocks | Create and edit content reused across cubes |
| Feed | Configure the feed and what is pinned |
| Structure | Menus and cube groupings |
| Sources | Run imports and turn source material into cubes |
| Files | Upload and organise media |
| Brand | Brand and appearance settings |
| Onboarding | Work through setup |
What an agent can read
Section titled “What an agent can read”Analytics for your Space and individual cubes, session detail, survey results, sync and transform logs, and the overall shape of your Space.
Reading is where agents are most immediately useful, because the work is volume — going through every cube against a standard you describe. An agent can inventory blocks, versions, languages, and publish status for a whole Space in one pass, then open individual cubes only where it needs to edit.
What an agent cannot touch
Section titled “What an agent cannot touch”Deliberately out of reach:
- Integrations. Connecting or re-authorising Shopify, Instagram and the rest.
- Your domain. DNS and custom domains.
- Checkout settings.
- Access. Members, invitations, and who can reach your Spaces.
These are the settings where a mistake is expensive or hard to undo, and they stay with you.
Working across systems
Section titled “Working across systems”An assistant is not limited to Rubikc. MCP is an open standard, so the same assistant can be connected to Rubikc and to your other tools at once — and act across them in a single piece of work.
That makes some things possible that neither system could do alone:
An SEO tool reports that a set of product pages have thin descriptions. The assistant reads that list, finds the matching cubes in Rubikc, drafts better content for each, and leaves it unpublished for you to review.
The pattern is the same whatever the other system: something else finds the problem, Rubikc is where it gets fixed. Because almost all of a Space is reachable by an agent, the fix does not have to come back to a person to be typed in by hand.
What this does not mean
Section titled “What this does not mean”Two things make the difference between an agent that helps and one that creates work:
- Fill in your content playbook. It is the guidance an agent works from.
- Keep publishing for yourself. See Working safely with an agent.