Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the topupsapi, 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%2Freloadly.com%2Freloadly" | 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%2Freloadly.com%2Freloadly" | 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 topupsapi API.
Publish a poll question with an array of answer choices
List published poll questions with each choice's vote count
Read the published_at timestamp of each poll question
Patterns agents use topupsapi API for, with concrete tasks.
★ Agent runs a quick team poll
An agent connected through Jentic publishes a question with its choices in one call, then later lists the questions to read back the votes recorded against each choice and report the leader. The spec has no vote-casting operation, so the agent reports on votes rather than casting them.
GET STARTED
Call POST /questions with question set to 'Favourite programming language?' and choices set to Swift, Python, Objective-C, and Ruby, then call GET /questions to read the vote counts
Prototype a question-and-choice flow
Developers building a survey or poll feature use this compact spec to test a create-and-list loop: a POST that takes a question string and choices array, and a GET that returns each question with choice objects carrying choice and votes fields.
Call POST /questions with a test question and two choices, then call GET /questions and confirm the new question appears with votes at 0
Poll results digest
A scheduled job lists all published questions and turns the votes on each choice into a short digest, sorted by published_at, for a chat channel or report.
Call GET /questions, sort the questions by published_at, and report the choice with the most votes for each
2 endpoints — the topupsapi spec listed under reloadly describes a small polls service: it publishes poll questions with a set of answer choices and lists the questions already published, each with its choices, vote counts, and published_at timestamp.
METHOD
PATH
DESCRIPTION
/questions
List all poll questions with vote counts
/questions
Publish a new poll question with choices
/questions
List all poll questions with vote counts
/questions
Publish a new poll question with choices
What agents get from Jentic-routed access to this vendor.
Setup
Wiring topupsapi by hand means finding its polls.apiblueprint.org host and the question and choices body shape from an Apiary document. Through Jentic you install once, import it from the API Directory, and your agent calls it with the schema already loaded.
Permission scoping
Both operations share the /questions path and differ only by method, so a rule can separate reading polls from publishing them: your agent may list questions without being able to create one unless you add POST.
Credential isolation
This spec declares no security scheme, so there is nothing secret to hold and nothing sensitive enters the agent's prompt, logs, or context. Calls run from your own Jentic One instance.
Intent-based discovery
Agents search Jentic by intent such as 'create a poll' or 'list poll questions', and Jentic returns the matching operation with its input schema so the agent sends the right question and choices fields.
Alternatives and complements available in the Jentic catalogue.
Specific to using topupsapi API through Jentic.
Does the topupsapi spec include mobile top-ups?
No. Although it is listed under Reloadly with the title topupsapi, its two operations publish and list poll questions on polls.apiblueprint.org. For airtime or top-up operations, look for a different Reloadly spec.
What authentication does the topupsapi use?
Per its OpenAPI spec, topupsapi declares no security scheme, and neither GET /questions nor POST /questions lists a credential.
How do I create a poll question with the topupsapi?
Send POST /questions with a JSON body containing question, a string, and choices, an array of strings. The 201 response returns the question with each choice set to 0 votes and a published_at timestamp, plus a Location header.
Can I cast a vote with the topupsapi?
Not through this spec. It defines listing and creating questions only; vote counts appear in the GET /questions response but no operation records a vote.
What are the rate limits for the topupsapi?
The OpenAPI spec does not specify rate limits. Check https://topupsapi.docs.apiary.io for the source documentation.
How do I list poll results through Jentic?
Search Jentic for 'list poll questions'. It returns the GET /questions operation, your agent calls it, and reads the votes on each choice. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the topupsapi?
Yes. Allow only GET /questions and a reporting agent can read polls and their votes but cannot publish a new question. Add POST /questions only for an agent that should create polls.
Know of an official OpenAPI document? Contribute it →
For Agents
Publish a poll question with answer choices and list existing questions with their per-choice vote counts.
Use for: Create a poll asking 'Favourite programming language?' with four choices, List all poll questions and their vote counts, Check which choice is leading on the programming language poll, Get the date each poll question was published
Not supported: Does not handle mobile airtime top-ups, vote casting, or survey response collection. Use for publishing and listing poll questions only.
The topupsapi spec listed under Reloadly describes a small polls service: it publishes poll questions with a set of answer choices and lists the questions already published, each with its choices, vote counts, and published_at timestamp. Despite the name, the operations in this spec cover polls only, served from polls.apiblueprint.org, and contain no airtime or mobile top-up functions. Treat it as a reference polls API for prototyping question-and-choice flows.
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>