Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the appmanai Public 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%2Fappmanai.com%2Fappmanai" | 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%2Fappmanai.com%2Fappmanai" | 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 appmanai Public API.
Search the App Store and Google Play for apps by name
Read current and historical app metrics for ratings, installs, and metadata
Pull app reviews and category rankings for an app
Look up keyword metrics such as search volume, difficulty, and ranking
Track how an app ranks for a keyword over time and worldwide
GET STARTED
Find keyword suggestions, competitors, and keyword overlap for an app
Generate keyword and app-metadata suggestions from the generate endpoints
Patterns agents use appmanai Public API for, with concrete tasks.
★ App Store Optimization Research
An agent researches a target keyword by reading its search volume and difficulty, then checks how a given app ranks for it across markets. appmanai returns keyword metrics and per-app rankings so the agent can decide which terms are worth optimizing without pulling data from several tools.
Call GET /keywords/metrics for a term, then GET /keywords/app/metrics/rankings to read how the app ranks for it
Competitor and Review Monitoring
A monitoring workflow pulls an app's ratings history, recent reviews, and category rankings on a schedule to track how it performs against competitors. The agent reads review and ranking data per app so changes in sentiment or position surface without manual store checks.
Call GET /apps/reviews for an app, then GET /apps/metrics/ratings/history to chart its rating trend
AI Agent Integration via Jentic
An AI agent reaches the appmanai Public API through Jentic without holding the bearer key itself. It searches by intent, receives the matching operation with its input schema, and executes the call with the credential injected at run time, so app and keyword data flow into a larger ASO workflow.
Search Jentic for 'read app store keyword metrics', load the GET /keywords/metrics schema, and execute it with Jentic-managed credentials
33 endpoints — the appmanai public api returns app store and google play data for app store optimization work.
METHOD
PATH
DESCRIPTION
/apps/search
Search apps by name
/apps/metrics/metadata
Read current app metadata
/apps/metrics/ratings/history
Read ratings history
/apps/reviews
List app reviews
/keywords/metrics
Read current keyword metrics
/keywords/app/metrics/rankings
Read keyword rankings for an app
/categories/top-apps
Read current top charts for a category
/generate/keywords
Generate keyword suggestions
/apps/search
Search apps by name
/apps/metrics/metadata
Read current app metadata
/apps/metrics/ratings/history
Read ratings history
/apps/reviews
List app reviews
/keywords/metrics
Read current keyword metrics
/keywords/app/metrics/rankings
Read keyword rankings for an app
/categories/top-apps
Read current top charts for a category
/generate/keywords
Generate keyword suggestions
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the appmanai Public API by hand means managing its bearer key and juggling the current, history, and worldwide variants of each metric endpoint yourself. Through Jentic you install once, import appmanai from the API Directory, store the key once, and your agent calls it.
Permission scoping
appmanai carries the app and keyword identifiers inside each request, so a rule bounds which operations your agent may call rather than which app it reads. You choose the operations it may use, such as the keyword and ranking reads, so the generate operations are not included unless you add them.
Credential isolation
Your appmanai 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 'read app store keyword metrics' or 'list app reviews', and Jentic returns the matching appmanai 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 appmanai Public API through Jentic.
What authentication does the appmanai Public API use?
The appmanai Public API authenticates with a bearer key in the Authorization header, per its OpenAPI spec. Read endpoints are GET with query parameters and the two generate endpoints are POST with a JSON body. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I read an app's keyword rankings with the appmanai Public API?
Yes. GET /keywords/metrics returns a term's search volume and difficulty, and GET /keywords/app/metrics/rankings returns how a given app ranks for it, with worldwide and history variants for broader coverage. The responses are structured JSON an agent can parse directly.
What are the rate limits for the appmanai Public API?
The appmanai OpenAPI spec does not specify rate limits. Watch for HTTP 429 responses and check appmanai's documentation for the current limits before pulling large batches of app or keyword data.
How do I read app store keyword metrics with the appmanai Public API through Jentic?
Search Jentic for 'read app store keyword metrics', and it returns the appmanai operation with its input schema. Load the schema and execute GET /keywords/metrics with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an appmanai MCP server?
You don't need an MCP server to give your agent the appmanai Public API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the app and keyword operations it needs. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.
Can I limit what my agent is allowed to do with the appmanai Public API?
Yes. appmanai carries the app and keyword identifiers inside each request, so a rule bounds which operations your agent may call. Allow only the read lookups the task needs, such as keyword metrics and rankings, so the generate operations stay off the table, and every call runs through your own instance where it is logged.
For Agents
Read App Store and Google Play data for ASO: app metadata, ratings and install history, reviews, category rankings, and keyword metrics and suggestions. Reads are GET with a bearer key; the two generate endpoints are POST.
Use for: Search for an app by name on the App Store, Get the current ratings and install history for an app, List the reviews for a specific app, Check how an app ranks for a target keyword
Not supported: Does not submit apps, manage store listings, or run ad campaigns. Use for reading App Store and Google Play metrics and keyword data only.
The appmanai Public API returns App Store and Google Play data for app store optimization work. It reads current and historical app metrics such as ratings, installs, and metadata, lists app reviews and category rankings, and reports keyword metrics including search volume, difficulty, and how an app ranks for a term over time. Two generate endpoints produce keyword and app-metadata suggestions, and reference endpoints list the supported countries, categories, and features.
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>