Vespa

Vespa.ai AS·Vespa.ai
Limited coverage

Vespa's site sits behind a bot-verification wall that Bixel does not evade. Coverage is limited to signals observable off-site (job postings, DNS, subdomain surfaces) until BixelBot's verified-bot admission clears.

Company Overview

As of October 30, 2026: Vespa is an AI search platform.

It has baseline security.

Backed by 57 dated facts
Drawn from 7 dimensions of the record, each dated and sourced.
The record, by dimensionevery dimension is its own page →
FeaturesBacked by 32 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Hybrid search platform
25 stated capabilities incl. hybrid search, RAG, and reranking, 7 integrations.
Full features read →
Change History97 dated events on the record
Feature added: Multi Phase Ranking
Feature added: BYOC
Feature added: Continuous Deployment
Feature added: Distributed Search
Feature added: BM25
Feature added: Dynamic Snippets
Feature added: Fully Managed
IdentityBixel ID · free forever
Bixel IDbxc_txnhv0ksnh0xbrandID in service · identity is free forever · permalink
Operated by

No registered company joined yet. Would resolve with: a registry identifier for the entity; a legal page on the site naming the registered company.

Registry identifiers

None on record.

Published identifiers
  • GitHub vespa-engine · inferred
  • LinkedIn vespa-ai · corroborated
  • X vespaengine · corroborated
  • YouTube channel/UCVXw_f6UHff8-V9FA1LMIiw · inferred
Get this record via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/vespa.ai

{
  "data": {
    "company": {
      "name": "Vespa",
      "domain": "vespa.ai",
      "categories": [
        "vector-databases"
      ]
    },
    "dimensions": {
      "stack": {
        "facts": [
          {
            "key": "stack.tech.aws",
            "value": true,
            "provenance": "observed",
            "as_of": "2026-10-30",
            "source_url": "trust.vespa.ai"
          }
        ]
      },
      "…": "…"
    }
  }
}
MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company({ domain: "vespa.ai" })

# returns the whole record above,
# each value with its source_url + as_of,
# ready to reason over
Build on the company record. One key, REST + MCP, every signal dated and sourced back to the page it came from.
How Bixel reads this

Every read above is derived from public signals, each sourced and dated, and kept honest about provenance: what the company states on its own pages and job posts (pricing, security, careers, positioning, its backend stack) versus what Bixel independently detects (technologies, infrastructure). Where a stated claim is also detected we mark it verified; where we only have the claim, we say so. Bixel infers posture: how it monetizes, how mature it is, where it's heading. It does notclaim private financials it can't observe. Where signals are thin, the record says so.

Public record, read from companies' own pages and boards. Every fact dated and sourced; provenance (observed vs company stated) shown inline.