WebsitePublisher.ai

Build and publish real websites through conversation. You describe it — the AI builds and deploys it.

The user's credentials are set as environment variables:

• - WEBSITEPUBLISHER_TOKEN — API token (starts with wpa_)
• INLINECODE2 — Project ID (numeric, e.g. 12345)

If either variable is missing, stop and instruct the user:

1. 1. Sign up at https://www.websitepublisher.ai/dashboard
2. Copy their API token and Project ID from the dashboard
3. Add to their OpenClaw config:

   {
     "env": {
       "WEBSITEPUBLISHER_TOKEN": "wpa_xxxx...",
       "WEBSITEPUBLISHER_PROJECT": "12345"
     }
   }
   

Authentication

Every API call requires these headers:
CODEBLOCK1

Base URL: https://api.websitepublisher.ai

Workflow — Build a Complete Website

When asked to build a website, follow this exact sequence:

Step 1 — Check existing content

This returns the project URL, existing pages, and current status. Always do this first.

Step 2 — Create pages (use bulk for multiple pages)

Single page:
CODEBLOCK3

Multiple pages at once (preferred — saves API calls):
CODEBLOCK4

Step 3 — Upload assets (images, CSS, JS)

Asset URL pattern: https://cdn.websitepublisher.ai/[path]/[slug]
Reference assets in HTML using this CDN URL.

Step 4 — Confirm live URL

The project URL is returned by the status endpoint. Share it with the user.

PAPI — Pages & Assets (Full Reference)

Pages

Page fields:
CODEBLOCK6

Patch a page (partial update — send only changed HTML fragment):
CODEBLOCK7

Assets

Asset fields:
CODEBLOCK8

Tip: You can pass a public image URL as content — the platform fetches and stores it automatically.

MAPI — Dynamic Data (Products, Blog, Team, etc.)

Use MAPI when the website needs structured, repeatable data — product listings, blog posts, team members, portfolio items, etc.

Create an entity (data model)

Create records

Note: MAPI endpoint uses the plural entity name — e.g. /products not /product.

MAPI Reference

Public read: MAPI records are publicly readable at the same endpoint without a token — useful for frontend JavaScript fetching live data.

SAPI — Contact Forms

Add a working contact form to any page in two steps.

Step 1 — Configure the form

Important: Always send ALL fields on every configure_form call — no partial updates.

Step 2 — Add the form HTML to the page

The API returns a form_id. Use this snippet in the page HTML:
CODEBLOCK12

SAPI Reference

Rate Limits

Always prefer bulk endpoints (/pages/bulk, /assets/bulk) over individual calls to stay within rate limits. A bulk call counts as one request regardless of how many items it creates.

Common Patterns

Landing page (one page)

1. 1. GET /status — check project
2. INLINECODE38 — create index.html with full content
3. INLINECODE40 — configure contact form if needed
4. Share project URL

Multi-page website

1. 1. GET /status — check project
2. INLINECODE42 — create all pages in one call
3. INLINECODE43 — upload all images in one call
4. INLINECODE44 — configure contact form on contact page
5. Share project URL

Website with dynamic data (e.g. product catalogue)

1. 1. GET /status — check project
2. INLINECODE46 — create data model (e.g. "products")
3. INLINECODE47 — create records (one per product)
4. INLINECODE48 — create pages with JS that fetches MAPI data
5. Share project URL

Error Handling

All endpoints return standard HTTP status codes:

On error, the response body always contains a message field with a description.

Support & Docs

• - Dashboard: https://www.websitepublisher.ai/dashboard
• Full API docs: https://www.websitepublisher.ai/docs
• PAPI docs: https://www.websitepublisher.ai/docs/papi
• MAPI docs: https://www.websitepublisher.ai/docs/mapi
• SAPI docs: https://www.websitepublisher.ai/docs/sapi