Yext
Yext is a digital presence platform that enables businesses to manage their listings across 200+ publishers, update location data, manage reviews, and power AI search experiences. Its REST APIs provide programmatic access to the Knowledge Graph, Listings, Reviews, Analytics, and Content Delivery capabilities.
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 Yext the way a machine reads it — 40 machine-readable artifacts across 23 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 — Yext scores 54.1/100 (developing), with a separate agent-readiness read of 48/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.
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 Yext
Each block below is one kind of artifact we hold for Yext. 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 23
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.
Yext Account Settings API
The Account Settings API from Yext — 10 operation(s) for account settings.
Yext Accounts API
The Accounts API from Yext — 8 operation(s) for accounts.
Yext Administrative API API
NOTE: You need a sandbox account to test your Administrative API integration. Contact your Account Manager to have one created for you.
Yext Analytics API
The Analytics API from Yext — 4 operation(s) for analytics.
Yext Computations API
The Computations API from Yext — 2 operation(s) for computations.
Yext Configuration API
The Configuration API from Yext — 3 operation(s) for configuration.
Yext Connectors API
The Connectors API from Yext — 5 operation(s) for connectors.
Yext Content API API
The Content API API from Yext — 2 operation(s) for content api.
Yext Domains API
The Domains API from Yext — 7 operation(s) for domains.
Yext Health Check API
The Health Check API from Yext — 1 operation(s) for health check.
Yext Knowledge Manager API
The Knowledge Manager API from Yext — 30 operation(s) for knowledge manager.
Yext Licenses API
The Licenses API from Yext — 3 operation(s) for licenses.
Yext Listings API
The Listings API from Yext — 26 operation(s) for listings.
Yext Lists API
The Lists API from Yext — 1 operation(s) for lists.
Yext Live API API
The Live API API from Yext — 21 operation(s) for live api.
Yext LogsAPI API
The LogsAPI API from Yext — 3 operation(s) for logsapi.
Yext Optimization Tasks API
The Optimization Tasks API from Yext — 2 operation(s) for optimization tasks.
Yext Plpixel API
The Plpixel API from Yext — 1 operation(s) for plpixel.
Yext Publisher Disruptions API
The Publisher Disruptions API from Yext — 2 operation(s) for publisher disruptions.
Yext Webhooks API
The Webhooks API from Yext — 0 operation(s) for webhooks.
Yext Reviews API
The Reviews API from Yext — 14 operation(s) for reviews.
Yext Social API
The Social API from Yext — 10 operation(s) for social.
Yext Suggestions API
The Suggestions API from Yext — 2 operation(s) for suggestions.
Scroll within the panel for all 23 ·
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.
Yext 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.
Yext 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.
Yext Finops
FINOPSSemantic 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.
Yext Context
JSON-LDSpectral Rules 1
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.
Yext API Rules
SPECTRALJSON Schema 4
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.
Yext Address
JSON SCHEMAYext Entity
JSON SCHEMAYext Hours
JSON SCHEMAYext Search Query Response
JSON SCHEMAExamples 5
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.
Yext Chat Message Example
EXAMPLEYext Listing Status Example
EXAMPLEYext Location Entity Example
EXAMPLEYext Search Query Example
EXAMPLESecurity 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 Yext — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
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/yext · machine-readable index on apis.io