LemonX Developers · Cloud Gateway

A secure cloud layer for WordPress AI growth workflows.

LemonX Cloud Gateway connects WordPress websites with the cloud-powered services required to run advanced AI, licensing, product entitlement, usage tracking, secure updates and premium LemonX workflows.

It gives developers a controlled bridge between a self-hosted WordPress site and LemonX cloud services — without forcing every sensitive operation to live directly inside the WordPress database.

Explore Gateway Architecture View Authentication See API Examples

Site-bound · License-aware · Usage-tracked · Built for secure WordPress AI workflows

What is LemonX Cloud Gateway?

LemonX Cloud Gateway is the secure service layer that helps LemonX-powered WordPress sites communicate with LemonX cloud infrastructure. It can support license verification, plan entitlements, AI gateway routing, usage quotas, secure update checks, premium feature access, agency site management and enterprise-level controls.

For developers, Cloud Gateway provides a predictable way to connect local WordPress functionality with cloud-based capabilities while preserving permission checks, site identity, product access and usage visibility.

Connect local WordPress to cloud services

Cloud Gateway bridges your WordPress installation with LemonX services for licensing, entitlements, AI routing and advanced product capabilities.

Keep feature access controlled

Product access can be checked against license status, plan level, site identity and enabled modules.

Track usage across products

AI calls, translation volume, indexing requests, MCP actions, report generation and cloud tasks can be measured and controlled.

Support scalable product workflows

Agencies, developers and enterprise teams can manage advanced workflows across one site or many sites.

Why it matters

Advanced AI workflows need more than local plugin settings.

A normal WordPress plugin can store options, render admin pages and run local PHP code. But an AI-powered growth suite needs more: license validation, usage controls, AI provider routing, plan-based entitlements, secure update delivery, cloud-based processing, multi-site account awareness and reliable service orchestration.

Cloud Gateway provides that missing layer.

Without Cloud Gateway

License state may be hard to verify.
Advanced features are difficult to control across plans.
Usage tracking becomes fragmented.
AI provider routing must be handled locally.
Agencies cannot easily manage multiple sites.
Secure updates and premium access become harder to enforce.
Enterprise workflows require too much custom infrastructure.

With LemonX Cloud Gateway

Licenses can be verified securely.
Product entitlements can be checked before features run.
Usage can be measured across modules.
AI and translation requests can be routed through controlled services.
Agencies can manage multi-site workflows.
Developers can build predictable cloud-connected integrations.
Enterprise teams can apply stronger governance and access control.

Architecture

How Cloud Gateway fits into the LemonX ecosystem.

LemonX Cloud Gateway sits between the local WordPress site and LemonX cloud services. It does not replace WordPress. It extends WordPress with secure, plan-aware, cloud-connected capabilities.

Architecture Flow

WordPress Site
LemonX Plugins
Local Authentication & Permissions
Cloud Gateway Request
Site Identity Verification
License & Entitlement Check
Usage & Quota Check
Cloud Service Execution
Response Back to WordPress
Local Result, Log or Task Update

Core Components

Local WordPress Plugin Layer

Runs inside WordPress and handles local admin UI, settings, content workflows, permissions, REST API, MCP tools and module logic.

Authentication Layer

Verifies the local user, site token, API key, MCP session or gateway credential before requests are made.

Site Identity Layer

Confirms which WordPress site is communicating with the gateway and whether it is authorized.

License & Entitlement Layer

Checks whether the site has access to requested products and premium features.

Usage Layer

Records and limits AI calls, translation usage, indexing actions, cloud operations and other measured events.

Cloud Service Layer

Provides advanced LemonX services such as AI routing, secure update validation, premium processing and enterprise workflows.

Response & Logging Layer

Returns structured responses to WordPress and records important actions for visibility, debugging and auditability.

Responsibilities

What Cloud Gateway can handle.

Responsibility 1

License Verification

Confirm whether a site can use LemonX premium features.

Cloud Gateway can verify whether a WordPress site has a valid LemonX license, whether the license is active, whether the site is bound to the license and whether the current plan allows the requested feature.

