Vespa · Rate Limits

Vespa Ai Rate Limits

Vespa serving throughput is governed by application configuration (per-container HTTP threads, document API concurrency, query timeout) rather than a fixed per-key request quota. The values below reflect Vespa's default protection mechanisms and Vespa Cloud guidance.

Vespa Ai Rate Limits is the machine-readable rate-limit profile for Vespa on the APIs.io network, in the API Commons Rate Limits shape.

It captures 6 rate-limit definitions, measuring queries_per_second, writes_per_second, concurrent, seconds, and documents.

Limit state is signalled in the retryAfter response header, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes response codes documented for throttled, serverError, and timeout.

Tagged areas include Rate Limiting, AI Search, and Vector Database.

6 Limits Exhausted: HTTP 429 retryAfter
Method: generated, dated 2026-05-25.
Written by API Evangelist on 2026-05-25 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingAI SearchVector Database

Limits

Query throughput cluster
queries_per_second
scales with container cluster size
Tune feed/query container resources and search threads per query to scale.
Document API throughput cluster
writes_per_second
scales with content cluster size
Vespa Cloud customers typically achieve tens of thousands of writes per second per content cluster.
In-flight document operations container
concurrent
bounded by container thread pool
Returns HTTP 429 when the per-container in-flight limit is exceeded.
Default query timeout request
seconds · request
500
Default query timeout is 500ms; configurable per request via the `timeout` parameter.
Default feed timeout request
seconds · request
180
Default feed timeout is 180s; configurable per request.
Visit batch request
documents · request
wantedDocumentCount
Visit operations are paginated via the `continuation` token; batch sizing is governed by `wantedDocumentCount`.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/vespa-ai-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.