Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Buy App Downloads 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%2Fbuy-app-downloads.com%2Fbuy-app-downloads" | 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%2Fbuy-app-downloads.com%2Fbuy-app-downloads" | 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 Buy App Downloads API.
List and create app listings
Retrieve or delete a single app listing
Place and list download orders
Retrieve or delete a single order
List the supported countries
GET STARTED
Patterns agents use Buy App Downloads API for, with concrete tasks.
★ Order app installs
Drive app installs programmatically. The agent places a download order for a listed app and targets it at the supported countries.
Call POST /orders to place an install order for an app
Manage app listings
Keep the set of promoted apps current. The agent creates listings, reads them back, and removes listings that are no longer promoted.
Call POST /apps to create a listing, GET /apps to review them
Track order status
Report progress on running campaigns. The agent reads a single order to check its status and lists orders to summarise what is in flight.
Call GET /orders/{id} to read the status of an order
9 endpoints — the buy app downloads api lets an agent order app installs and manage the listings and orders behind them.
METHOD
PATH
DESCRIPTION
/apps
List app listings
/apps
Create an app listing
/apps/{id}
Retrieve a single app listing
/apps/{id}
Delete an app listing
/orders
List download orders
/orders
Place a download order
/orders/{id}
Retrieve a single order
/orders/{id}
Delete an order
/apps
List app listings
/apps
Create an app listing
/apps/{id}
Retrieve a single app listing
/apps/{id}
Delete an app listing
/orders
List download orders
/orders
Place a download order
/orders/{id}
Retrieve a single order
/orders/{id}
Delete an order
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Buy App Downloads API by hand means managing a bearer token, pointing at the buy-app-downloads.com host, and shaping the order requests yourself. Through Jentic you install once, import the Buy App Downloads API from the Jentic API Directory, store the token once, and your agent calls it.
Permission scoping
You decide which operations your agent may call, so it can read orders without being able to place or delete them. Because the order id sits in the URL path (/orders/{id}), a rule can pin the agent to a single order rather than the whole account.
Credential isolation
Your Buy App Downloads bearer token 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 'order app installs' or 'check an order status', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference.
Alternatives and complements available in the Jentic catalogue.
Specific to using Buy App Downloads API through Jentic.
What authentication does the Buy App Downloads API use?
The Buy App Downloads API uses a bearer token. Through Jentic, that token is stored encrypted in your Jentic One instance and injected at execution time, so the raw token never enters the agent context.
What can an agent do with the Buy App Downloads API?
It can list and create app listings, read or delete a single listing, place and list download orders, read or delete a single order, and list the supported countries. The service is built for programmatic app user acquisition.
How does an agent connect to the Buy App Downloads API through Jentic?
Install Jentic One, import the Buy App Downloads API from the Jentic API Directory, and store the bearer token once. Your agent then calls the operations you have allowed without handling the raw token.
What are the rate limits for the Buy App Downloads API?
Rate limits are not specified in the OpenAPI spec. Check the Buy App Downloads documentation for current limits. Through Jentic, retries are handled in the execution layer.
How many endpoints does the Buy App Downloads API have?
The Buy App Downloads API exposes 9 endpoints covering apps, orders, and supported countries.
Can I limit what my agent is allowed to do with the Buy App Downloads API?
Yes. Jentic One is self-hosted by you, so your own rules decide which operations your agent may call. You can let it read orders without being able to place or delete them, and because the order id sits in the URL path, such as /orders/{id}, a rule can pin the agent to a single order.
Know of an official OpenAPI document? Contribute it →
For Agents
Order app installs and manage listings and orders through the Buy App Downloads API. List or create apps, place and track download orders, and read supported countries. Secured with a bearer token.
Use for: List the available app listings, Create a new app listing, Place an app download order, Check the status of an order
Not supported: Does not handle app store publishing or install attribution - use it to order app downloads and manage the orders behind them.
The Buy App Downloads API lets an agent order app installs and manage the listings and orders behind them. It can list and create app listings, read or delete a single listing, place and list download orders, read or delete a single order, and list the countries installs can be targeted at. It is a user-acquisition service for mobile apps.
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>