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

# ProxyOmega Reseller API

The ProxyOmega Reseller API provisions residential, mobile, and IPv6 datacenter proxy services for the sub-accounts you resell to. It creates and updates sub-accounts, provisions Unlimited Residential, Platinum, Mobile, and IPv6 subscriptions against your reseller balance, and generates ready-to-use proxy lists with country, region, city, and ASN targeting. A development server at the /dev path returns mock data without an API key or KYC, so you can test provisioning before going live.

## For AI agents

Create proxy reseller sub-accounts, provision residential, mobile, and IPv6 proxy subscriptions, and generate targeted proxy lists in formats such as host:port:username:password or socks5. Also reads wholesale pricing, balance, and transaction history.

## Scope

Does not handle web scraping, proxy IP reputation checks, or end-customer payment collection. Use for provisioning and managing resold ProxyOmega proxy services only.

## Capabilities

- Create, update, and delete white-label sub-accounts with a username, email, and your own external_id
- Provision Unlimited Residential, Platinum, Mobile, or IPv6 proxy subscriptions for a sub-account and cancel them to deprovision
- Generate up to 1000 proxies per call with country, region, city, ASN, and sticky session targeting in formats including socks5 and csv
- Configure per-port IP rotation and country targeting on Unlimited Residential subscriptions
- Read wholesale product pricing, your reseller balance, and transaction history filtered by deposit, provision, refund, or adjustment
- List the countries, regions, and cities available for each proxy product before targeting

## Use cases

### Agent-run proxy customer provisioning

An AI agent connected to your storefront or billing system can onboard a proxy customer end to end: create the sub-account, provision the product the customer paid for, and return a formatted proxy list. The ProxyOmega Reseller API deducts provisioning from your reseller balance, so the agent can check the balance first and stop before a purchase would fail with an insufficient balance error.

Example prompt: Create a sub-account with username acme_user1 and email ops@acme.example, provision a Platinum subscription with product_type platinum and gb 50, then generate 10 proxies with country us

### Targeted proxy list generation

Scraping and ad-verification customers need proxies pinned to a location. The proxy-list operation generates between 1 and 1000 proxies for a sub-account with country, region, city, and ASN targeting plus a sticky session and a ttl of 1 to 60 minutes, returned in formats such as host:port, username:password@host:port, socks5, json, or csv.

Example prompt: Generate 25 mobile proxies for sub-account 123 with product_type mobile, country gb, city london, a ttl of 30, and format json

### Unlimited Residential port configuration

Unlimited Residential subscriptions are targeted per port rather than through the proxy username. The port-configs operations list, create or update, and delete the configuration on each port, setting a rotation_minutes interval such as 1, 5, or 30 and a country_targeting code, so a reseller can give each customer port its own rotation behaviour.

Example prompt: Set port_number 10001 on subscription 456 of sub-account 123 to rotate every 10 minutes with country_targeting de

### Reseller balance and transaction reconciliation

Resellers reconcile what they charged customers against what ProxyOmega deducted. The API returns the current reseller balance, moves funds from the main account into the reseller balance, and pages through transaction history filtered by type such as provision or refund, so spend per period can be matched to customer invoices.

Example prompt: List provision transactions on page 1 with a limit of 100 and total the amounts deducted this month

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/sub-accounts` | Create a sub-account |
| POST | `/sub-accounts/{id}/subscriptions` | Provision a proxy service for a sub-account |
| GET | `/sub-accounts/{id}/proxy-list` | Generate a targeted proxy list |
| POST | `/sub-accounts/{sub_account_id}/subscriptions/{subscription_id}/port-configs` | Create or update a port configuration |
| DELETE | `/sub-accounts/{sub_account_id}/subscriptions/{subscription_id}` | Cancel a subscription |
| GET | `/balance` | Get the reseller balance |
| GET | `/products` | Get products and wholesale pricing |
| GET | `/geographic/cities` | List available cities for a product |

## Key resources

- **Sub-accounts** — White-label customer accounts with username, email, label, and external_id
- **Subscriptions** — Provisioned proxy services per sub-account: unlimited, platinum, mobile, or ipv6
- **Proxy lists** — Generated proxy credentials with geographic and session targeting
- **Port configurations** — Per-port rotation and country targeting for Unlimited Residential subscriptions
- **Balance and transactions** — Reseller balance, fund transfers, and transaction history
- **Products and geography** — Wholesale pricing and the countries, regions, and cities available per product

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 81 / 100
- **View full report:** https://jentic.com/apis/proxyomega.com/proxyomega/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 ProxyOmega by hand means handling its X-API-Key header, switching between the production and /dev servers, and building the oneOf provisioning bodies for each product. Through Jentic you install once, import ProxyOmega from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** ProxyOmega puts the sub-account id in the URL path (`/sub-accounts/{id}/...`), so a rule can pin your agent to one sub-account and the operations you pick. You choose the operations it may call, so spending ones like provisioning or balance transfer and destructive ones like sub-account deletion are not included unless you add them.
- **Credential handling:** Your ProxyOmega 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.
- **Discovery method:** Agents search Jentic by intent such as 'generate a proxy list' or 'provision residential proxies', and Jentic returns the matching ProxyOmega operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Oxylabs Web Scraper API** — Oxylabs runs scraping jobs on its own proxy network, where ProxyOmega gives you raw proxies to resell.
- **Bright Data Web Scraper API** — Bright Data collects web data asynchronously as snapshots instead of issuing proxy lists.
- **IP2Proxy Proxy Detection** — IP2Proxy reports whether an IP is flagged as a proxy or VPN.

## FAQ

### What authentication does the ProxyOmega Reseller API use?

The ProxyOmega Reseller API authenticates with an API key sent in the X-API-Key header, as declared in its OpenAPI spec, and the spec notes production access also needs completed KYC verification. The development server at /dev needs no key. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.

### Can I generate targeted proxy lists with the ProxyOmega Reseller API?

Yes. GET `/sub-accounts/{id}/proxy-list` takes a required product_type plus optional country, region, city, asn, session, ttl, and quantity parameters, and returns up to 1000 proxies in a format such as host:port:username:password, socks5, json, or csv. Region, city, and ASN targeting apply to the platinum and mobile products.

### What are the rate limits for the ProxyOmega Reseller API?

The OpenAPI spec description states production limits of 100 requests per minute as burst and 1,000 requests per hour sustained, with HTTP 429 and a Retry-After header when exceeded. The development API has no rate limits.

### How do I provision a proxy subscription with the ProxyOmega Reseller API through Jentic?

Search Jentic for 'provision a proxy subscription', which returns POST `/sub-accounts/{id}/subscriptions` with its input schema, then send a product_type such as platinum with a gb amount, or unlimited with a duration and ports. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a ProxyOmega MCP server?

You don't need an MCP server to give your agent the ProxyOmega Reseller API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in your agent's context.

### Can I limit what my agent is allowed to do with the ProxyOmega Reseller API?

Yes. Write a rule that allows only the proxy-list and subscription-list reads under `/sub-accounts/123`, so the agent can hand out proxies for that one customer but cannot provision new services, spend your balance, or delete the sub-account, and every call it makes is logged.