Vercel is a cloud platform that helps developers build, deploy, and scale modern web applications quickly and efficiently. It provides an optimized hosting environment for frontend frameworks like Next.js (which it created), as well as other React, Vue, Angular, and static site projects. Vercel automates workflows for continuous deployment, edge caching, and serverless functions, so developers can push code changes and see them live almost instantly.
Vercel publishes 6 APIs on the APIs.io network, including Webhooks, Chat API, Chats API, and 3 more. Tagged areas include AI Gateway, Gateways, Observability, Webhook, and Serverless.
The Vercel catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 3 Spectral governance rulesets.
Vercel’s developer surface includes authentication, engineering blog, changelog, documentation, support, pricing, signup flow, and 40 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/vercel: open an issue to ask a question, or submit a pull request to add artifacts.
Submit an artifact on GitHub — free →Manage your own listing — the Influence plan, $499/mo →
Vercel is an area vendor: providers adopt it to run part of their developer surface. This is the Kin Score checks its features can move for a provider that adopts it, what each one really earns, and what it earns nothing for.
mcp hostinghostingmeasured7 features checked 2026-09-25 · rubric v0.22.0
Hosting on Vercel moves no Kin Score check by itself. What it does is make a provider’s own agent surfaces cheap to ship: mcp-handler runs an MCP server the provider writes on the provider’s own domain, with a helper that serves /.well-known/oauth-protected-resource, and any llms.txt or .well-known file is just a route or a static file. Those points are earned by the provider’s server and files, graded on what the provider builds; the only surface Vercel’s own code generates for a customer, the vercel.shop template forwarding Shopify’s UCP, is a platform surface and grades platform.
Agent Readiness22.2 of 139 pts
Discoverability10.0 of 54 pts
Check
Earns
Through
Well-Known Catalog Agent Readiness · customers +1.8 pts vs controlPublish the well-known documents AND declare them (WellKnown / APICatalog) in common[] of its apis.yml — the dimension reads the pointer, not the host.
Serves a .well-known surface Discoverability · customers +0.6 pts vs controlWrite and serve an api-catalog linkset, security.txt or protected-resource document under /.well-known on its own domain; Vercel serves whatever route the provider writes, nothing by default.
Publishes llms.txt Discoverability · customers +13.3 pts vs controlWrite the llms.txt itself and ship it as a static file or route. Vercel generates none; the vercel.shop template’s generated file would be derived (0.25), not the provider’s own.
MCP Serverconditional Agent Readiness · customers +17.9 pts vs controlOnly if the provider has an API or data to expose and writes the server’s tools itself — mcp-handler is a transport adapter, and the docs’ example tool rolls a die. A server built this way is the provider’s own server on the provider’s domain.
Protected Resource Metadataconditional Agent Readiness · customers +9.0 pts vs controlOnly if the provider already operates an OAuth authorization server — the helper publishes metadata naming it; it cannot supply one.
Agentic Commerce Well-Known Documentconditional Agent Readiness · customers -0.2 pts vs controlOnly for a Shopify merchant who deploys the vercel.shop template.
127 detected customers vs 5089 comparable providers: composite 50.0 vs 48.0, agent readiness 36.0 vs 32.4. Association, not cause.
Across 8977 providers that publish a contract, adopting Vercel would move 8920. Median lift: composite +1.2 (90th percentile +1.9), agent readiness +2.9 (+3.3). Conditional rows excluded.
What Vercel ships that earns nothing (2)
Bot verification with Web Bot Auth — Vercel verifies signatures on INBOUND bot traffic at its edge; the dimension reads a provider-declared AIPREF / ContentSignal / WebBotAuth posture, and edge verification publishes nothing.
Markdown content negotiation pattern — Serving text/markdown on Accept is a different surface from llms.txt; no check reads content negotiation.
A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership can. The rating is not for sale → · Full vendor facets artifact
Interfaces this provider implements that became standards by being copied rather than ratified. Each is profiled by the API Commons, and the evidence column says how the claim was established — not that it was made.
Vercel Webhooks deliver platform events to a subscriber-configured HTTPS endpoint via HTTP POST with a JSON body. Subscriptions are created as Account Webhooks (Team Settings) o...
AsyncAPI definition for Vercel's webhook surface. Vercel webhooks are HTTP POST deliveries from Vercel to a subscriber-configured endpoint URL registered either as an Account We...
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →