canonical: https://jentic.com/apis/1clickwebsite.ai/1clickwebsite

# 1ClickWebsite API

The 1ClickWebsite API provisions complete websites from a template, generates Lead Gen mini-sites in batches, and routes white-label agency site requests. Once a site is built, a second set of endpoints edits the generated WordPress site directly: reading and updating rendered field values, validating changes, clearing the page cache, and updating per-post SEO. Platform endpoints authenticate with a 1ClickWebsite bearer key, while the site-editing endpoints run against the generated site using a WordPress username and application password.

## For AI agents

Provision websites and Lead Gen mini-sites, route agency site requests, and edit the generated WordPress site's fields and SEO for AI agents.

## Scope

Does not handle domain registration, hosting billing, or email delivery. Use for generating and editing 1ClickWebsite sites only.

## Capabilities

- Provision a complete website from a chosen template and poll its build status
- Generate Lead Gen mini-sites in batches and update batch settings before processing
- Submit and track white-label agency site requests
- Read and update rendered field values on a generated site and validate the change first
- Update per-post SEO and clear the page cache on a built WordPress site

## Use cases

### AI site-building agent

An AI agent that builds a landing site on request needs to provision and then confirm the build without a human watching the queue. Through Jentic the agent searches for 'create a website from a template', loads the matching 1ClickWebsite operation with its input schema, and submits the request with the bearer key injected at call time. It then polls the build-status operation until the site is ready and reports the URL.

Example prompt: Call POST `/api/provision` with a template, then poll GET `/api/provision/{siteId}` until the build reports complete

### Lead Gen mini-site batches

A marketing team spinning up many prospect-specific mini-sites submits them as a batch rather than one at a time. 1ClickWebsite accepts a batch, lets the team adjust its settings while it is queued, and processes it on confirmation. An agent can create the batch, patch its settings, and confirm it is queued for generation.

Example prompt: Create a batch with POST `/api/lead-gen/batches`, adjust it with PATCH `/api/lead-gen/batches/{batchId}`, then confirm processing

### Post-build content and SEO editing

After a site is generated, an agent maintaining it edits the content and search metadata directly on the WordPress site. 1ClickWebsite exposes the active field schema and current values, a validation step, and a per-post SEO update, so changes can be checked before they are written. The page cache can be cleared so edits appear immediately.

Example prompt: Read current values with GET `/wp-json/ocf/v1/state`, validate an update with POST `/wp-json/ocf/v1/validate`, then apply it

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/provision` | Create a site from a template |
| GET | `/api/provision/{siteId}` | Check a site build status |
| GET | `/api/templates` | List site templates |
| POST | `/api/lead-gen/batches` | Create a Lead Gen batch |
| POST | `/api/agency/v1/site-requests` | Create an agency site request |
| GET | `/wp-json/ocf/v1/state` | Read current field values |
| POST | `/wp-json/ocf/v1/state` | Update rendered field values |
| PATCH | `/wp-json/ocf/v1/posts/{postId}/seo` | Update post SEO |

## Key resources

- **Site creation** — Templates, provisioning, and build-status checks for full V2 websites
- **Lead Gen** — Batch creation, settings, and processing for Lead Gen mini-sites
- **Site editing** — OCF field schema, state, validation, cache clearing, and per-post SEO on the generated WordPress site

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 35 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/1clickwebsite.ai/1clickwebsite/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring 1ClickWebsite by hand means handling two auth schemes at once: a bearer API key for the platform endpoints and a WordPress username and application password for the site-editing endpoints, each on its own host. Through Jentic you install once, import 1ClickWebsite from the API Directory, store both credentials once, and your agent calls it.
- **Permission scoping:** The platform operations sit under /api paths and the site-editing operations under /wp-json, and each site, batch, and post id travels in the URL path, so a rule can pin your agent to the operations it needs. You choose which it may call, so cache-clearing or agency routes are not included unless you add them.
- **Credential handling:** Your 1ClickWebsite bearer key and the WordPress application password are stored once, encrypted, by your own Jentic One instance and attached at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a website from a template' or 'update post SEO', and Jentic returns the matching 1ClickWebsite operation with its input schema so the agent calls the right endpoint with the correct credential.

## Related APIs

- **Webflow Data API** — Visual website builder and CMS where sites are designed and managed through a hosted platform
- **Shopify REST Admin API** — Adds storefront, catalog, and checkout to a generated marketing site
- **SEMrush API** — Keyword and SEO research to inform the per-post SEO fields a 1ClickWebsite site exposes

## FAQ

### What authentication does the 1ClickWebsite API use?

It uses two schemes per its OpenAPI spec. Platform endpoints use bearer authentication with a 1ClickWebsite API key (account keys begin with lgen_ and white-label agency keys begin with 1cw_agency_). The site-editing endpoints under /wp-json use HTTP basic authentication with a WordPress username and application password. Through Jentic both credentials are held by your own instance and attached per call.

### Can I create a website and check when it is ready with the 1ClickWebsite API?

Yes. POST `/api/provision` creates a site from a template and returns a siteId, and GET `/api/provision/{siteId}` reports the build status so an agent can poll until the site is complete. GET `/api/templates` lists the templates you can build from.

### What are the rate limits for the 1ClickWebsite API?

The OpenAPI spec does not declare numeric rate limits. Check the 1ClickWebsite documentation for the current per-plan limits before submitting large Lead Gen batches, and treat site provisioning as an asynchronous job rather than a tight polling loop.

### Is there a 1ClickWebsite MCP server?

You do not need an MCP server to give your agent 1ClickWebsite. Jentic connects it directly from the API Directory: import it, store your bearer key and WordPress credentials once, and your agent calls the site-creation and editing operations it needs.

### How do I update a post's SEO through Jentic?

Search Jentic for 'update post SEO on a generated site', load the PATCH `/wp-json/ocf/v1/posts/{postId}/seo` operation, and execute it with the postId and the new SEO fields. The WordPress basic credentials are attached by your instance. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the 1ClickWebsite API?

Yes. Write a rule that allows only the operations a task needs, such as creating a site and checking its build, so the destructive and agency routes stay out of reach unless you add them. Because site creation and WordPress editing use separate credentials, you can grant one without the other, and every call the agent makes is logged.