Skip to content

EP Provisioning

EP Provisioning turns a freshly-installed PageMotor site into a receiver for automated setup. A central Discovery AI server can push configuration (theme, plugins, initial content, assistant memory, API keys) to a brand-new site and the site configures itself from that payload. Designed for hosting companies rolling out AI-managed websites at scale.

Published by ElmsPark Studio.

  1. A prospective customer talks to Discovery AI on the hosting company’s central server.
  2. Discovery AI extracts brand voice, services, audiences, and other context from the conversation.
  3. The hosting company’s automation spins up a VPS with fresh PageMotor.
  4. EP Provisioning is pre-installed with an API key.
  5. Discovery AI POSTs the provisioning payload to the new site.
  6. EP Provisioning applies it: sets theme colours, activates plugins, writes assistant memory files, configures EP Assistant with its own API key, creates a default contact form.
  7. The customer receives a welcome email with a magic-link login, lands in their admin panel, and starts managing their site through conversation.

Receives a signed JSON payload and applies the contents:

  • Site metadata. Business name, address, phone.
  • Theme customisation. Colours, fonts, logo.
  • Plugin activation. Activates listed plugins in the correct order.
  • Content seeds. Creates default pages (home, about, contact).
  • Default contact form. Creates a “main” form in EP Email.
  • Assistant memory files. Writes 6 markdown files to ep-assistant/src/memory/ (brand voice, audiences, services, site inventory, discovery context). The brand-voice file’s writing rules can be customised via an optional writing_rules array in the brand_voice payload (e.g. ["British English always", "Sentence case headings"]). Without one, a neutral default applies — no regional spelling is forced on the provisioned site.
  • Plugin API keys. Configures EP Assistant with its own Anthropic key.
  • Webmaster user. Creates or updates the admin account with a magic-link login token.
  • PageMotor 0.11.5 or later
  • EP Suite base class
  • EP Email, EP Assistant and other plugins mentioned in the payload must also be installed on the target site for their sections to apply.

EP Provisioning is typically installed as part of the fresh-site automation rather than manually. If you’re setting up a provisioning target by hand:

  1. Download ep-provisioning.zip from the EP Suite downloads page.
  2. Upload and activate.
  3. Open Plugin Settings → EP Provisioning.
  4. Click Generate API key.
  5. Share the key with the central Discovery AI system so it can POST here.

