For Agents
Programmatically execute API action. Covers 1 operations.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WHMCS Client Management 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%2Fwhmcs.com%2Fwhmcs" | shStep 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%2Fwhmcs.com%2Fwhmcs" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with WHMCS Client Management API.
Execute API Action
Manage payments data programmatically
Integrate WHMCS Client Management API into automated workflows
Query and filter WHMCS Client Management API records by parameters
GET STARTED
Use for: I need to execute API action, Find available payments operations, Get the current status of WHMCS Client Management API resources, List all records from WHMCS Client Management API
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
The WHMCS API allows you to perform operations and actions within WHMCS from external third party and custom code. This includes managing clients, domains, invoices, tickets, orders, and more. All API requests are made via POST to the api.php endpoint with authentication credentials and action parameters. The API exposes 1 endpoints.
Monitor WHMCS Client Management API operational status and events
Patterns agents use WHMCS Client Management API for, with concrete tasks.
★ Payments Operations
Use the WHMCS Client Management API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including execute API action.
Call POST /api.php to execute API action
Data Retrieval and Monitoring
Query WHMCS Client Management API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary WHMCS Client Management API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call WHMCS Client Management API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'execute API action', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — the whmcs api allows you to perform operations and actions within whmcs from external third party and custom code.
METHOD
PATH
DESCRIPTION
/api.php
Execute API Action
/api.php
Execute API Action
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the WHMCS Client Management API by hand means pointing at your own WHMCS installation URL, POSTing form actions to api.php, and parsing its responses yourself. Through Jentic you install once, import the WHMCS Client Management API from the API Directory, store the connection details once, and your agent calls it.
Permission scoping
This API exposes a single api.php action endpoint, so scope the agent to the operations it needs, such as reading client records, rather than to one client. You choose the operations it may call, so write or delete actions are not included unless you add them.
Credential isolation
Your WHMCS connection details are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'run a WHMCS client action', and Jentic returns the matching WHMCS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Specific to using WHMCS Client Management API through Jentic.
What authentication does the WHMCS Client Management API use?
The WHMCS Client Management API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I execute API action with the WHMCS Client Management API?
Yes. Use the POST /api.php endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the WHMCS Client Management API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I execute API action through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'execute API action'. Jentic returns the matching WHMCS Client Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the WHMCS Client Management API have?
The WHMCS Client Management API exposes 1 endpoints covering api.php operations.
Can I limit what my agent is allowed to do with the WHMCS Client Management API?
Yes. Because you run Jentic One yourself, your own rules decide which WHMCS operations and credentials your agent may use. The WHMCS Client Management API is exposed through a single api.php action endpoint, so you scope the agent to only the actions it needs, such as reading client records, rather than granting it everything. Write or delete actions are not available to the agent unless you explicitly add them.