Install Jentic One Beta

Connect the 1ClickWebsite API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 1ClickWebsite API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F1clickwebsite.ai%2F1clickwebsite" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F1clickwebsite.ai%2F1clickwebsite" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with 1ClickWebsite API.

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

GET STARTED

Start building with 1ClickWebsite API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use 1ClickWebsite API for, with concrete tasks.

★ 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.

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.

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.

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

22 endpoints — the 1clickwebsite api provisions complete websites from a template, generates lead gen mini-sites in batches, and routes white-label agency site requests.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using 1ClickWebsite API through Jentic.

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.

1ClickWebsite API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent Managementbearer, basic22 EndpointsREST

For 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.

Use for: Create a new website from a template, Check whether a site build has finished, Generate a batch of Lead Gen mini-sites, List the available site templates

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

51%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the 1ClickWebsite API to your agent

Capabilities

Start building with 1ClickWebsite API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

1ClickWebsite API

Jentic AI Readiness Score

1ClickWebsite API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness