Update Your Page by Talking to an AI Assistant Instead of an Editor

Keeping a page current is small work that adds up: a new product here, a section that needs reordering, a promo code on your affiliate links, a seasonal theme swap before a sale. None of it is hard — it’s just time you’d rather spend on the actual business. If you’re the kind of person who already asks an AI assistant to draft your captions or answer your email, there’s no reason your page should be the one thing you still manage by hand.

So we built a way to hand that off too. Keepp has an HTTP Agent API and a ready-made skill, which means you can connect an AI assistant — ChatGPT, Claude, Gemini, or your own agent — and manage your whole page by describing what you want in plain language.

What the Agent API actually does

The mechanics are simple, and worth understanding even if you never touch the raw API yourself. A Keepp page is stored as a single page document: an ordered list of blocks — links and buttons, cards, profile, socials, headers, text, forms, maps, products, bookings — plus a theme object controlling fonts, colors, and corner radius. The API exposes exactly two operations on that document: one call reads the whole thing, and one call replaces the whole thing. There’s no block-level “add one thing” endpoint — an assistant fetches your entire page, decides what the new version should look like, and sends the entire thing back.

That whole-document model is why an assistant can do things a single-purpose “add a link” tool couldn’t: it can see everything already on your page before deciding where a new block belongs, whether your page has gotten long enough to need sections and tabs, and whether an existing block should just be edited instead of duplicated. It’s the same document the visual editor reads and writes, so nothing about it is a shadow copy — change your page with an assistant, and it’s exactly as published as if you’d dragged a block into place yourself.

Products and bookings are the one part of that document the API can’t write. You still create products and set prices under Products, and define availability under Bookings, in your dashboard — the same as connecting Stripe and selling a product, or setting up a booking calendar. The agent can read that list and place any of it onto the page — as a card, in a header section, reordered, resized — but it cannot create a new product, change a price, or invent a bookable slot through the API. That’s a deliberate line: your API key controls how your page looks, never what a customer gets charged.

There’s a second guardrail worth knowing about. A page tops out at 100 blocks, and that cap is enforced identically on both sides — the editor and the API. If an assistant tries to push a page past it, the whole update is rejected outright, not silently truncated. You never end up with a page that lost its bottom half because an agent tried to cram in too much.

What that looks like in practice

Once your assistant has your key and the skill, you talk to it the way you’d brief an assistant, not the way you’d write code:

• “Add a header called Shop and put my three products under it.”
• “These are affiliate items. Put my code GLOW15 on each and link the button to my referral URL.”
• “Add a form for my free challenge that collects emails.” — see collecting leads and feedback for what fields a form block supports.
• “Change my brand color to deep green, round the corners, and pick a font pairing that feels warmer.” — the same controls covered in styling your page and choosing a font pairing.
• “Add a booking block for Tuesday and Thursday afternoons, 2 to 5pm, and move it above the products.”
• “This page has gotten long — break it into sections and give it tabs.” — exactly the reorganizing structuring a long page describes doing manually.
• “My workshop sold out — take that card down and add a waitlist form instead.”
• “Schedule the holiday banner to go live December 1st and come down January 2nd.” — the scheduling an assistant can set up for you.

Notice the booking example: the assistant can’t invent a bookable service, but once you’ve defined “1-on-1 consult, 30 minutes” under Bookings, it absolutely can decide which afternoons to expose, build the block, and place it wherever makes sense on the page — reading and reasoning about your calendar settings is different from fabricating them.

It reads your page, makes the changes, and publishes. What used to be ten minutes of clicking through the editor becomes one sentence.

Which assistants this works with

The API is plain HTTP, so anything that can make a request and hold a conversation can drive it — this isn’t a Keepp-specific chatbot, it’s your own assistant with a key. In practice that means:

• Claude, ChatGPT, and Gemini in their normal chat interfaces — paste in the skill file, give them your key, and describe what you want.
• Claude Code, installed as a plugin (/plugin marketplace add thinslatelabs/keepp-skill) for people who already live in a terminal-based coding assistant.
• Any custom agent or workflow tool built on the raw API — the developer docs and llms.txt are the reference if you’re wiring this into something of your own.

The skill is the part that makes this reliable rather than a coin flip. It isn’t just API documentation — it teaches the assistant judgment: when a plain link beats a product card, when a page needs sections and tabs instead of one long scroll, when a form on the page will convert better than a link out to one. That’s the difference between a page that looks like a pile of blocks an AI dumped out and one that looks like something you’d have built yourself with an eye for how a Keepp page actually works. It’s open source and free: github.com/thinslatelabs/keepp-skill.

Why it’s read-only on money, and why the whole page gets replaced

Two design choices are worth explaining rather than just stating, because they’re the reason this feels safe to hand to an assistant instead of nerve-wracking.

Read-only on products and bookings is a trust boundary, not a missing feature. An API key that could create a product would also be a key that could create a product priced at whatever an assistant hallucinated, or a booking slot that didn’t correspond to real availability. By keeping catalog creation in the dashboard — where you’re setting the actual dollar figure and connecting the actual Stripe account — the API can be generous with everything else (copy, layout, theme, ordering) without ever putting a transaction at risk. This is the same instinct behind getting paid your way: Keepp separates the part that touches money from the part that just arranges what a visitor sees.

Whole-document replacement is why “ask it what changed” matters. Because an update sends the complete block list back, a careless assistant could in principle drop something by leaving it out of its response. The skill explicitly instructs assistants to read the full page before writing anything back, and every response is expected to report block counts before and after. In practice this is rarely an issue, but it’s the one habit worth keeping: after a big request, skim the published page and ask the assistant what it changed if anything looks off. It still has your original page in the conversation, so undoing a mistake is another sentence, not a support ticket.

How this differs from editing in the visual editor

Nothing here replaces the editor — it sits alongside it. The editor is the right tool when you’re making a visual judgment call in real time: does this photo crop look right, does this button feel too big, does the map block sit in the right spot relative to your hours. Those are decisions that go faster with your eyes on the page and a mouse in your hand.

The Agent API earns its keep on a different kind of task: batch changes, restructuring, and the stuff you’d rather describe than click through. “Reorganize everything I sell into three sections by category” is a fifteen-minute drag-and-drop session in the editor and a ten-second sentence to an assistant. Seasonal refreshes, promo-code updates across a dozen affiliate cards, taking a sold-out item down and swapping in a waitlist form — these are the tasks where typing out the intent is genuinely faster than pointing and clicking, and they’re also the tasks people tend to defer because clicking through them feels tedious. An assistant with your key doesn’t get tedious about it.

You never have to use it. Everything the Agent API does, you can still do by hand in the editor — it’s there for the days you’d rather describe the result than click through it, not a replacement for having an editor at all.

Common questions

Do I need a developer to set this up? No. Generating a key is a button in your dashboard, and giving an assistant the skill file is copy-paste. The step-by-step walkthrough covers the whole flow with no code involved unless you’re building your own integration.

Can the assistant see my customers’ data? No. The API operates on your page document — blocks, layout, theme — and reads your product and booking definitions to place them. It doesn’t expose buyer information, submissions, or analytics. For that, reading your submissions and understanding your analytics are separate, dashboard-only views.

What if I don’t like what it did? Ask it to change it back — the conversation still holds your previous page state. Nothing an assistant publishes is more permanent than anything you’d publish yourself from the editor; it’s the same document, the same undo instinct.

Is this a Pro-only feature? Yes — the Agent API is part of the Pro plan and above, alongside things like scheduled blocks, custom fonts, and full analytics.

What happens if my key leaks? Treat it like a password. Open AI Agent in your dashboard and hit Regenerate or Revoke — the old key stops working immediately, and you can only ever have one active key at a time, so there’s no orphaned second key floating around with access.

Getting started

1. Open AI Agent in your Keepp dashboard and generate an API key.
2. Give your assistant the skill and your key.
3. Tell it what you want your page to say.

The step-by-step is in Manage your page with an AI agent, and developers can dive into the full API reference. If you’re still deciding whether Keepp’s block model fits what you’re building, how your page works and choosing the right block are the two guides worth reading first.

---

Claim your keepp.link/yourhandle page free — no credit card, live in minutes.