Bazaarvoice
Bazaarvoice operates a retail and brand user-generated-content network that collects, moderates, and syndicates ratings, reviews, questions and answers, and product-sampling content across thousands of brand and retailer sites. Its developer platform exposes a family of APIs - the flagship Conversations API for retrieving and submitting UGC, the V2.0 Content Search API for searching reviews/questions/answers/contributors and product catalog lookahead, plus the Transactions, Response, Social Commerce, and Authentic Discovery APIs, and structured-data (JSON-LD/Microdata) endpoints for SEO. APIs authenticate with a Bazaarvoice Portal-managed passkey (Bv-Passkey header) or, for the Transactions and Response APIs, 2-legged OAuth2 client credentials. Official iOS, Android, SEO, Magento, and Salesforce Commerce SDKs are published on GitHub.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Bazaarvoice the way a machine reads it — 11 machine-readable artifacts across 6 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 — Bazaarvoice scores 50.3/100 (developing), with a separate agent-readiness read of 72/100 (agent native). 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.
How we profile Bazaarvoice
Each block below is one kind of artifact we hold for Bazaarvoice. 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 6
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.
Bazaarvoice Answers API
The Answers API from Bazaarvoice — 1 operation(s) for answers.
Bazaarvoice Clients API
The Clients API from Bazaarvoice — 1 operation(s) for clients.
Bazaarvoice Contributor API
The Contributor API from Bazaarvoice — 3 operation(s) for contributor.
Bazaarvoice Lookahead API
The Lookahead API from Bazaarvoice — 1 operation(s) for lookahead.
Bazaarvoice Questions API
The Questions API from Bazaarvoice — 4 operation(s) for questions.
Bazaarvoice Reviews API
Search for reviews
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
bazaarvoice-mcp.yml
MCP SERVERRate 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.
Bazaarvoice Rate Limits
RATE LIMITSSecurity 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.
Resources
Every other property we hold for Bazaarvoice — 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 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bazaarvoice · machine-readable index on apis.io