Install Jentic One Beta

Connect the Catalog API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Catalog 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.

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%2Febay.com%2Febay-commerce-catalog" | sh

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%2Febay.com%2Febay-commerce-catalog" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Catalog API.

Search eBay's product catalog by keyword, GTIN, or category to find matching products

Retrieve complete product details by ePID including aspects, images, and item specifics

Match seller inventory to eBay catalog entries for pre-filled listing creation

Filter catalog search results by category, aspect refinements, and product identifiers

Access standardized product attributes that auto-populate listing fields

GET STARTED

Start building with Catalog API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Catalog API for, with concrete tasks.

★ AI Agent Catalog Matching

AI agents use the eBay Catalog API through Jentic to automatically match seller inventory to eBay's product catalog. When a seller provides a UPC, ISBN, or product title, the agent searches the catalog, identifies the exact product match, and retrieves all structured attributes needed to create a pre-filled listing - eliminating manual data entry for item specifics, titles, and images.

Search the eBay catalog for products matching UPC 194252056227 and retrieve the top match's ePID, title, and item specifics

Bulk Listing Data Enrichment

Enrich bulk product feeds with eBay catalog data before creating listings. For each item in a seller's inventory file, search the catalog by GTIN or keyword to find the matching ePID, then retrieve standardized titles, descriptions, images, and aspect values. This ensures all listings have complete, accurate information that complies with eBay's structured data requirements.

For a product with title 'Apple AirPods Pro 2nd Generation', search the catalog to find the matching ePID and retrieve all available item specifics

Category and Aspect Discovery

Discover valid eBay categories and their required aspects before listing products. The catalog search endpoint returns aspect refinements that indicate which product attributes are available for filtering. Use this to build category-aware listing tools that prompt sellers for the right item specifics based on their product type.

Search the catalog for 'wireless headphones' and retrieve the available aspect refinements including brand, connectivity, and color options

Key Endpoints

2 endpoints — look up and search ebay's product catalog to find exact matches for items sellers want to list.

METHOD

PATH

DESCRIPTION

GET

/product/{epid}

Get product details by eBay Product ID

GET

/product_summary/search

Search catalog products by keyword, GTIN, or category

GET

/product/{epid}

Get product details by eBay Product ID

GET

/product_summary/search

Search catalog products by keyword, GTIN, or category

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the eBay Catalog API by hand means running the OAuth 2.0 flow, caching and refreshing the token, and setting marketplace headers on each product lookup. Through Jentic you install once, import the Catalog API from the API Directory, store the client credentials once, and your agent calls it while Jentic handles the token exchange.

Permission scoping

The Catalog API puts the product id in the URL path (/product/{epid}), so a rule can pin your agent to product lookup and matching: it reads catalog products and nothing else. Since these are read-only operations, the agent's reach stays limited to the lookups you allow.

Credential isolation

Your eBay OAuth credentials are stored once, encrypted, by your own Jentic One instance, which exchanges them for a token and injects it at execution time. The raw client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find eBay catalog product by UPC', and Jentic returns the matching Catalog API operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Catalog API through Jentic.

What authentication does the eBay Catalog API use?

The eBay Catalog API requires OAuth 2.0 bearer tokens with the commerce.catalog.readonly scope. Through Jentic, your OAuth tokens are stored encrypted in your Jentic One instance - agents receive pre-authenticated requests without handling the OAuth flow or token refresh directly.

Can I search the eBay catalog by UPC or ISBN?

Yes. The GET /product_summary/search endpoint accepts a gtin filter parameter for UPC, EAN, and ISBN lookups. Pass the barcode value and the API returns matching catalog products with their ePIDs, titles, and images. This is the fastest path to an exact product match.

What are the rate limits for the eBay Catalog API?

The Catalog API follows eBay's standard rate limits of 5000 calls per day per application for the product_summary/search endpoint and 5000 calls per day for the product/{epid} endpoint. Rate limit headers (X-EBAY-C-MARKETPLACE-ID) are returned with each response.

How do I retrieve product details for listing creation through Jentic?

Search Jentic for 'look up eBay catalog product by ID' to discover the GET /product/{epid} operation. Pass the ePID and receive structured JSON with the product title, description, images, and all item specifics. These fields map directly to eBay listing creation parameters.

What data does the catalog product response include?

A product response includes the ePID, title, description, primary and additional images, product identifiers (UPC, ISBN, ePID), aspect values (brand, model, color, size), and the eBay category assignment. This pre-fills most required listing fields automatically.

Is the eBay Catalog API available in all marketplaces?

The Catalog API supports eBay's major marketplaces including US (EBAY_US), UK (EBAY_GB), Germany (EBAY_DE), and Australia (EBAY_AU). Set the X-EBAY-C-MARKETPLACE-ID header to target a specific marketplace. Product catalog coverage varies by marketplace.

Can I limit what my agent is allowed to do with the eBay Catalog API?

Yes. Because you self-host Jentic One, your own rules decide which of the eBay Catalog operations the agent may call, so you can allow it to search products with GET /product_summary/search and read details with GET /product/{epid} while blocking everything else. Both operations are read-only and put the product id in the URL path, so a rule can pin the agent to catalog lookup and matching and nothing more. Jentic One also holds your eBay OAuth credentials and injects the token at execution time, so the agent never sees the raw client secret and stays inside the scope you define.

Ebay Catalog API

Browse all Ebay APIs

AI ReadinessFoundational (C)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontoauth22 EndpointsREST

For Agents

Search eBay's product catalog by keyword or retrieve product details by ePID. Returns structured product data including titles, images, and item specifics for listing creation.

Use for: I need to find the eBay catalog product matching a specific UPC barcode, Search for product listings that match my inventory item by keyword, Retrieve the item specifics and stock images for an eBay product ID, Find all catalog products in a specific eBay category

Not supported: Does not handle listing creation, order management, or payment processing - use for product catalog lookup and matching only.

Look up and search eBay's product catalog to find exact matches for items sellers want to list. Listing against a catalog product auto-fills titles, descriptions, item specifics, and stock images - reducing listing creation time and ensuring data accuracy across millions of product entries.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

76%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

50%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Catalog API to your agent

Capabilities

Start building with Catalog API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ebay Catalog API

Jentic AI Readiness Score

Catalog API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness