Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ProxyKingdom-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%2Fproxykingdom.com%2Fproxykingdom" | 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%2Fproxykingdom.com%2Fproxykingdom" | 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 ProxyKingdom-Api.
Gets a random proxy for chosen parameters.
Access ProxyKingdom-Api resources via REST API
Access ProxyKingdom-Api resources via REST API
Patterns agents use ProxyKingdom-Api for, with concrete tasks.
★ Developer Tools Operations
Use the ProxyKingdom-Api to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including gets a random proxy for chosen parameters..
GET STARTED
Call GET /proxy to gets a random proxy for chosen parameters.
Data Retrieval and Monitoring
Query ProxyKingdom-Api endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows without manual intervention.
Query the ProxyKingdom-Api API to retrieve current data and verify the response contains expected fields
AI Agent Integration via Jentic
AI agents discover and call ProxyKingdom-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 'gets a random proxy for chosen parameters.', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — proxykingdom.
METHOD
PATH
DESCRIPTION
/proxy
Gets a random proxy for chosen parameters.
/proxy
Gets a random proxy for chosen parameters.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ProxyKingdom API by hand still means writing the HTTP client, setting query parameters, and parsing its proxy response yourself. Through Jentic you install once, import ProxyKingdom from the API Directory, and your agent calls it without you maintaining that plumbing.
Permission scoping
The ProxyKingdom API exposes a single read operation (GET /proxy) with no resource id in the path, so you limit the agent to the operations it needs, such as fetching a random proxy. That read is the whole surface, and you decide it is the only thing the agent may call.
Credential isolation
ProxyKingdom needs no credential in this spec, so there is nothing to store, and any header your setup does require is held 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 'get a random proxy matching parameters', and Jentic returns the matching ProxyKingdom 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 ProxyKingdom-Api through Jentic.
What authentication does the ProxyKingdom-Api use?
The ProxyKingdom-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 gets a random proxy for chosen parameters. with the ProxyKingdom-Api?
Yes. Use the GET /proxy endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the ProxyKingdom-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 gets a random proxy for chosen parameters. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets a random proxy for chosen parameters.'. Jentic returns the matching ProxyKingdom-Api operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the ProxyKingdom-Api have?
The ProxyKingdom-Api exposes 1 endpoints covering proxy operations.
Can I limit what my agent is allowed to do with the ProxyKingdom API?
Yes. The ProxyKingdom API exposes a single read operation, GET /proxy, which fetches a random proxy for the parameters you choose. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, so you can allow only that proxy-fetch call and nothing else. That one read is the entire surface you expose to the agent.
For Agents
Programmatically gets a random proxy for chosen parameters.. Covers 1 operations.
Use for: I need to gets a random proxy for chosen parameters., I need to access ProxyKingdom-Api programmatically, I want to integrate ProxyKingdom-Api into my workflow, Search for available developer tools operations
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
proxykingdom.com/main version v1. The API exposes 1 endpoints.
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>