Example Checks

License key validity
License activation status
Site binding status
Plan level
Product access
Expiration date
Renewal state
Agency seat allocation
Enterprise account status

Use Cases

Activate LemonX Pro.
Check whether AEO Pro features are available.
Validate agency site allocations.
Disable premium features when a license expires.
Show license state inside WordPress admin.
Prevent unauthorized use of paid features.

Responsibility 2

Product Entitlements

Decide which features are available for each site.

Entitlements define what a site, license, plan or account is allowed to use. Cloud Gateway can help LemonX modules determine whether specific features should be enabled.

Example Checks

AEO Pro enabled
Code Pro enabled
Verto Pro enabled
MCP Pro enabled
Advanced reports enabled
AI gateway access enabled
Translation queue access enabled
Agency multi-site features enabled
Enterprise policy controls enabled
Priority support enabled

Use Cases

Show or hide product features.
Enable advanced AEO reports.
Control translation volume by plan.
Limit MCP apply tools to Pro plans.
Unlock agency dashboards.
Enable enterprise security controls.

Responsibility 3

Usage & Quota Tracking

Measure product usage across AI, translation and automation workflows.

Cloud Gateway can record and return usage data so users and developers understand how product limits are being consumed.

Example Checks

AI generation requests
AI tokens or credits
Translation characters
Translation tasks
Indexing submissions
MCP tool calls
MCP apply actions
OCR processing
Report generation
Cloud API calls
Webhook deliveries
Background tasks

Use Cases

Show remaining usage in the WordPress dashboard.
Warn users before reaching quota.
Prevent runaway automation.
Help agencies monitor client usage.
Support usage-based billing or plan limits.
Debug unusually high AI consumption.

Responsibility 4

AI Gateway Routing

Route AI requests through controlled provider logic.

Cloud Gateway can help route AI requests to supported models and providers based on product context, plan level, usage limits, fallback rules and availability.

Example Checks

Use a fast model for drafts.
Use a stronger model for final content.
Use a lower-cost provider for bulk tasks.
Use fallback provider when one fails.
Block unsupported providers by plan.
Route enterprise requests through approved providers.
Apply safety or formatting policies before response.

Use Cases

Centralize model management.
Reduce local API key complexity.
Apply provider fallback chains.
Control AI costs.
Offer plan-based model access.
Provide enterprise-approved AI routes.

Responsibility 5

Secure Updates

Support trusted plugin and theme update workflows.

Cloud Gateway can help verify update eligibility, deliver premium update metadata and ensure that licensed users receive appropriate plugin and theme updates.

Example Checks

Product license status
Installed version
Latest available version
Plan entitlement
Update channel
Security release availability
Beta access
Theme update eligibility

Use Cases

Deliver LemonX Pro updates.
Provide premium feature patches.
Support beta channels for selected users.
Control agency update access.
Verify secure update metadata.
Reduce unauthorized distribution risk.

Responsibility 6

Agency Multi-Site Management

Help agencies manage many client websites.

Agencies often manage multiple WordPress sites. Cloud Gateway can provide a shared account layer that tracks site activations, licenses, usage, entitlements and product access across client properties.

Example Checks

Account sites
License seats
Product activation status
Site health state
Usage by site
Client-level reports
Entitlement by site
Gateway connection status
Plan limits

Use Cases

Activate LemonX across many client sites.
Monitor usage across accounts.
Prepare client reports.
Manage agency seats.
Detect disconnected sites.
Control which sites can use premium modules.

Responsibility 7

Enterprise Governance

Support stricter security, policy and control requirements.

Enterprise teams may need stronger controls over AI providers, usage, permissions, cloud connectivity and auditability. Cloud Gateway can support enterprise governance features that go beyond normal plugin settings.

Example Checks

Approved AI providers
Team-level entitlements
Usage caps
Policy enforcement
Audit export
SLA-aware routing
Private cloud options
Custom account rules
Advanced support access

Use Cases

