Axesso De Axesso API
Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationnone4 EndpointsREST
For Agents
Look up Amazon product details, run Amazon keyword searches, and retrieve buy recommendations through Axesso's structured scraping API. Returns JSON that agents can use without parsing HTML.
Use for: Look up the price and rating of an Amazon product by ASIN, Search Amazon for 'wireless headphones' and return the top results, Get buy recommendations for an Amazon product, Find the available sort options for an Amazon keyword search
Not supported: Does not handle order placement, seller account management, or non-Amazon marketplaces - use for Amazon product lookup, keyword search, and buy-recommendation retrieval only.
The Axesso API provides programmatic access to Amazon product data, including product lookups, keyword search results, sort options, and buy-recommendation suggestions. It is used by price-monitoring tools, e-commerce researchers, and competitive-intelligence agents that need structured Amazon data without scraping. The API is hosted at api.axesso.de and exposes four GET endpoints under the /amz path.
Install Jentic One Beta
Connect the Axesso API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Axesso 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.
1
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%2Faxesso.de%2Faxesso" | sh2
Step 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%2Faxesso.de%2Faxesso" | 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.
Capabilities
What an agent can do with Axesso API.
Look up an Amazon product by ASIN or URL and retrieve structured product information
Run a keyword search against Amazon and return ranked product results
Retrieve the available sort options for a given Amazon keyword search
Fetch buy recommendations associated with a specific Amazon product
Replace HTML scraping of Amazon listings with a structured JSON response surface
Use Cases
Patterns agents use Axesso API for, with concrete tasks.
★ Amazon Price and Listing Monitoring
Repricing tools and merchandising teams can poll Axesso to track price, rating, and availability changes on specific ASINs. GET /amz/amazon-lookup-product returns structured product data so monitoring jobs can diff against the previous snapshot. Suitable for dashboards that watch a defined set of competitor or own-brand listings.
Call GET /amz/amazon-lookup-product for an ASIN and store price, stock, and rating fields in a snapshot table for later comparison
Keyword Research for Amazon SEO
Sellers can run keyword queries through GET /amz/amazon-search-by-keyword to see how Amazon ranks listings for a given query. Combine with /amz/sort-options to test different sort orders and surface what Amazon shows shoppers under each. Useful for listing-optimisation and PPC keyword planning.
Run GET /amz/amazon-search-by-keyword for the seller's top three target keywords and capture the first 20 results per query
Competitive Recommendation Mining
Marketplaces and brand teams can fetch the buy recommendations Amazon shows alongside a competing product via GET /amz/amazon-lookup-buy-recommendations. This surfaces frequently-bought-with and similar-product slots that are valuable for category strategy. Suited to retail-intelligence workflows.
Call GET /amz/amazon-lookup-buy-recommendations for a target ASIN and extract the recommended ASINs for category benchmarking
Agent-Driven Amazon Research via Jentic
An e-commerce research agent can search Amazon, look up products, and retrieve recommendations through Jentic without managing the Axesso endpoint URLs. Jentic exposes the four operations as discoverable tools the agent can chain. Suited to category-research assistants and pricing copilots.
Search Jentic for 'search amazon by keyword', load GET /amz/amazon-search-by-keyword, and execute it for the user's research query
Key Endpoints
4 endpoints — the axesso api provides programmatic access to amazon product data, including product lookups, keyword search results, sort options, and buy-recommendation suggestions.
METHOD
PATH
DESCRIPTION
GET
/amz/amazon-lookup-product
Lookup product information for an Amazon listing
GET
/amz/amazon-search-by-keyword
Run an Amazon keyword search
GET
/amz/amazon-lookup-buy-recommendations
Get buy recommendations for a product
GET
/amz/sort-options
Get available sort options for a keyword search
GET
/amz/amazon-lookup-product
Lookup product information for an Amazon listing
GET
/amz/amazon-search-by-keyword
Run an Amazon keyword search
GET
/amz/amazon-lookup-buy-recommendations
Get buy recommendations for a product
GET
/amz/sort-options
Get available sort options for a keyword search
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Axesso by hand means standing up an HTTP client against api.axesso.de, adding the API key Axesso requires for production, and writing your own back-off for 429s while iterating across ASINs. Through Jentic you install once, import the Axesso API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
The Axesso product identifier and keyword travel as query parameters on GET operations, not as URL path segments, so scoping is by operation rather than by resource. You limit the agent to the operations it needs, such as GET /amz/amazon-lookup-product or GET /amz/amazon-search-by-keyword, and the others are not exposed unless you add them.
Credential isolation
Your Axesso API key is stored once, encrypted, by your own Jentic One instance and injected into the request at call time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up an amazon product' or 'search amazon by keyword', and Jentic returns the matching Axesso operation with its input schema so the agent calls the right endpoint without reading the Axesso docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Axesso API through Jentic.
What authentication does the Axesso API use?
The published OpenAPI spec does not declare a security scheme on these four /amz endpoints. In practice Axesso requires an API key for production usage; through Jentic, that key is held in the vault and injected at call time so it never reaches the agent context.
Can I look up a single Amazon product with the Axesso API?
Yes. GET /amz/amazon-lookup-product takes the product identifier and returns structured product information so you do not need to scrape the Amazon HTML.
How do I search Amazon by keyword through the Axesso API?
Call GET /amz/amazon-search-by-keyword with the keyword and any sort parameters. Use GET /amz/sort-options first to discover the valid sort values for that query.
What are the rate limits for the Axesso API?
The OpenAPI spec does not declare rate limits. Axesso enforces plan-based quotas via the customer dashboard. Back off on 429 responses and stagger lookups when iterating across many ASINs.
How do I run an Amazon search through Jentic?
Search Jentic for 'search amazon by keyword', load the GET /amz/amazon-search-by-keyword schema, and execute it. Jentic forwards the query and returns the JSON results to your agent.
Is the Axesso API free?
Axesso runs paid plans with quotas tied to product lookups and keyword searches. Check the Axesso website for current pricing tiers; Jentic only mediates the API calls, not billing.
Can I limit what my agent is allowed to do with the Axesso API?
Yes. Because Jentic One is self-hosted, you set the rules on your own instance, and access to Axesso is scoped per operation rather than per resource, since the product identifier and keyword travel as query parameters on GET calls. You expose only the operations your agent needs, such as GET /amz/amazon-lookup-product or GET /amz/amazon-search-by-keyword, and the remaining operations like GET /amz/amazon-lookup-buy-recommendations and GET /amz/sort-options stay unavailable unless you add them. Your Axesso API key is held by your own instance and injected at call time, so the agent uses it without ever seeing it.
GET STARTED