canonical: https://jentic.com/apis/proxykingdom.com/proxykingdom

# ProxyKingdom-Api

proxykingdom.com/main version v1. The API exposes 1 endpoints.

## For AI agents

Programmatically gets a random proxy for chosen parameters.. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Gets a random proxy for chosen parameters.
- Access ProxyKingdom-Api resources via REST API
- Access ProxyKingdom-Api resources via REST API

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'gets a random proxy for chosen parameters.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/proxy` | Gets a random proxy for chosen parameters. |

## Key resources

- **Proxy** — Operations for proxy

## AI readiness

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.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 15 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/proxykingdom.com/proxykingdom/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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