Limit AI provider usage to approved services.
Apply organization-level content rules.
Manage multiple business units.
Export audit data.
Support compliance workflows.
Create enterprise-grade WordPress AI governance.

Request lifecycle

What happens when WordPress calls Cloud Gateway?

Local workflow starts

A LemonX module initiates a cloud-connected action such as license verification, AI routing, usage sync or entitlement check.

Local permission check runs

WordPress verifies the local user, capability, nonce, API key, MCP context or background task permission.

Gateway request is signed

The plugin prepares a request with site identity, product context, feature request and authentication data.

Gateway verifies site identity

Cloud Gateway confirms that the request comes from a recognized and authorized site.

License and entitlement checks run

The gateway verifies whether the site, plan and product are allowed to use the requested feature.

Usage and quota checks run

The gateway checks whether the requested action is within allowed usage limits.

Cloud action executes

The requested cloud-connected operation is performed.

Structured response returns

The gateway returns success, data, task ID, usage update or error information.

WordPress stores result or log

The local plugin updates the admin UI, task status, report, usage panel or activity log.

Gateway API

Example gateway-facing resources.

The following endpoints are developer-facing examples that describe the type of resources Cloud Gateway may expose or support. Final endpoint names should match the active LemonX implementation.

License Endpoints

POST /gateway/v1/license/activate
POST /gateway/v1/license/deactivate
GET  /gateway/v1/license/status
POST /gateway/v1/license/refresh

Entitlement Endpoints

GET  /gateway/v1/entitlements
POST /gateway/v1/entitlements/check
GET  /gateway/v1/products
GET  /gateway/v1/features

Usage Endpoints

POST /gateway/v1/usage/record
GET  /gateway/v1/usage/summary
GET  /gateway/v1/usage/limits
GET  /gateway/v1/usage/history

AI Gateway Endpoints

POST /gateway/v1/ai/generate
POST /gateway/v1/ai/route
GET  /gateway/v1/ai/providers
GET  /gateway/v1/ai/models

Site Endpoints

POST /gateway/v1/sites/register
GET  /gateway/v1/sites/status
POST /gateway/v1/sites/sync
POST /gateway/v1/sites/disconnect

Update Endpoints

GET  /gateway/v1/updates/check
GET  /gateway/v1/updates/package
POST /gateway/v1/updates/verify

Agency Endpoints

GET  /gateway/v1/agency/sites
GET  /gateway/v1/agency/usage
GET  /gateway/v1/agency/entitlements
GET  /gateway/v1/agency/reports

Local API

How WordPress can expose Cloud Gateway status locally.

Developers may also access gateway-related state through LemonX local REST API endpoints inside WordPress. These endpoints can help admin dashboards, agency tools and integrations inspect gateway status without calling the cloud directly.

Example Local Endpoints

GET  /wp-json/lemonx/v1/pro/cloud/status
GET  /wp-json/lemonx/v1/pro/license
GET  /wp-json/lemonx/v1/pro/entitlements
GET  /wp-json/lemonx/v1/pro/usage
POST /wp-json/lemonx/v1/pro/license/activate
POST /wp-json/lemonx/v1/pro/license/deactivate
POST /wp-json/lemonx/v1/pro/cloud/sync

Use Cases

Display license status in WordPress admin.
Show remaining AI or translation usage.
Check whether a Pro feature is available.
Debug Cloud Gateway connectivity.
Refresh entitlements after plan changes.
Build agency dashboards from local site data.

Authentication

Cloud Gateway requests must verify both site and account.

Cloud Gateway authentication should confirm the local site identity, account/license state and request integrity. The gateway should not rely on user-provided data alone.

Recommended Authentication Signals

Site IDLicense keyGateway tokenRequest signatureTimestampProduct IDFeature IDPlugin versionDomain or site URLAccount IDPlan entitlementUsage context

Recommended Controls

Use HTTPS for every gateway request.
Sign sensitive requests.
Include timestamp to reduce replay risk.
Bind tokens to site identity where possible.
Rotate tokens when needed.
Do not expose gateway tokens to frontend JavaScript.
Log failed authentication attempts.
Verify entitlements before executing premium actions.

