Vault12

Vault12 is a non-custodial crypto asset security company whose Vault12 Guard mobile app backs up wallet seed phrases and private keys using Shamir's Secret Sharing across a decentralized network of appointed Guardians, with designated legacy contacts for crypto inheritance — no cloud storage and no custody of funds. Its developer surface is open source, centered on the Zax NaCl-based cryptographic relay (asynchronous end-to-end-encrypted device-to-device messaging and file exchange), the glow.ts client library, and native Shamir's Secret Sharing implementations, plus RFC 8414 OAuth 2.0 authorization-server metadata published on vault12.com and a public Zax test relay at zt.vault12.com.

Vault12 publishes 1 API on the APIs.io network. Tagged areas include Company, Cryptocurrency, Security, Backup, and Inheritance.

Vault12’s developer surface includes engineering blog, support, pricing, authentication, sandbox, changelog, and 13 more developer resources.

26.4/100 emerging ▬ flat Agent 14/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs
CompanyCryptocurrencySecurityBackupInheritanceWalletsCryptographySecret SharingKey Management

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 26.4/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 6.1 / 20
Commercial Clarity 6.3 / 20
Operational Transparency 4.8 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 14/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/vault12: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Vault12 Zax Cryptographic Relay API

Open-source NaCl-based cryptographic relay operated as asynchronous "dead drops" for end-to-end-encrypted device-to-device communication. Clients establish anonymous session key...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Vault12 Authentication

oauth2/session-handshake · 2 schemes

SECURITY

Vault12 Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Vault12 Scopes

4 scopes · authorizationCode/implicit/password/refresh_token

4 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: vault12
name: Vault12
description: Vault12 is a non-custodial crypto asset security company whose Vault12 Guard mobile app backs up wallet seed
  phrases and private keys using Shamir's Secret Sharing across a decentralized network of appointed Guardians, with designated
  legacy contacts for crypto inheritance — no cloud storage and no custody of funds. Its developer surface is open source,
  centered on the Zax NaCl-based cryptographic relay (asynchronous end-to-end-encrypted device-to-device messaging and file
  exchange), the glow.ts client library, and native Shamir's Secret Sharing implementations, plus RFC 8414 OAuth 2.0 authorization-server
  metadata published on vault12.com and a public Zax test relay at zt.vault12.com.
url: https://raw.githubusercontent.com/api-evangelist/vault12/refs/heads/main/apis.yml
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://assets.rbl.ms/27528763/origin.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- dcvc
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 11
  pass: local-v1
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Cryptocurrency
- Security
- Backup
- Inheritance
- Wallets
- Cryptography
- Secret Sharing
- Key Management
apis:
- name: Vault12 Zax Cryptographic Relay API
  description: Open-source NaCl-based cryptographic relay operated as asynchronous "dead drops" for end-to-end-encrypted device-to-device
    communication. Clients establish anonymous session keys via a proof-of-work handshake (POST /start_session, /verify_session)
    and then post encrypted commands to /command — upload, count, download, messageStatus, delete, plus the Zax 2.0 file-command
    family (startFileUpload, uploadFileChunk, downloadFileChunk, fileStatus, deleteFile). Vault12 maintains a public test
    relay with 30-minute message expiration.
  humanURL: https://github.com/vault12/zax
  baseURL: https://zt.vault12.com
  tags:
  - Relay
  - Cryptography
  - Messaging
  - File Exchange
  properties:
  - type: Documentation
    url: https://github.com/vault12/zax
  - type: APIReference
    url: https://s3-us-west-1.amazonaws.com/vault12/crypto_relay.pdf
  - type: SourceCode
    url: https://github.com/vault12/zax
  - type: Sandbox
    url: https://zt.vault12.com
common:
- type: DomainSecurity
  url: security/vault12-domain-security.yml
- type: Website
  url: https://vault12.com
- type: Blog
  url: https://vault12.com/blog/
- type: Support
  url: https://vault12.com/help/
- type: Pricing
  url: https://vault12.com/pricing/
- type: TermsOfService
  url: https://vault12.com/terms/
- type: PrivacyPolicy
  url: https://vault12.com/privacy/
- type: StatusPage
  url: https://status.vault12.com/
- type: GitHubOrganization
  url: https://github.com/vault12
- type: Packages
  url: packages/vault12-packages.yml
- type: SDKs
  url: packages/vault12-packages.yml
- type: WellKnown
  url: well-known/vault12-well-known.yml
- type: OAuthScopes
  url: scopes/vault12-scopes.yml
- type: Authentication
  url: authentication/vault12-authentication.yml
- type: Conformance
  url: conformance/vault12-conformance.yml
- type: LLMsTxt
  url: llms/vault12-llms.txt
- type: Sandbox
  url: sandbox/vault12-sandbox.yml
- type: Lifecycle
  url: lifecycle/vault12-lifecycle.yml
- type: ChangeLog
  url: changelog/vault12-changelog.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io