10Web Partner Integration Guide — Agentic Website Builder

10WEB · PARTNER PLAYBOOK

Agentic Website Builder

Self-Hosted Integration Guide for Hosting Providers

FULLY WHITE LABELED

GO TO MARKET

Three ways to sell it

One technical integration unlocks three distinct revenue plays. Decide how you want to sell the agentic website builder — each option comes with its own natural funnel and integration approach.

Bundled Feature

Bundle in core hosting plans

Include the agentic website builder as a built-in feature on every hosting plan.

Revenue impact Higher signup conversion. Increased ARPU across all plans.

Add-On Upsell

Offer as a paid add-on

Sell the agentic website builder as an optional upgrade on your existing hosting plans.

Revenue impact Incremental revenue from the existing base. Clean attribution.

New Product Line

Launch as a standalone product

A separate agentic website builder — its own landing page, pricing, and audience.

Revenue impact New revenue stream from a new audience.

STEP 1 · DESCRIBE YOUR PLATFORM

🏔

Hosting panel as frontend & backend Customers log into cPanel, Plesk, DirectAdmin, CyberPanel, or similar directly

🖥

Hosting panel as backend only Customers see your custom dashboard — the panel runs behind it

🛠

Fully custom platform No hosting panel — you built the entire stack yourself

PRE-FLIGHT

Before you start

Configure your 10Web workspace once.

Set up branding

Upload your logo, colors, and product name. Customers see 10Web fully white-labeled.

my.10web.io/builder-api/branding →

Create an API key

Workspace-level master key. You’ll use it for website management and usage limits.

my.10web.io/builder-api/key →

Download the 10Web license plugin

You’ll install this on every WordPress site you prepare.

my.10web.io/builder-api/setup-guide →

Review the API documentation

One gateway API + one WordPress REST API. That’s it.

apidocs.10web.io/self-hosted/ →

ARCHITECTURE

Integration overview

Regardless of how you sell it, every integration is built from the same core components. The order changes depending on your funnel.

What you build

Configure your brand identity in the 10Web workspace — logo, colors, fonts, and domain. Everything downstream inherits your branding so the end user never sees 10Web.

Build a prompt input in your own UI — on a landing page (before signup) or inside your customer dashboard (after signup). The prompt is a single free-text string describing the website the user wants, passed to the generation API.

A WordPress site with the 10Web license plugin installed and activated via the WP REST API. The license plugin automatically installs all other required plugins and the theme, then deletes itself. Pull from a warm pool for instant response, or provision on demand.

⚠ Store website_id in your database — you need it for limits, usage tracking, and lifecycle management.

Add the 10Web license plugin to your hosting panel’s auto-installer plugin/theme set — WordPress Toolkit (Plesk), Softaculous (cPanel), Installatron, or similar. When users install WordPress, the license plugin is included automatically — no REST API provisioning needed.

⚠ Store website_id in your database — retrieve it via the Get website ID endpoint after the user completes generation.

Generate a one-time login token and redirect the user straight into the WordPress editor. They never see a WordPress login screen — the experience feels native to your platform.

Create subscription plans, handle payments, and manage billing for the website builder. This is entirely on your side — 10Web charges you at the workspace level, and you set your own pricing and billing cycles for end users. If you use a billing platform like WHMCS, Blesta, or HostBill, you can trigger WordPress provisioning and plugin installation automatically via their module/hook system when a customer completes a purchase.

Set generation limits, track usage, reset counters, and delete sites through a simple gateway API secured with your master API key.

What 10Web powers

The agentic AI builder receives the user’s prompt and creates a full multi-page site with real content, images, layout, and theme in under two minutes. Generation happens entirely on 10Web’s AI infrastructure — your server just makes one API call.

After generation, users continue building and refining their site with multiple editing tools — all running inside WordPress under your brand.

AI Editing — prompt-based edits powered by the agentic engine
Visual Editor — drag-and-drop
Code Editor — React and Tailwind
WordPress admin — full WP dashboard

All updates to the website builder are delivered automatically through the white-labeled website theme.

Same components, different order. The next section shows three integration approaches with step-by-step detail for each.

FUNNELS

Integration flows

Each approach rearranges the same building blocks into a different funnel shape.

APPROACH 1

I will capture the prompt in my UI

✍

Step 1

Capture prompt

Your landing page or dashboard

👤

Step 2

Signup / Pay

Before or after prompt

⚙

Step 3

Provision WP + license plugin

