Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the reverb, 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%2Freverb.com%2Freverb" | 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%2Freverb.com%2Freverb" | 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 reverb API.
List of all article categories
Full taxonomy tree of categories including middle categories
Get subcategory details
Returns a set of comparison shopping pages based on the current params
Show comparison shopping page
GET STARTED
Patterns agents use reverb API for, with concrete tasks.
★ Developer Tools Operations
Use the reverb to perform developer tools operations programmatically. The API provides 163 endpoints covering core functionality including list of all article categories, list of supported product categories, full taxonomy tree of categories including middle categories.
Call GET /articles/categories to list of all article categories
Automated Articles Management
Automate articles operations by combining multiple reverb endpoints. Agents can list of supported product categories and then full taxonomy tree of categories including middle categories in a single workflow.
Call GET /categories to list of supported product categories, then verify the result
AI Agent Integration via Jentic
AI agents discover and call reverb endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.
Search Jentic for 'list of all article categories', load the operation schema, and execute with Jentic-managed credentials
163 endpoints — reverb provides programmatic access to developer tools functionality.
METHOD
PATH
DESCRIPTION
/articles/categories
List of all article categories
/categories
List of supported product categories
/categories/taxonomy
Full taxonomy tree of categories including middle categories
/categories/{product_type}/{category}
Get subcategory details
/categories/{uuid}
Get category details
/comparison_shopping_pages
Returns a set of comparison shopping pages based on the current params
/comparison_shopping_pages/find
Show comparison shopping page
/comparison_shopping_pages/{id}/listings
Return new or used listings for a comparison shopping page
/articles/categories
List of all article categories
/categories
List of supported product categories
/categories/taxonomy
Full taxonomy tree of categories including middle categories
/categories/{product_type}/{category}
Get subcategory details
/categories/{uuid}
Get category details
/comparison_shopping_pages
Returns a set of comparison shopping pages based on the current params
/comparison_shopping_pages/find
Show comparison shopping page
/comparison_shopping_pages/{id}/listings
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Reverb by hand means running its OAuth2 client-credentials flow, refreshing tokens against reverb.com, and mapping the right read and write scopes for each call to api.reverb.com yourself. Through Jentic you install once, import Reverb from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Reverb's catalog and comparison-shopping reads travel in the path and query, not as a single resource you can pin, so limit the agent to the operations it needs, such as listing categories or fetching comparison-shopping pages. You choose that set, so write operations like editing listings or feedback are not included unless you add them.
Credential isolation
Your Reverb OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list all article categories' or 'find comparison shopping pages', and Jentic returns the matching Reverb 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 reverb API through Jentic.
What authentication does the reverb use?
The reverb uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I list of all article categories with the reverb?
Yes. Use the GET /articles/categories endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the reverb?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list of all article categories through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list of all article categories'. Jentic returns the matching reverb operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the reverb have?
The reverb exposes 163 endpoints covering articles, categories, comparison_shopping_pages operations.
Can I limit what my agent is allowed to do with the Reverb API?
Yes. Because Jentic One is self-hosted and governed by your own rules, you decide exactly which Reverb operations the agent can call. You can restrict it to the read operations it needs, such as listing article and product categories or fetching comparison shopping pages, while excluding write operations like editing listings or sending feedback. Those operations are never available to the agent unless you explicitly add them to its allowed set.
For Agents
Programmatically list of all article categories, list of supported product categories. Covers 163 operations with oauth2 authentication.
Use for: I need to of all article categories, I want to of supported product categories, Search for full taxonomy tree of categories including middle categories, Find all subcategory details
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
reverb provides programmatic access to developer tools functionality. The API exposes 163 endpoints secured with oauth2 authentication.
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.
Return new or used listings for a comparison shopping page
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>