Install Jentic One Beta

Connect the Kroger API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kroger 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%2Fkroger.com%2Fkroger" | 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%2Fkroger.com%2Fkroger" | 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 Kroger API.

Search the Kroger product catalogue by term, location, brand, and fulfillment method

Retrieve detailed product information by product ID including pricing per store location

Search store locations by ZIP code, latitude/longitude, chain, or department availability

Get full details for a single store location including services and operating hours

Add one or more product UPCs to the authenticated customer's Kroger cart

GET STARTED

Start building with Kroger API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Kroger API for, with concrete tasks.

★ Recipe-to-cart shopping experience

A meal-planning app converts a recipe into Kroger UPCs by searching the product catalogue with /products, then uses PUT /cart/add to drop the matched items into the authenticated shopper's cart for pickup or delivery. Kroger handles inventory, pricing, and fulfilment options. The integration is typically built in 3-5 days once OAuth client credentials are issued.

Call GET /products?filter.term=organic+spinach&filter.locationId=01400376 to find a UPC, then PUT /cart/add with that UPC and quantity 1.

Store locator for delivery and pickup

A retail app uses /locations to render a list of nearby Kroger banners - Kroger, Ralphs, King Soopers, Fred Meyer, and others - filtered by ZIP, distance, and available services such as pharmacy or fuel. The /locations/{locationId} endpoint returns hours and amenity flags so the app can pick the right pickup window. This pattern serves the bulk of the API's external traffic.

Call GET /locations?filter.zipCode.near=45202&filter.radiusInMiles=10 and return the names, addresses, and pharmacy availability of the matching stores.

Personalised product browsing

An authenticated shopping experience reads the shopper profile from /identity/profile and combines it with location-scoped product searches to surface store-specific pricing, promotions, and availability. The OAuth authorization-code flow links the shopper's Kroger identity to the partner app while keeping credentials on Kroger.

After completing the OAuth authorization-code flow, call GET /identity/profile and use the returned profileId to scope subsequent product queries.

Agent-driven grocery ordering via Jentic

An assistant agent searches Jentic for 'add items to grocery cart' and is matched to PUT /cart/add along with the product search and location operations needed to resolve UPCs. Jentic handles the OAuth token refresh on the agent's behalf so the agent can compose 'find the nearest Kroger, search for these items, add them to my cart' as a single workflow.

Use the Jentic MCP tool kroger_add_to_cart to add UPCs ['0001111041700','0007003820027'] with quantity 2 each to the authenticated shopper's cart.

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for kroger api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/connect/oauth2/token

Issue an OAuth access token

GET

/connect/oauth2/authorize

Start the authorization-code flow

GET

/products

Search products by term and location

GET

/products/{productId}

Get product details by ID

GET

/locations

Search store locations

GET

/locations/{locationId}

Get a specific store location

PUT

/cart/add

Add items to the authenticated cart

GET

/identity/profile

Get the authenticated customer profile

POST

/connect/oauth2/token

Issue an OAuth access token

GET

/connect/oauth2/authorize

Start the authorization-code flow

GET

/products

Search products by term and location

GET

/products/{productId}

Get product details by ID

GET

/locations

Search store locations

GET

/locations/{locationId}

Get a specific store location

PUT

/cart/add

Add items to the authenticated cart

GET

/identity/profile

Get the authenticated customer profile

Why Jentic?

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

Setup

Wiring the Kroger API by hand means running the OAuth2 flow, base64-encoding client_id:client_secret for the token request, tracking scopes like product.compact and cart.basic:write, and refreshing access tokens against api.kroger.com yourself. Through Jentic you install once, import the Kroger API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

Kroger gates access by OAuth scope and its write targets travel in the request body, so scope the agent to the operations it needs, such as searching products and finding store locations. You choose that set, so the cart-add operation is not included unless you add it.

Credential isolation

Your Kroger client id, client secret, and refresh tokens are stored once, encrypted, by your own Jentic One instance, which refreshes access tokens at execution time. The secrets never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find nearby Kroger stores' or 'search grocery products', and Jentic returns the matching Kroger operation with its required scopes and parameters so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Kroger API through Jentic.

Why is there no official OpenAPI spec for Kroger API?

Kroger does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kroger API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Kroger API use?

Kroger uses OAuth 2.0 with both client-credentials and authorization-code grants - product and location search work with client credentials, while /cart/add and /identity/profile require authorization-code tokens scoped to the shopper. The token endpoint authenticates with HTTP Basic. Jentic stores the client secret and refresh tokens encrypted in your Jentic One instance.

Can I add items to a Kroger shopper's cart with the Kroger API?

Yes. PUT /cart/add accepts a list of items, each with a UPC and quantity, against the OAuth token of the authorised shopper. The shopper must have completed the authorization-code flow first so the token carries the cart.basic:write scope.

What are the rate limits for the Kroger API?

Kroger enforces a daily call limit per developer application - typically 10,000 calls per day for the standard tier - with separate ceilings for product search, location search, and cart endpoints. Refer to developer.kroger.com for exact figures and design batched calls where possible.

How do I search for products in a specific store through Jentic?

Search Jentic for 'kroger product search', load GET /products, and execute it with filter.term and filter.locationId. The locationId can be sourced from a prior call to GET /locations. Install with pip install jentic.

Does the Kroger API support placing a final order or checkout?

No. The Public API stops at adding items to the cart. Final checkout, payment, fulfilment selection, and order tracking happen inside the Kroger app or website - there is no public endpoint that submits an order.

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

Yes. Because you run Jentic One yourself, you decide which Kroger operations the agent may call, so you can grant only product search (GET /products) and store lookup (GET /locations) while withholding the cart-add operation (PUT /cart/add). Kroger enforces this at the OAuth scope level and its write targets travel in the request body, so the agent never gets the cart or identity operations unless your own rules add them. Your Kroger client id, secret, and refresh tokens stay under your control and are never placed in the agent's prompt or context.

Kroger API

AI ReadinessAI-Aware (B)63/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticE CommerceStorefrontoauth2,basic8 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search Kroger products, find nearby stores, look up the authenticated shopper's profile, and add items to their cart through OAuth-protected endpoints.

Use for: Search for organic milk on Kroger, Find the three nearest Kroger stores to ZIP 45202, Get product details for Kroger product ID 0001111041700, Add a list of grocery items to the shopper's Kroger cart

Not supported: Does not handle order checkout, payment, delivery routing, or loyalty redemption - use for product search, store location, identity, and cart-add only.

Jentic publishes the only available OpenAPI specification for Kroger API, keeping it validated and agent-ready. The Kroger Public API exposes 8 endpoints for searching products, looking up store locations across the Kroger family of supermarket banners, adding items to a shopper's cart, and reading the authenticated customer profile. Authentication uses OAuth 2.0 with both client-credentials and authorization-code flows, plus HTTP Basic for the token endpoint, so partner apps can mix anonymous product browsing with authenticated cart and identity calls. Kroger operates more than 2,700 stores in the United States, and the location endpoints accept ZIP, latitude/longitude, and chain filters.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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.

44%

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: DSignals: 4

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

88%

OperationId Quality

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

50%

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: D+Signals: 1

47%

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: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Kroger API to your agent

Capabilities

Start building with Kroger API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Kroger API

Jentic AI Readiness Score

Kroger 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