Entitlement pattern

Check access before running premium workflows.

Example Flow

User starts a premium LemonX action.
WordPress checks local permission.
LemonX checks whether the product module is active.
WordPress requests entitlement state from Cloud Gateway.
Gateway validates license, plan and site identity.
Gateway returns allowed or denied.
WordPress either runs the action or shows an upgrade / access message.
Result is logged where appropriate.

Example Response: Allowed

{
  "success": true,
  "entitlement": {
    "feature": "aeo.ai_citation_tracking",
    "allowed": true,
    "plan": "agency",
    "expires_at": "2027-07-04T00:00:00Z"
  }
}

Example Response: Denied

{
  "success": false,
  "error": {
    "code": "entitlement_required",
    "message": "This feature requires LemonX AEO Pro.",
    "required_plan": "pro"
  }
}

Usage tracking

Track usage without slowing down workflows.

Usage tracking should be reliable, but it should not make the user experience slow or fragile. Some usage events can be recorded synchronously, while others can be queued and synced in batches.

Example Usage Event

{
  "event": "ai.generation.completed",
  "site_id": "site_123",
  "product": "code",
  "feature": "page_generation",
  "model": "premium-model",
  "units": 1,
  "tokens_input": 2400,
  "tokens_output": 1800,
  "timestamp": "2026-07-04T10:00:00Z"
}

Recommended Usage Categories

AI generationTranslationOCR processingAEO analysisIndexing submissionsMCP tool callsMCP apply actionsReport generationCloud API requestsSecure update checks

Best Practices

Batch low-risk usage records.
Record high-cost actions immediately.
Show usage to administrators.
Warn before limits are reached.
Avoid duplicate usage records.
Store request IDs for debugging.
Allow graceful failure for non-critical sync events.

AI routing

Route AI requests through product-aware logic.

Different LemonX workflows may need different AI models. A bulk translation task, an AEO analysis, a page generation request and an MCP content edit may not require the same provider, speed, cost or quality level.

Cloud Gateway can support product-aware AI routing.

Example Routing Rules

AEO analysis uses a reasoning-optimized model.
Bulk draft generation uses a cost-efficient model.
Final landing page generation uses a higher-quality model.
Translation uses language-optimized providers.
Enterprise accounts use approved providers only.
If one provider fails, use a configured fallback.
If quota is low, block or downgrade selected workflows.

Developer Use Cases

Centralize AI model selection.
Avoid exposing provider keys locally.
Apply cost-control rules.
Support fallback providers.
Enforce enterprise provider policies.
Monitor AI usage by product.

Secure updates

Premium software updates need trusted delivery.

LemonX Pro and premium product modules may require secure update checks. Cloud Gateway can help verify whether a site is allowed to receive a specific update package or release channel.

Update Channels

Stable
Security release
Beta
Agency preview
Enterprise controlled rollout

Update Checks

Current installed version
Product license status
Site authorization
Plan entitlement
Release channel access
Compatibility requirements
Update package signature
Security release priority

Use Cases

Deliver product updates to licensed users.
Offer beta access to selected accounts.
Allow agencies to test updates before broad rollout.
Prioritize security releases.
Prevent unauthorized premium downloads.
Support enterprise update control.

Agency workflows

Cloud Gateway helps agencies manage many WordPress sites.

Use Case 1: Multi-site license management

Agencies can connect multiple client sites under one account and monitor activation status, plan access and product availability.

Use Case 2: Usage visibility by client

Agencies can understand which sites are using the most AI, translation, indexing or MCP activity.

Use Case 3: Client reporting

Cloud Gateway can support centralized report access, helping agencies show SEO, translation, MCP and growth activity.

Use Case 4: Seat allocation

Agencies can allocate license seats or product access across client websites.

Use Case 5: Bulk entitlement refresh

When an agency plan changes, connected sites can refresh entitlements through Cloud Gateway.

Use Case 6: Site health monitoring

Agencies can detect disconnected sites, expired licenses, failed syncs or usage warnings.

Enterprise workflows

