Keepp Agent API

Build and run your Keepp page from an AI app, or from your own code. Connect an MCP app like Claude or ChatGPT, or call the HTTP API with a key.

https://api.keepp.link/mcp

HTTP API

For your own code. Available on Pro. Generate a key from your dashboard under AI Agent.

Authentication

Send your key as a bearer token. Base URL https://api.keepp.link.

Authorization: Bearer keepp_live_…

Endpoints

A page is a list of blocks

Blocks sit on a two-column grid. A full block takes a row; two half blocks pair side-by-side. Array order is the order on the page.

PUT https://api.keepp.link/api/v1/page
{
  "version": 12,
  "theme": { "roundedness": "soft", "brandColor": "#C2185B" },
  "blocks": [
    { "id": "2f9c…", "type": "profile-circle", "size": "full",
      "name": "Studio Marlow", "about": "Hand-thrown ceramics." },
    { "id": "7a41…", "type": "header", "size": "full", "text": "Shop", "showInNav": true },
    { "type": "product", "size": "half", "productId": "8f2c…" },
    { "type": "card", "size": "half", "kind": "promo-code",
      "title": "20% off your first order", "code": "FIRST20" }
  ]
}

Block envelope

Scheduling

Any block can be given a window, and it only appears inside it:

"schedule": { "from": "2026-08-01T09:00", "until": "2026-08-14T23:59", "tz": "Asia/Kolkata" }

At least one of from / until is required. Times are deliberately local rather than UTC, so 9am Friday stays 9am across a daylight-saving change. The window is evaluated server-side when the page is read, so a block that hasn’t started isn’t in the HTML at all, so it can’t be found in view-source. Scheduled blocks still count toward the 100-block limit.

Block types

A menu item is { name, description, price, tags[] }. Keep descriptions to 50 words, up to 100 items, and no more than 10 distinct tags per menu.

* required. profile-cta and nav are singletons, one each per page.

Form fields

A form takes a fields array of { id, label, type, required }, where id is a UUID you generate. Submissions land in your dashboard.

Sending no identifier, or two, rejects the whole PUT. It’s the most common reason a hand-built form block fails.

Card kinds

Use a card for something sold elsewhere. For something bought on your page through Stripe, use a product block.

Products & bookings

Call GET /api/v1/catalog and send only the reference: { "type": "product", "productId": "…" }. The server fills title, price, images and buyability from the record, so any values you send for those are overwritten. This is deliberate: a key can never publish a price the seller didn’t set.

Images

Put a public https image URL in mediaUrls, imageUrl, or iconUrl and it’s fetched and stored for you. Paths already starting with /uploads/ are yours already, so send them back unchanged.

Theme

Unrecognised theme keys and invalid values are silently dropped, not rejected, so a typo in fontPairing leaves your fonts unchanged with no error. Re-read the page if you need to confirm a theme change landed.

Limits

• Up to 100 blocks per page.
• Images up to 10 MB each (JPEG/PNG/WebP/GIF), from a direct public https URL.
• 60 requests per minute per key.
• Writes publish to your live page immediately. There is no draft state.
• A full page is roughly 6k tokens. If you’re generating one with an LLM, raise its output limit, because a truncated body fails as malformed JSON.

Errors

• 401 NO_API_TOKEN / INVALID_API_TOKEN: missing or revoked key.
• 403 PLAN_REQUIRED: the key’s business is not on Pro.
• 400 INVALID_INPUT: a block is malformed, or the page broke a rule.
• 422 INVALID_IMAGE: an image URL couldn’t be fetched, was the wrong type/size, redirected, or resolved to a non-public address.
• 404 NOT_FOUND: a productId or bookingUnitId isn’t yours.
• 409 VERSION_CONFLICT: you sent a version and the page moved. Re-read and reapply.
• 429 RATE_LIMITED: more than 60 requests in a minute.

Errors caused by one block include blockIndex, its position in the array you sent. A rejected write changes nothing, so your page is exactly as it was.

Using an LLM? Hand it the Keepp skill or the llms.txt index. Both teach it how to structure a good page, not just call the API.