Install Jentic One Beta

Connect the ProxyOmega Reseller API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ProxyOmega Reseller 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%2Fproxyomega.com%2Fproxyomega" | sh

Step 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%2Fproxyomega.com%2Fproxyomega" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with ProxyOmega Reseller API.

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

GET STARTED

Start building with ProxyOmega Reseller API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ProxyOmega Reseller API for, with concrete tasks.

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

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.

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.

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.

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

Key Endpoints

20 endpoints — the proxyomega reseller api provisions residential, mobile, and ipv6 datacenter proxy services for the sub-accounts you resell to.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using ProxyOmega Reseller API through Jentic.

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.

ProxyOmega Reseller API

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Community OpenAPI document · agent-readyCloud InfrastructureNetworkingapiKey20 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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

Use for: I need to create a proxy sub-account for a new customer, Provision 50GB of Platinum residential proxies for sub-account 123, Generate 10 US proxies in socks5 format for a sub-account, Check whether my reseller balance covers a new subscription

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

27%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

31%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

75%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ProxyOmega Reseller API to your agent

Capabilities

Start building with ProxyOmega Reseller API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ProxyOmega Reseller API

Jentic AI Readiness Score

ProxyOmega Reseller API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness