Kroger
Partner APIs related to integrating with a full-service delivery partner.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Kroger the way a machine reads it — 18 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Kroger scores 17.2/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Kroger
Each block below is one kind of artifact we hold for Kroger. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Kroger Authorization API (Partners)
The authorization endpoints provide a token that will allow your service or application to call Kroger APIs.
Kroger Authorization API (Public)
The authorization endpoints provide a token that will allow your service or application to call Kroger APIs.
Kroger Cart API (Partner)
The Carts API provides access to create, view, and update a customers cart.
Kroger Cart API (Public)
The Cart API allows you to add an item to an authenticated customers cart.
Kroger Catalog API
Catalog API integration let partners to access Krogers catalog data via available product endpoints. The catalog can be customized for the partners based on their needs and requ...
Kroger Catalog API V2
Catalog API integration let partners to access Krogers catalog data via available product endpoints. The catalog can be customized for the partners based on their needs and requ...
Kroger Identity API
The Identity API provides access to the profile information of an authenticated Kroger customer.
Kroger Identity API (Public)
The Identity API allows you to access the profile ID of an authenticated customer.
Kroger Location API (Partner)
Partner APIs enable official partners to access strategic functionality and data. Since the needs of our partners determine our Partner APIs, they are not open for public consum...
Kroger Location API (Public)
The Locations API provides access to all locations, chains, and departments that are owned by The Kroger Co.
Kroger Products API (Partners)
The Products API allows you to search the Kroger product catalog.Pagination.
Kroger Products API (Public)
The Products API allows you to search the Kroger product catalog.
Kroger Seamless Delivery API
Partner APIs related to integrating with a full-service delivery partner.
Kroger Locker Integration APIs (Partners)
This contract outlines the APIs agreement for vendors seeking integration with Kroger as a locker vendor. The provided APIs enable partners to transmit unattended locker pickup ...
Scroll within the panel for all 14 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Kroger Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Kroger Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Kroger Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Kroger — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/kroger · machine-readable index on apis.io