Cloud Gateway can support governance for larger teams.

Use Case 1: Approved AI provider policy

Enterprise accounts can define which AI providers are allowed.

Use Case 2: Usage caps by team or site

Organizations can limit AI, translation or cloud usage by department, site or project.

Use Case 3: Audit export

Enterprise teams can export logs for security review and compliance workflows.

Use Case 4: Private or restricted routing

Certain plans may route AI or cloud workflows through approved infrastructure.

Use Case 5: Central entitlement control

Administrators can enable or disable product features across multiple properties.

Use Case 6: Priority support and SLA context

Gateway can help identify plan level, support priority and service context.

Error handling

Cloud Gateway responses should be clear and actionable.

Error Code	Meaning	Recommended Action
gateway_unavailable	Gateway cannot be reached	Retry later or check connection
invalid_site	Site identity is missing or invalid	Reconnect site
license_invalid	License key is invalid	Check license
license_expired	License is expired	Renew license
entitlement_required	Feature is not included in plan	Upgrade plan
quota_exceeded	Usage limit reached	Upgrade or wait for reset
signature_invalid	Request signature failed	Check token and request signing
token_expired	Gateway token expired	Refresh token
product_inactive	Required product is inactive	Enable product
provider_unavailable	AI provider route failed	Retry or use fallback
update_not_allowed	Site cannot access update	Check license and channel
rate_limited	Too many requests	Reduce request frequency

Best Practice: Error messages should help developers fix the problem without exposing sensitive information.

Health checks

Monitor Cloud Gateway status from WordPress.

Developers and site owners need visibility into whether Cloud Gateway is connected and functioning. Health checks help diagnose licensing, entitlement, update, usage and AI gateway issues.

Recommended Health Fields

Gateway connectedLast successful syncLicense statusEntitlement statusUsage sync statusCloud token statusPlugin versionSite identity statusProduct activation stateLast errorRecommended action

Example Health Response

{
  "success": true,
  "gateway": {
    "connected": true,
    "last_sync": "2026-07-04T10:00:00Z",
    "license": "active",
    "entitlements": "synced",
    "usage": "synced",
    "cloud_token": "valid"
  },
  "products": {
    "aeo": "active",
    "code": "active",
    "verto": "active",
    "mcp": "active",
    "pro": "active"
  }
}

Best practices

Build Cloud Gateway workflows securely.

Best Practice 1: Never expose gateway tokens in frontend code

Gateway credentials should only be used server-side.

Best Practice 2: Verify site identity

Do not rely only on domain names. Use site-bound identity where possible.

Best Practice 3: Sign sensitive requests

Use request signing for license, entitlement, usage and secure update actions.

Best Practice 4: Check entitlements before work starts

Avoid running expensive tasks before verifying access.

Best Practice 5: Track usage carefully

Prevent runaway automation and unexpected costs.

Best Practice 6: Use retry logic wisely

Retry transient gateway errors, but avoid infinite loops.

Best Practice 7: Fail gracefully

If a non-critical gateway sync fails, keep the admin UI usable and show a clear warning.

Best Practice 8: Log request IDs

Use request IDs to debug issues across WordPress and cloud services.

Best Practice 9: Separate staging and production

Staging sites should use separate identities, usage records and update channels.

Best Practice 10: Respect privacy

Only send data required for the requested cloud workflow.

Privacy

Send only what the cloud service needs.

Cloud Gateway should be designed around data minimization. Some workflows require only license and site metadata. Others may require AI prompt data, translation content or usage details. Developers should understand what each workflow sends.

Data That May Be Needed

Site ID
Domain
Plugin version
License key hash or token
Product activation state
Feature request
Usage event
Task status
AI prompt or content when using cloud AI
Translation text when using cloud translation
Error context for debugging

Data That Should Not Be Sent Unless Required

Raw database dumps
Unrelated user data
Payment details stored locally
Private API keys
Passwords
Sensitive personal data
Unrelated customer records

Developer Recommendation: For each gateway-connected workflow, document what data is sent, why it is needed and how it is protected.

Comparison

