Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SimpliVPNAPI, 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%2Fsimplivpn.net%2Fsimplivpn" | 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%2Fsimplivpn.net%2Fsimplivpn" | 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 SimpliVPNAPI API.
GetServers
Register
Login
EnableUser
DisableUser
GET STARTED
UsernameAvailable
Patterns agents use SimpliVPNAPI API for, with concrete tasks.
★ Developer Tools Operations
Use the SimpliVPNAPI to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including getservers, getserversummaries, register.
Call GET /servers to getservers
Automated Disable User Management
Automate disable user operations by combining multiple SimpliVPNAPI endpoints. Agents can getserversummaries and then register in a single workflow.
Call GET /server-summaries to getserversummaries, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SimpliVPNAPI 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 apiKey tokens manually.
Search Jentic for 'getservers', load the operation schema, and execute with Jentic-managed credentials
7 endpoints — simplivpn.
METHOD
PATH
DESCRIPTION
/servers
GetServers
/server-summaries
GetServerSummaries
/register
Register
/login
Login
/enable-user
EnableUser
/disable-user
DisableUser
/username-available
UsernameAvailable
/servers
GetServers
/server-summaries
GetServerSummaries
/register
Register
/login
Login
/enable-user
EnableUser
/disable-user
DisableUser
/username-available
UsernameAvailable
What agents get from Jentic-routed access to this vendor.
Setup
Wiring SimpliVPN by hand means learning that its key rides in the Authorization header and carrying it across the server, registration, and user enable and disable calls yourself. Through Jentic you install once, import SimpliVPN from the API Directory, store the key once, and your agent calls it.
Permission scoping
SimpliVPN carries its targets in the request body rather than as a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as listing servers or checking username availability, and leave out account changes like disabling a user unless you add them.
Credential isolation
Your SimpliVPN API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list VPN servers' or 'check if a username is available', and Jentic returns the matching SimpliVPN 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.
Specific to using SimpliVPNAPI API through Jentic.
What authentication does the SimpliVPNAPI use?
The SimpliVPNAPI uses an API key passed in the `Authorization` header. 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 getservers with the SimpliVPNAPI?
Yes. Use the GET /servers endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SimpliVPNAPI?
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 getservers through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getservers'. Jentic returns the matching SimpliVPNAPI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SimpliVPNAPI have?
The SimpliVPNAPI exposes 7 endpoints covering disable user, enable user, login operations.
Can I limit what my agent is allowed to do with the SimpliVPN API?
Yes. Because Jentic One is self-hosted and governed by your own rules, you decide which SimpliVPN operations your agent may call and which credentials it may use. Since SimpliVPN passes its targets in the request body rather than as a resource ID in the URL, you scope the agent at the operation level: allow read-only calls like GET /servers and POST /username-available while withholding account changes such as POST /disable-user or POST /enable-user. Only the operations you approve are exposed to the agent, and your API key is injected at execution time without entering the agent's context.
For Agents
Programmatically getservers, getserversummaries. Covers 7 operations with apiKey authentication.
Use for: I need to getservers, I want to getserversummaries, Search for register, Find all login
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
simplivpn.net/main version 1.0. The API exposes 7 endpoints secured with apiKey authentication.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>