Via REST API

Store website_id

🔒

Step 4

Autologin

One-time token redirect

⚡

Step 5

Generation

POST/wvc/v1/create

Prompt timing is flexible: capture before signup (landing page) or after (dashboard) — same integration, different funnel placement.

APPROACH 2

I will redirect users to the website generation workflow

👤

Step 1

Signup / Pay

User creates account

⚙

Step 2

Provision WP + license plugin

Via REST API

Store website_id

🔒

Step 3

Autologin

One-time token redirect

✍

Step 4

10Web captures prompt

White-labeled editor in WP

inside editor in WP

⚡

Step 5

Generation

Handled by editor

APPROACH 3

I am using a hosting panel with WordPress management

👤

Step 1

Signup / Pay

User creates account

⚙

Step 2

Install WP + license plugin

Auto-bundled by panel

via WordPress Toolkit / Softaculous / similarStore website_id

🔒

Step 3

Panel logs user into WP

Built-in panel SSO

handled by hosting panel

✍

Step 4

10Web captures prompt

White-labeled editor in WP

inside editor in WP

⚡

Step 5

Generation

Handled by editor

DEEP DIVE

Detailed integration guides

Expand each approach for full step-by-step integration instructions, API calls, and code samples.

You own the prompt experience — on a landing page (before signup) or inside your customer dashboard (after signup). Either way, your code collects the prompt and calls the generation API.

Step 1

Capture prompt

Landing page or dashboard

Step 2

Signup / Pay

Before or after prompt

Step 3

Provision WP

Store website_id

Step 4

Autologin

Step 5

Generation

Prompt timing is flexible: capture before signup (landing page — persist the prompt through the auth redirect) or after (dashboard — no persistence needed, user is already authenticated).

Key characteristics

You call /wvc/v1/create explicitly with the user’s prompt
Full control over prompt UX — styling, validation, suggestions
If capturing before signup, persist user_prompt in session/local storage
If capturing after signup, gate by entitlement — only paying/trial users see the prompt
Pre-provision a warm pool of WordPress sites for instant response

API calls you’ll make

POSTwp-json/wp/v2/plugins — install license plugin
PUTwp-json/wp/v2/plugins/slug — activate plugin
POST/?rest_route=/wvc/v1/create — trigger generation
Gateway API calls for lifecycle management

Step-by-step integration

Prepare WordPress sites (warm pool)

Pre-provision WordPress instances with the license plugin installed and activated. Use the WP REST API Plugins endpoint to upload and install the plugin. Authenticate with Application Passwords (Basic Auth over HTTPS).

InstallPOST https://your-site.com/wp-json/wp/v2/plugins
Content-Disposition: attachment; filename="tenweb-license-plugin.zip"
Content-Type: application/zip

// Binary file body

Activate the plugin

Once uploaded, activate the license plugin. It will auto-install all required components (theme, builder plugins) and then delete itself.

ActivatePUT https://your-site.com/wp-json/wp/v2/plugins/tenweb-license-plugin

{
  "status": "active"
}

Create API user + Application Password

Create a dedicated WordPress user with administrator privileges and generate an Application Password for API authentication. Use this for all subsequent REST API calls. Learn more →

Capture the prompt

Present a prompt input on your landing page or inside your customer dashboard. The prompt is a single user_prompt string — a free-text description of the website the user wants (e.g. “A modern photography portfolio with gallery and contact page”). If capturing before signup, persist it in the session so it survives the auth redirect.

Payload shape{ "user_prompt": "string — free-text website description" }

Assign WP site & trigger generation

After signup/payment (or immediately if the user is already authenticated), assign a prepared WordPress site from your warm pool. Then call the generation endpoint with the prompt.

RequestPOST https://your-site.com/?rest_route=/wvc/v1/create

{
  "user_prompt": "A modern photography portfolio..."
}

⚠ Store the website_id returned in the response. You need it for limits, usage tracking, and lifecycle management.

Redirect with one-time login token

Generate a one-time login token and redirect the user into the WordPress editor. They land directly in the builder — no WP login screen. Implement using wp_set_auth_cookie() or a token-based autologin mechanism.

URL patternhttps://your-site.com/wp-login.php?token={one_time_token}&redirect_to=/wp-admin/admin.php?page=wvc-editor

Minimal code on your side. Provision WordPress, redirect the user — the white-labeled editor captures the prompt and triggers generation automatically.

Step 1

Signup / Pay

Step 2

Provision WP

