Landvault
Landvault was surfaced as a portfolio company of Speedinvest and added to the API Evangelist network as a stub awaiting enrichment. Enrichment probing on 2026-07-19 found no operating company surface: the landvault.io domain of record resolves to a GoDaddy parking page rather than a website, serving a /lander redirect stub for every path, with no MX records and only a registrar-default DMARC record. The landvault.xyz variant redirects to a GoDaddy for-sale listing. No developer portal, documentation, API reference, OpenAPI definition, SDK, package-registry presence, or GitHub organization could be verified. This profile is retained as a dead lead with recorded probe evidence so the enrichment pipeline does not repeatedly re-attempt it.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Landvault the way a machine reads it — 1 machine-readable artifact, 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 — Landvault scores 6.8/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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.
How we profile Landvault
Each block below is one kind of artifact we hold for Landvault. 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.
Security Posture 1
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.
Resources
Every other property we hold for Landvault — 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.
Access & Security 1
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/landvault · machine-readable index on apis.io