Product 02
Live · pagewebpro.com

PageWebPro

Make the site. Take the bookings. Get paid. A website platform where the business machinery is part of the product — and where the entire editor is also an API an AI agent can drive.

At a glance
What it isA multi-tenant website platform with business modules built in
ForRestaurants, shops and makers, events and venues, studios and services
ServesServer-rendered HTML with a ~3 KB runtime; custom domains on every plan
Agent API120 MCP tools — pages, blocks, media, content, commerce, screenshots
PricingFrom €9 a month, per its own site
Why it exists

A website is
rarely the job.

The job is a table booked, a ticket scanned at the door, an order paid for, an enquiry that reaches a person. Most site builders stop at the brochure and sell you four more subscriptions that do not know about each other.

01

Four logins, one business

Site here, bookings there, tickets somewhere else, payments in a fourth place. Nothing reconciles, and the owner is the integration layer.

02

Embeds are slow and ugly

Third-party widgets arrive as iframes with their own fonts, their own colours and half a megabyte of script. The page you designed is not the page that loads.

03

Nothing is scriptable

Editors are built for a mouse. The moment you want an assistant, a bulk change or a hundred locations, you are back to copy and paste.

So the modules are part of the product.

What is in the box

Six modules,
one set of records.

Each has its own settings and its own data, and each renders a widget the published page draws at runtime. They are not add-ons; they are why the platform exists.

Forms

Validation, file uploads, spam protection, stored submissions and an email to a real inbox. The delivery half and the field half are edited separately, so a form can be restyled without breaking where it goes.

Bookings

Restaurant tables, rentals, appointments. Services, resources, availability windows, add-ons and pricing rules — with rescheduling and cancellation as first-class actions.

Tickets

Events with occurrences and tiers, sold through the same cart as products, checked in at the door by QR. Availability is fetched live rather than baked into a cached page.

Shop

Physical, digital and subscription products, a cart, a checkout, and payment through Mollie or Stripe — which means iDEAL and SEPA, not only cards.

Content

Define a content type, get a listing, a detail template and locale-aware URLs. Translations are scanned and managed per string, with machine translation available for a first pass.

Analytics

Cookieless visitor measurement, first-party, no consent banner required for the basics. You see traffic without handing it to somebody else first.

The agent API

An editor a
machine can use.

The platform speaks MCP, the protocol AI assistants use to reach real tools. Not a chat box bolted onto a builder — the same operations the visual editor performs, exposed as typed calls with validation, revisions and rollback.

Structure

Pages are JSON trees of blocks, addressed by path or by node id. An agent reads the subtree it will touch, validates its edit for free, then writes — all-or-nothing, one revision.

Sight

It can render the page through the platform's own server-side renderer and look at the screenshot, at mobile, tablet or desktop width. It can also read the emitted HTML.

Memory

Every site carries a shared project-context document that people and agents both write to, so the next session starts knowing how this site was built.

Scope

Pages, blocks, layouts, media, fonts and theme tokens, content types and entries, translations, forms, bookings, events, products and orders.

Proof, rather than a promise

The site you are reading was authored entirely through this API: the site record, the design tokens, the fonts, the navigation and footer, every block on every page, and the screenshots used to check the layout at each step.

Nothing here used a private endpoint. If an API can build a site of this kind, it can maintain a customer's.

See the commands that built the homepage
What the visitor gets

The heavy editor
never leaves the studio.

A published page is server-rendered HTML. The editor's framework is stripped out and replaced by a small runtime that powers forms, tabs, modals and reveals. Theme tokens and page CSS are inlined; unused theme rules are removed against the rendered markup.

Custom domains get certificates automatically at the edge. Sitemaps and robots are generated from the site's real URL surface rather than assembled by hand.

Runtime

About 3 KB of script on a published page.

CSS

Tokens and page rules inlined; the theme purged against the markup.

Images

Prebuilt renditions with a ready-made srcset and intrinsic dimensions, so pages do not shift while loading.

Languages

Multiple locales per site with hreflang, per-string translations and a machine-translation pass for the first draft.