When should a workflow use Cloud Gateway?

Local-only workflow

Best when the task can be completed entirely inside WordPress.

Admin UI rendering
Local settings storage
Simple content edits
Local template selection
Local hook execution
Basic read-only actions

Cloud Gateway workflow

Best when the task requires account, license, cloud, usage or advanced service context.

License verification
Product entitlement checks
AI gateway routing
Usage tracking
Secure updates
Premium reports
Agency site management
Enterprise policies

Summary: Use WordPress locally when local execution is enough. Use Cloud Gateway when the workflow needs secure cloud-connected context.

Examples

Common Cloud Gateway developer workflows.

Example 1: Check license before showing a premium feature

Flow

Local admin page loads.
WordPress checks user permission.
Plugin requests entitlement state.
Cloud Gateway confirms plan access.
UI shows or hides premium feature.

Result: Users only see features available to their plan.

Example 2: Record usage after AI page generation

Flow

User generates a landing page.
LemonX Code completes generation.
Usage event is created.
Cloud Gateway records AI usage.
Dashboard updates remaining quota.

Result: AI usage stays visible and controlled.

Example 3: Route translation through approved provider

Flow

Verto queues translation.
Cloud Gateway checks plan and language.
Gateway selects provider route.
Translation task runs.
Usage is recorded.

Result: Translation workflows follow plan, language and provider rules.

Example 4: Verify update eligibility

Flow

WordPress checks for LemonX Pro update.
Cloud Gateway verifies license and channel.
Gateway returns update metadata.
WordPress installs update through normal update flow.

Result: Premium updates are delivered only to eligible sites.

Example 5: Agency account sync

Flow

Agency connects multiple client sites.
Each site syncs license and health data.
Cloud Gateway groups sites under agency account.
Agency dashboard shows status and usage.

Result: Agencies can monitor client sites from one account layer.

Build cloud-aware WordPress AI workflows.

Use LemonX Cloud Gateway to connect local WordPress functionality with secure licensing, AI routing, usage tracking, premium access and agency-ready cloud services.

View API Examples Read Authentication Guide

Cloud Gateway FAQ

What is LemonX Cloud Gateway?

Cloud Gateway is the cloud-connected layer that supports licensing, entitlements, usage tracking, AI routing, secure updates and premium LemonX workflows.

Is Cloud Gateway required for every LemonX feature?

No. Many local WordPress workflows can run without cloud services. Cloud Gateway is mainly used for license, Pro, cloud-connected, usage-tracked and premium workflows.

Does Cloud Gateway replace WordPress?

No. WordPress remains the core site system. Cloud Gateway extends LemonX with secure cloud-connected capabilities.

Can Cloud Gateway route AI requests?

Yes. It can support AI provider routing, fallback logic, plan-based model access and usage tracking where enabled.

Does Cloud Gateway store my website content?

It should only process or receive the data required for a specific cloud-connected workflow. Developers should document what data is sent for each feature.

What happens if Cloud Gateway is unavailable?

Local features should continue where possible. Cloud-dependent features may show a clear error, retry later or fall back based on configuration.

Can agencies use Cloud Gateway?

Yes. Agencies can use Cloud Gateway to manage license seats, site activations, usage, reports and product entitlements across multiple client sites.

Can enterprises control AI provider usage?

Enterprise workflows can use Cloud Gateway to enforce approved provider policies, usage caps and governance rules where supported.

How does Cloud Gateway relate to LemonX Pro?

LemonX Pro is the product layer that can unlock licensing, entitlements, cloud-connected features and premium access. Cloud Gateway is the service layer that can power those capabilities.

Can developers access gateway status locally?

Yes. Local LemonX REST API endpoints can expose license, entitlement, usage and cloud status to authorized users and integrations.

Cloud Gateway is the bridge between WordPress control and cloud-powered AI capability.

Keep WordPress local where it should be local. Use Cloud Gateway where licensing, entitlements, usage, AI routing, secure updates and multi-site workflows need a trusted cloud layer.

Continue to Webhooks View REST API Explore Examples