Albertsons
Albertsons Companies is one of the largest food and drug retailers in the United States, operating supermarkets and pharmacies under banners including Albertsons, Safeway, Vons, Jewel-Osco, Acme, Shaw's, Star Market, and others. The company operates the Albertsons Media Collective, a retail media network that provides advertisers API access to near-real-time campaign performance data and audience targeting capabilities based on shopper purchase behavior across its banner network.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Albertsons the way a machine reads it — 63 machine-readable artifacts across 4 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 — Albertsons scores 28.3/100 (thin), with a separate agent-readiness read of 31/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
The Albertsons Media Collective API announced 2025-01-07 is issued only inside an advertising agreement, and the Azure API Management developer portal that fronted it is gone — the entire stratus.albertsons.com DNS zone now returns SERVFAIL from every public resolver, and the recorded base host api.albertsons.com is a stale record pointing at a decommissioned MyWebGrocer address with TCP 80 and 443 filtered, so there is no public reference or spec left to read.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Albertsons's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://portal-prod.apim.azwestus.stratus.albertsons.com/→ HTTP 0https://api.albertsons.com/openapi.json→ HTTP 0https://www.albertsons.com/llms.txt→ HTTP 404https://www.albertsonsmediacollective.com/openapi.json→ HTTP 404https://www.albertsonsmediacollective.com/.well-known/agent-card.json→ HTTP 200
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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Albertsons's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/albertsons/"
title="Albertsons on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/albertsons.svg"
alt="Albertsons Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/albertsons/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/albertsons/"
title="Albertsons on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/albertsons/card.svg"
alt="Albertsons Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Albertsons
Each block below is one kind of artifact we hold for Albertsons. 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 4
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.
albertsons Audiences API
Manage audience targeting segments for retail media campaigns.
albertsons Campaigns API
Manage advertising campaigns on the Albertsons Media Collective.
albertsons Performance API
Access campaign performance metrics and analytics.
albertsons Reporting API
Generate and retrieve performance reports.
Open Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAlbertsons Media Collective Audiences API
OPEN COLLECTIONAlbertsons Media Collective Audiences Campaigns API
OPEN COLLECTIONAlbertsons Media Collective Audiences Performance API
OPEN COLLECTIONAlbertsons Media Collective Audiences Reporting API
OPEN COLLECTIONAlbertsons Media Collective API
OPEN COLLECTIONPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate 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.
Albertsons 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.
Albertsons Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Near-Real-Time Campaign Performance
Access advertising campaign performance data in near-real-time to bring metrics into custom dashboards and measurement models.
Audience Targeting
Target campaigns using audience segments derived from Albertsons shopper purchase behavior across grocery and pharmacy banners.
Campaign Management
Create, update, and manage advertising campaigns with budget controls, scheduling, and audience targeting configurations.
Custom Reporting
Generate configurable performance reports with custom dimensions and metrics for export to external analytics tools.
Azure API Management Portal
Interactive developer portal built on Microsoft Azure API Management with documentation, code samples, and an API testing console.
Multi-Banner Reach
Access to shopper audiences across Albertsons, Safeway, Vons, Jewel-Osco, Acme, and other banner networks.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Albertsons API Rules
SPECTRALAlbertsons API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Audience List Response
JSON SCHEMAAudience
JSON SCHEMACampaign List Response
JSON SCHEMACampaign
JSON SCHEMACreate Campaign Request
JSON SCHEMAError Response
JSON SCHEMAPerformance Metric
JSON SCHEMAPerformance Metrics Response
JSON SCHEMAReport Request
JSON SCHEMAReport Response
JSON SCHEMAScroll within the panel for all 10 ·
JSON Structure 10
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Retail Media Api Audience List Response Structure
JSON STRUCTURERetail Media Api Audience Structure
JSON STRUCTURERetail Media Api Campaign List Response Structure
JSON STRUCTURERetail Media Api Campaign Structure
JSON STRUCTURERetail Media Api Create Campaign Request Structure
JSON STRUCTURERetail Media Api Error Response Structure
JSON STRUCTURERetail Media Api Performance Metric Structure
JSON STRUCTURERetail Media Api Performance Metrics Response Structure
JSON STRUCTURERetail Media Api Report Request Structure
JSON STRUCTURERetail Media Api Report Response Structure
JSON STRUCTUREScroll within the panel for all 10 ·
Examples 10
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 10 ·
Security Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Campaign Performance Dashboards
Pull near-real-time campaign metrics into custom brand or agency dashboards for monitoring impressions, clicks, and ROAS.
Automated Budget Optimization
Integrate campaign performance data into automated bidding and budget allocation systems.
Third-Party Measurement Integration
Share campaign performance data with measurement partners like TransUnion for attribution and audience analysis.
Media Mix Modeling
Incorporate Albertsons retail media performance data into multi-channel media mix models.
Audience Insights
Analyze shopper audience segments to inform product marketing strategy and campaign targeting decisions.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
TransUnion
Partnership integration for enhanced audience measurement and identity resolution using TransUnion data.
Microsoft Azure
Developer portal and API gateway infrastructure built on Microsoft Azure API Management.
Analytics Platforms
Export campaign data to third-party analytics dashboards and reporting tools via the Performance API.
Resources
Every other property we hold for Albertsons — 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 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/albertsons · machine-readable index on apis.io
This is an independent, third-party profile of Albertsons, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.