Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shop, 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%2Fshop.app%2Fshop" | 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%2Fshop.app%2Fshop" | 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 Shop API.
Search for products
Return more details about a list of products.
Integrate Shop into automated workflows
Query and filter Shop records by parameters
Monitor Shop operational status and events
GET STARTED
Patterns agents use Shop API for, with concrete tasks.
★ E-Commerce Operations
Use the Shop to perform e commerce operations programmatically. The API provides 2 endpoints covering core functionality including search for products, return more details about a list of products..
Call GET /openai/search to search for products
Data Retrieval and Monitoring
Query Shop resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Shop endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Shop 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 none tokens manually.
Search Jentic for 'search for products', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — search for millions of products from the world's greatest brands.
METHOD
PATH
DESCRIPTION
/openai/search
Search for products
/openai/details
Return more details about a list of products.
/openai/search
Search for products
/openai/details
Return more details about a list of products.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Shop API by hand means formatting search and details requests against server.shop.app and parsing the product results yourself. Through Jentic you install once, import Shop from the API Directory, and your agent calls it, with no key to manage since these endpoints are open.
Permission scoping
The Shop endpoints in this spec are two read-only lookups, so you limit the agent to the operations it needs, such as product search or product details, and it can call nothing beyond the read operations you choose.
Credential isolation
Shop exposes these endpoints without a credential, so there is no secret to store, and any configuration your Jentic One instance holds is injected at execution time rather than placed in the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search for products' or 'get product details', and Jentic returns the matching Shop 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.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Shop API through Jentic.
What authentication does the Shop use?
The Shop uses no authentication. 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 search for products with the Shop?
Yes. Use the GET /openai/search endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Shop?
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 search for products through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search for products'. Jentic returns the matching Shop operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Shop have?
The Shop exposes 2 endpoints covering openai operations.
Can I limit what my agent is allowed to do with the Shop API?
Yes. Because you run Jentic One yourself, your own rules decide which Shop operations the agent may call. The Shop API exposes only two read-only lookups, product search via GET /openai/search and product details via GET /openai/details, so you can grant the agent just the one it needs and it can call nothing beyond the read operations you allow. Since these endpoints need no credential, there is no secret to hand the agent, and any configuration your instance holds is injected only at execution time.
For Agents
Programmatically search for products, return more details about a list of products.. Covers 2 operations.
Use for: I need to for products, I want to return more details about a list of products., Get the current status of Shop resources, List all records from Shop
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Search for millions of products from the world's greatest brands. The API exposes 2 endpoints.
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>