Store website_id

Step 3

Autologin

Step 4

10Web captures prompt

inside editor in WP

Step 5

Generation

Key characteristics

No custom prompt UI needed — the editor handles it
No /wvc/v1/create call — the editor triggers generation
Install via REST API (or auto-installer as alternative)
Minimal code on your side

API calls you’ll make

POSTwp-json/wp/v2/plugins — install license plugin
PUTwp-json/wp/v2/plugins/slug — activate plugin
GET/wp-json/wvc/v1/website-id — fetch website_id after generation
Gateway API calls for lifecycle management

Step-by-step integration

User signs up or starts trial

Standard signup flow. The user creates an account and selects a hosting plan.

Provision WP + license plugin

Install WordPress and the license plugin via the WP REST API Plugins endpoint. Authenticate with Application Passwords. Alternatively, use your panel’s auto-installer (WordPress Toolkit, Softaculous, etc.) if available.

Install & activatePOST https://your-site.com/wp-json/wp/v2/plugins
// Upload tenweb-license-plugin.zip

PUT https://your-site.com/wp-json/wp/v2/plugins/tenweb-license-plugin
{ "status": "active" }

Redirect to WP onboarding with one-time login token

Generate a one-time login token and redirect the user to the onboarding URL. Implement using wp_set_auth_cookie() or a token-based autologin mechanism. The white-labeled editor will capture the prompt and trigger generation automatically.

URL patternhttps://your-site.com/wp-login.php?token={one_time_token}
  &redirect_to=/wp-admin/admin.php?page=wvc-editor&from_dashboard=1&onboarding=1

Fetch website_id after generation

Retrieve the website_id via the Get website ID endpoint once the user completes generation.

RequestGET https://your-site.com/wp-json/wvc/v1/website-id

⚠ Store the website_id in your database for lifecycle management.

For hosting panels with built-in WordPress management (cPanel, Plesk, DirectAdmin, CyberPanel, or similar). The plugin is bundled automatically when users install WordPress through the panel’s auto-installer — no REST API provisioning needed. This also applies if you are a reseller using WHM to provision cPanel accounts.

Step 1

Signup / Pay

Step 2

Install WP + plugin

via auto-installer

Step 3

Panel logs user into WP

built-in panel SSO

Step 4

10Web captures prompt

inside editor in WP

Step 5

Generation

Key characteristics

No custom prompt UI needed — the editor handles it
No /wvc/v1/create call — the editor triggers generation
No custom autologin needed — the panel’s built-in “Log in to WordPress” handles SSO
Auto-installer (WordPress Toolkit, Softaculous, Installatron) is the primary install method — no REST API provisioning
Least code of all three approaches

API calls you’ll make

Auto-installer plugin/theme set (WordPress Toolkit, Softaculous, or similar) — install license plugin (docs)
GET/wp-json/wvc/v1/website-id — fetch website_id after generation
Gateway API calls for lifecycle management

Step-by-step integration

Configure your auto-installer

Add the 10Web license plugin to your auto-installer’s plugin/theme set — WordPress Toolkit (Plesk), Softaculous (cPanel), Installatron, or your panel’s equivalent. When users install WordPress, the license plugin is included automatically.

User signs up — WordPress is ready

After signup and WordPress provisioning through the panel, the site is ready with the license plugin already active. No REST API calls needed for setup.

User logs into WordPress via the panel

The hosting panel’s built-in “Log in to WordPress” button handles authentication — no custom autologin needed. Configure the panel’s redirect target to land on the editor onboarding page if your panel supports custom redirect URLs.

Ideal redirect target/wp-admin/admin.php?page=wvc-editor&from_dashboard=1&onboarding=1

Tip: If your panel doesn’t support custom redirect targets, the user will land on the default wp-admin dashboard and can access the builder from there.

Fetch website_id after generation

Since you don’t call /wvc/v1/create yourself, retrieve the website_id via the Get website ID endpoint after the user completes generation.

RequestGET https://your-site.com/wp-json/wvc/v1/website-id

⚠ Store the website_id in your database for lifecycle management.

REFERENCE

API reference

Two API surfaces. The WordPress REST API runs on each site. The 10Web gateway manages all sites from one place.

Generate a website View in API docs →

Trigger AI website generation from a user prompt. Used in Approach 1 where you control the prompt capture.

RequestPOST https://your-site.com/?rest_route=/wvc/v1/create

{
  "user_prompt": "A modern photography portfolio with gallery and contact page"
}

