Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Multi Item Search, 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%2Fswaggerhub.testorg1233322%2Fmulti-item-search" | 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%2Fswaggerhub.testorg1233322%2Fmulti-item-search" | 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 Multi Item Search API.
information about retail products, searched based on keywords and other attribu
Manage e commerce data programmatically
Integrate Multi Item Search into automated workflows
Query and filter Multi Item Search records by parameters
Monitor Multi Item Search operational status and events
GET STARTED
Patterns agents use Multi Item Search API for, with concrete tasks.
★ E-Commerce Operations
Use the Multi Item Search to perform e commerce operations programmatically. The API provides 1 endpoints covering core functionality including information about retail products, searched based on keywords and other attribu.
Call GET /multiItemsSearchAsync to information about retail products, searched based on keywords and other attribu
Data Retrieval and Monitoring
Query Multi Item Search 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 Multi Item Search endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Multi Item Search 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 apiKey tokens manually.
Search Jentic for ' information about retail products, searched based on keywords and other attribu', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — search retail products based on keywords and other attributes.
METHOD
PATH
DESCRIPTION
/multiItemsSearchAsync
information about retail products, searched based on keywords and other attribu
/multiItemsSearchAsync
information about retail products, searched based on keywords and other attribu
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Multi Item Search API by hand means setting its X-API-KEY and X-APP-ID headers, targeting the Algopix host, and handling the async search call and retries yourself. Through Jentic you install once, import Multi Item Search from the API Directory, store the key and app id once, and your agent calls it.
Permission scoping
Multi Item Search takes its query in request parameters rather than a resource id in the path, so scope the agent to the single async multi-item search operation it exposes. You choose the operations it may call, so nothing beyond that search runs unless you add it.
Credential isolation
Your Multi Item Search key and app id 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 'search retail products by keyword', and Jentic returns the matching Multi Item Search 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 Multi Item Search API through Jentic.
What authentication does the Multi Item Search use?
The Multi Item Search uses an API key passed in the `X-API-KEY` header. 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 information about retail products, searched based on keywords and other attribu with the Multi Item Search?
Yes. Use the GET /multiItemsSearchAsync endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Multi Item Search?
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 information about retail products, searched based on keywords and other attribu through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for ' information about retail products, searched based on keywords and other attribu'. Jentic returns the matching Multi Item Search operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Multi Item Search have?
The Multi Item Search exposes 1 endpoints covering API operations.
Can I limit what my agent is allowed to do with the Multi Item Search API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use. This API exposes a single async multi-item search operation (GET /multiItemsSearchAsync) that takes its query in request parameters, so you scope the agent to just that search and nothing else runs unless you add it. Your API key and app id stay encrypted in your own instance and are injected only at execution time.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically information about retail products, searched based on keywords and other attribu. Covers 1 operations with apiKey authentication.
Use for: I need to information about retail products, searched based on keywords and other attribu, Find available e commerce operations, Get the current status of Multi Item Search resources, List all records from Multi Item Search
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Search retail products based on keywords and other attributes. The API exposes 1 endpoints secured with apiKey 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.
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>