Vespa
Limited coverage
Vespa's site sits behind a bot-verification wall. Security follows once the live pages open; the dimensions on this record that do not need them are filled.
Security Posture
Not yet observed
Security is read from Vespa's live pages, which Bixel is not yet cleared to read.
Security Change Historydated events · values unlock with a key
Security signal removed: GDPR · high significance
Security across Vector DatabasesVespa ranked in place · tap through for each read
No observed security facts yet for KDB.AI, LanceDB, Marqo, Milvus, MyScale and Vespa.
IdentityBixel ID · free forever
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 security for vespa.ai via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/vespa.ai/facts?dimension=security
{
"data": {
"facts": [
"…"
]
}
}MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "vespa.ai", dimension: "security" })
# returns the security record above,
# each value with its source_url + as_of,
# ready to reason overBuild on the company record. One key, REST + MCP, every signal dated and sourced back to the page it came from.
Public record, read from companies' own pages and boards. Every fact dated and sourced; provenance (observed vs company stated) shown inline.