Response{
  "success": true,
  "website_id": "ws_abc123def456",
  "status": "generating"
}

⚠ Store website_id in your database — you need it for limits, usage tracking, and lifecycle management.

Autologin (one-time token)

Redirect users directly into the editor without a WordPress login screen. Used in Approaches 1 and 2. In Approach 3, the hosting panel’s built-in SSO handles login.

Approach 1https://your-site.com/wp-login.php?token={one_time_token}
  &redirect_to=/wp-admin/admin.php?page=wvc-editor

Approach 2https://your-site.com/wp-login.php?token={one_time_token}
  &redirect_to=/wp-admin/admin.php?page=wvc-editor&from_dashboard=1&onboarding=1

Retrieve website ID View in API docs →

For Approaches 2 and 3 (where the editor captures the prompt), fetch the website_id after the user completes generation.

RequestGET https://your-site.com/wp-json/wvc/v1/website-id

// Response
{
  "website_id": "ws_abc123def456"
}

Site management gateway View in API docs →

Base URL: https://api.ai-website-builder.net

Authentication: x-api-key: {your_master_api_key}

Method	Endpoint	Description
GET	`/wvc/websites/custom-limitations`	Get current generation limits for a website
PUT	`/wvc/websites/custom-limitations`	Set custom generation limits for a website
PUT	`/wvc/generation-configs/default-website-limit/`	Set default generation limit for all new websites
GET	`/wvc/websites/usage`	Get generation usage for a website
POST	`/wvc/websites/reset-usage`	Reset usage counters for a website
DELETE	`/wvc/websites/delete`	Delete a website and free resources

FAQ

Frequently asked questions

Common integration questions from hosting providers.

Standard WordPress requirements — PHP 7.4+, MySQL 5.7+ or MariaDB 10.3+, and HTTPS. There are no special server-side dependencies because the AI generation happens on 10Web’s infrastructure. Your servers only host the resulting WordPress site.

Application Passwords (built into WordPress core since 5.6). Create a dedicated administrator user on each WordPress site and generate an Application Password for it. Use Basic Auth over HTTPS for all REST API calls. This is the simplest and most reliable method for server-to-server communication.

A warm pool is a set of pre-provisioned WordPress sites with the license plugin already installed and activated, ready to be assigned instantly when a user signs up. This eliminates the wait time for WordPress installation. The right pool size depends on your signup velocity — start with 10–20 and scale based on demand. This applies to Approaches 1 and 2; Approach 3 (hosting panel) provisions through the panel’s auto-installer on demand.

Both let the 10Web editor capture the prompt inside WordPress. The difference is how WordPress gets provisioned. In Approach 2, you install WordPress and the license plugin yourself via the REST API. In Approach 3, the hosting panel’s auto-installer (WordPress Toolkit, Softaculous, Installatron, etc.) handles installation automatically — you just configure the plugin/theme set once. Choose Approach 3 if your customers interact directly with the panel (cPanel, Plesk, DirectAdmin, CyberPanel). Choose Approach 2 if the panel runs behind your own custom dashboard.

Use the gateway API to set per-website generation limits (/wvc/websites/custom-limitations) and a default limit for all new websites (/wvc/generation-configs/default-website-limit/). Track usage with the usage endpoint and reset counters when billing cycles renew. This lets you enforce tiered plans where higher-paying users get more generations.

Use the gateway API’s usage endpoint (/wvc/websites/usage) to query generation counts per website. Store the website_id for each customer in your database and poll usage periodically, or query on demand for billing reconciliation.

Set the website’s generation limit to zero via the gateway API to block new generations while keeping the existing site live, or call the delete endpoint (/wvc/websites/delete) to remove it entirely. The WordPress site itself remains a standard site on your servers regardless — the gateway API only manages the AI builder layer.

Yes. Use your 10Web workspace API key to provision test sites during development. These use the same generation pipeline as production, so you can validate the full flow end-to-end. There is no separate sandbox API — you test against the real system.

For Approaches 1 and 2, create a custom WordPress endpoint or mu-plugin that accepts a one-time token, validates it, calls wp_set_auth_cookie() to authenticate the user, and redirects to the editor URL. Generate a unique token on your backend, store it with a short expiry, and pass it as a query parameter in the redirect URL. The token should be single-use and time-limited for security. For Approach 3, you typically don’t need custom autologin — the hosting panel’s built-in “Log in to WordPress” button handles authentication natively.