POST to the site’s home page (https://targetsite.com/) as an ordinary form post (application/x-www-form-urlencoded), with:

  • ep_provision=provision
  • api_key=YOUR-API-KEY
  • theme_data and customer_email (required), plus any of the optional fields: customer_name, business_name, customer_slug, compiled_css, pages, images, services, jurisdiction, assistant_memory, assistant_api_key and, since 1.6.0, brand_kit.

Fields that carry structured data (theme_data, pages, images, services, assistant_memory, brand_kit) are JSON text.

The response is JSON: {"success": true, ...} with a line for each step that ran, or {"success": false, "error": "..."}.

Since 1.6.0, provisioning can create a page as a PageMotor HTML document: served exactly as written at its own address, not wrapped in the site’s theme. This is the kind of page EP Editor and ad landing pages use.

Add it to pages with "type": "html" and the full page as "document":

[{"type": "html", "slug": "spring-offer", "document": "<!DOCTYPE html><html><head><title>Spring offer</title></head><body>...</body></html>"}]
  • slug sets the address. title is optional: without it, the page’s <title> (or first heading) is used.
  • status is "live" (the default) or "draft".
  • {{IMAGE_BASE_URL}} is filled in, as it is for the theme, when images are sent in the same request.
  • Sending a page with the same slug again updates that page rather than making a second one.

The page goes live on the site’s next visit. PageMotor adds the site’s favicon, social sharing image, page title and structured data to every HTML document. Those settings are not loaded yet while provisioning runs, so the page is saved as a draft and finished on the very next visit to the site (any page, including the owner’s first login), then published. Until then nobody can see it. The response lists each page with its address and "state": "finishes on the next request to the site".

A page that cannot be used (no HTML in it, or a status other than live or draft) is listed under html_pages_errors and the rest of provisioning carries on.

Since 1.6.0, the brand can arrive as one object in the brand_kit field:

{
"name": "Kestrel Coffee",
"colours": {"primary": "#12343b", "accent": "#c0392b"},
"fonts": {
"css": "https://fonts.bunny.net/css?family=inter-tight:400,600&display=swap",
"display": "\"Inter Tight\", system-ui, sans-serif",
"body": "\"Inter Tight\", sans-serif"
},
"logo": {"url": "https://example.com/logo.svg", "alt": "Kestrel Coffee", "width": 160, "height": 26},
"voice": {"tone": "Warm and plain", "words_to_avoid": ["synergy"]}
}
  • name is required. Everything else is optional.
  • colours: each colour has a role you choose (primary, accent, ink…) and a hex value. A list of {"role": ..., "hex": ...} works too.
  • fonts must load from fonts.bunny.net, the privacy-friendly mirror of the Google Fonts catalogue (same address shape, swap the domain). A Google Fonts address is refused.
  • logo can also be just the address.
  • voice is a paragraph, or the same tone / words_to_use / words_to_avoid / writing_rules shape as assistant_memory.brand_voice.

What provisioning does with it:

  • Theme. The colours and font stacks become CSS variables (--brand-primary, --brand-font-body and so on) in the new theme’s stylesheet, the kit’s Bunny Fonts stylesheet is loaded, and the colours appear in the theme editor’s variables when the theme data has its own variables.
  • HTML pages. Each one gets the same variables and font link at the top of its head, so its own styles can use var(--brand-primary). {{BRAND_NAME}}, {{BRAND_LOGO}} (a ready-made image tag), {{BRAND_LOGO_URL}} and {{BRAND_LOGO_ALT}} are filled in.
  • Business name and voice. The kit’s name is used as the business name when none is sent, and its voice goes to EP Assistant’s brand-voice notes when no brand_voice is sent.
  • The checked kit is kept on the site, so later tools can read the same brand back.

A kit with a mistake stops provisioning before anything changes. The response is 400 with a message saying what is wrong, for example colour "primary" must be a hex value like #12343b. Keys the kit does not use are listed under brand_kit.ignored_keys and do not stop anything.

Existing set-ups are unaffected. Without brand_kit, nothing changes. When the kit and an older field disagree, the older field wins: a font import in compiled_css, a business_name, or a brand_voice in assistant_memory is kept.

  • API key authentication on every request.
  • IP allowlist on the settings page — restrict to your Discovery AI server’s IP.
  • Audit log of every provisioning request, successful or failed.
  • Once activated a provisioning site can be locked: subsequent requests are rejected unless you re-enable. Prevents a stolen key from being used to reconfigure a live site.
  • Missing plugin. Payload asks to configure EP Booking, but EP Booking isn’t installed. Plugin logs the failure and continues with other sections.
  • Schema mismatch. Payload has unknown keys. Logged as warnings; known keys still process.
  • Bad API key. Request rejected with 401.
  • Rate limit. Too many provisioning attempts from the same key in a short window are throttled.

“Provisioning request fails with 401 Unauthorized”

Section titled ““Provisioning request fails with 401 Unauthorized””

API key is wrong or disabled. Regenerate and update on the Discovery AI side.

“Some plugins got configured, others didn’t”

Section titled ““Some plugins got configured, others didn’t””

The log shows which sections applied and which didn’t. Missing plugins are the usual culprit — EP Provisioning can only configure what’s installed.

“The provisioned site’s admin login doesn’t work”

Section titled ““The provisioned site’s admin login doesn’t work””

Check the magic-link token hasn’t expired. Tokens have a default 24-hour window. Customer can request a password reset if they miss the window.

“Site was accidentally re-provisioned and customer’s data was overwritten”

Section titled ““Site was accidentally re-provisioned and customer’s data was overwritten””

This is why the Lock after provisioning setting exists. Turn it on after first successful provision. If the damage is done, restore from a backup.

“I want to manually trigger provisioning from the central side to re-sync”

Section titled ““I want to manually trigger provisioning from the central side to re-sync””

On the target site, clear the lock, then POST a fresh payload. Audit log tracks the re-sync event.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

  • Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.

A security update. Please install it.

  • The health check no longer returns your API key.
  • Sign-in tokens are single-use and tied to their account. A sign-in link works once, and only for the account it was made for.

A security update. Please install it.

  • Once a site is yours, nobody else can reset it. The central setup server can still reset a site and send it again while it is being built. As soon as you sign in for the first time, by your login link or with your password, that reset is switched off for good, so it can never remove your account or reopen your site.
  • Setup only accepts safe names and real images. The site’s short name must be plain letters, digits and hyphens, and only genuine PNG, JPEG, GIF and WebP images are saved. Anything else is refused before it is written.
  • Provisioning can now create plain HTML pages. The new site gets the page as a PageMotor HTML document: served exactly as written, at its own address, not wrapped in the site’s theme. This is the kind of page EP Editor and our ad landing pages use.
  • Each HTML page gets the site’s head, done properly. PageMotor adds the site’s favicon, social sharing image, page title and structured data to every HTML document. Provisioning saves the page as a draft first and lets PageMotor finish it on the site’s very next visit, when those settings are fully loaded, then publishes it. Before that first visit the page is not shown to anyone, so it is never seen half-made. A page sent with "status": "draft" stays a draft.
  • Sending the same page again updates it. A page with the same address replaces the earlier version rather than making a second copy.
  • A brand kit, supplied in one go. It takes the brand’s name, colours (each with a role, such as primary or accent), logo, fonts and voice. Provisioning checks it, then uses it everywhere at once: the colours and fonts go into the new theme and the theme editor, into every HTML page’s head, and the voice goes to EP Assistant. HTML pages can use brand placeholders for the name and logo, filled in from the kit.
  • Fonts only from Bunny Fonts. A kit’s fonts must load from fonts.bunny.net, the privacy-friendly mirror of the Google Fonts catalogue. A Google Fonts address is refused with a message showing the Bunny address to use instead.
  • A kit with a mistake is refused before anything changes. If the kit is not valid, provisioning stops with a clear message saying what is wrong (a colour that is not a hex value, a missing name, a font address that is not Bunny Fonts) and nothing on the site is touched.
  • Nothing changes for existing set-ups. Every field provisioning already took works exactly as before. When a kit and an older field say different things, the older field wins: your own stylesheet’s font, your own business name and your own brand voice are kept.
  • Needs PageMotor 0.11.5 or later.
  • A new site’s EP Assistant starts on Claude Sonnet 5.5. When provisioning sets up EP Assistant with a key, it now chooses Sonnet 5.5, which costs about a third less than the Sonnet 4.6 it chose before.
  • Needs PageMotor 0.11.5 or later.
  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • Saved keys and passwords that stopped working are recovered. On PageMotor 0.11.3 or later, a key or password saved in this plugin’s settings before this plugin protected its keys itself could be kept in a scrambled form the plugin could not read, so the connection it was for failed. The plugin now unscrambles it once and keeps it protected as usual.
  • If a saved key cannot be recovered, it is no longer stored in its unreadable form. The error log says which one to enter again in the plugin settings.
  • Keys you save from now on are unaffected.
  • Fixes stored keys and passwords reading as empty after a PageMotor 0.11.3 or 0.11.4 update. After the core update, every secret this plugin had encrypted at rest came back blank, so anything that needed it failed with an authentication error until the value was typed in again. Nothing was deleted: the encrypted value was still in the settings row, but PageMotor 0.11.3 moved the site secret that opens it, and this plugin was still looking in the old place. It now finds the secret in both places, so an existing value opens again without re-entry, and a value that was re-entered in the meantime keeps working and is moved back under the site secret.
  • If you updated PageMotor and then re-entered a key or password, there is nothing to do. If you updated and have not re-entered it, this release restores it on the next page load.
  • Your API key is now stored encrypted. Existing values are converted automatically, with nothing to re-enter.
  • Existing sites convert themselves the next time the plugin loads, once. There is nothing to re-enter and no key to replace.
  • Reading your settings over the API now returns a placeholder rather than the value, and writing that placeholder back leaves the stored secret untouched. Clearing it by submitting an empty value still works as before.