Keybase

Keybase is an end-to-end encrypted messaging, file-sharing, and key-directory platform built on public-key cryptography, founded by Chris Coyne and Max Krohn and acquired by Zoom in 2020. It maps human-readable usernames to public keys and cryptographically verifiable social-identity proofs (Twitter, GitHub, Reddit, Hacker News, personal domains, and cryptocurrency addresses), and provides encrypted chat, teams, KBFS encrypted filesystem, git, and a wallet. Keybase exposes a public read-oriented HTTP JSON API (version 1.0) at keybase.io/_/api/1.0 for user lookup, PGP key fetch, Merkle-tree verification, and session/signature auth, plus officially supported chat-bot SDKs for Node.js, Python, and Go that script the local keybase client and CLI.

Keybase publishes 1 API on the APIs.io network. Tagged areas include Company, Security, Encryption, Cryptography, and Identity.

Keybase’s developer surface includes documentation, API reference, engineering blog, support, CLI, and 9 more developer resources.

🌐 Visit website 📡 Source on GitHub

22.1/100 emerging ▬ flat Agent 6/100 agent aware library Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Security Encryption Cryptography Identity Messaging Key ManagementPGPDeveloper Tools

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 22.1/100 · emerging

Contract Quality 0.0 / 25

Developer Ergonomics 12.3 / 20

Access Clarity 0.0 / 20

Operational Transparency 1.7 / 13

Contract Governance 0.5 / 12

Discoverability 7.6 / 10

Agent readiness — 6/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/keybase: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Keybase API

Keybase public HTTP JSON API (v1.0). Read-oriented endpoints for user lookup and discovery by social proof, PGP public-key fetch, Merkle-tree root and block retrieval for verifi...

Security Posture 2

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

Keybase Authentication

session-token/signature-based · 2 schemes

SECURITY

Keybase Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 2

Authentication, authorization, and security posture

Security

Security

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

ParentCompany

ParentCompany

Source (apis.yml)

aid: keybase
name: Keybase
description: Keybase is an end-to-end encrypted messaging, file-sharing, and key-directory platform built on public-key cryptography,
  founded by Chris Coyne and Max Krohn and acquired by Zoom in 2020. It maps human-readable usernames to public keys and cryptographically
  verifiable social-identity proofs (Twitter, GitHub, Reddit, Hacker News, personal domains, and cryptocurrency addresses),
  and provides encrypted chat, teams, KBFS encrypted filesystem, git, and a wallet. Keybase exposes a public read-oriented
  HTTP JSON API (version 1.0) at keybase.io/_/api/1.0 for user lookup, PGP key fetch, Merkle-tree verification, and session/signature
  auth, plus officially supported chat-bot SDKs for Node.js, Python, and Go that script the local keybase client and CLI.
url: https://raw.githubusercontent.com/api-evangelist/keybase/refs/heads/main/apis.yml
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://keybase.io/images/icons/icon-keybase-logo-48.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Security
- Encryption
- Cryptography
- Identity
- Messaging
- Key Management
- PGP
- Developer Tools
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Keybase API
  description: Keybase public HTTP JSON API (v1.0). Read-oriented endpoints for user lookup and discovery by social proof,
    PGP public-key fetch, Merkle-tree root and block retrieval for verification, and the salt/login/session and signature-posting
    flow. All responses use a status envelope of {code, name}; the API supports CORS.
  humanURL: https://keybase.io/docs/api/1.0
  baseURL: https://keybase.io/_/api/1.0
  tags:
  - Identity
  - Cryptography
  - Key Management
  properties:
  - type: Authentication
    url: authentication/keybase-authentication.yml
  - type: Conventions
    url: conventions/keybase-conventions.yml
  - type: ErrorCatalog
    url: errors/keybase-problem-types.yml
  - type: DataModel
    url: data-model/keybase-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/keybase-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: AgentSkill
    url: skills/_index.yml
  - type: Conformance
    url: conformance/keybase-conformance.yml
  - type: Lifecycle
    url: lifecycle/keybase-lifecycle.yml
common:
- type: Website
  url: https://www.keybase.io/
- type: ParentCompany
  url: https://apis.io/providers/zoom/
  name: Zoom
  x-relationship: acquired
  x-evidence: Keybase is an end-to-end encrypted messaging, file-sharing, and key-directory platform built on public-key cryptography,
    founded by Chris Coyne and Max Krohn and acquired by Zoom in 2020.
- type: DeveloperPortal
  url: https://keybase.io/docs
- type: Documentation
  url: https://keybase.io/docs
- type: APIReference
  url: https://keybase.io/docs/api/1.0
- type: Blog
  url: https://keybase.io/blog
- type: GitHubOrganization
  url: https://github.com/keybase
- type: Support
  url: https://keybase.io/docs/bug_reporting
- type: Security
  url: https://keybase.io/docs/secadv
- type: Packages
  url: packages/keybase-packages.yml
- type: SDKs
  url: packages/keybase-packages.yml
- type: CLI
  url: cli/keybase-cli.yml
- type: LLMsTxt
  url: llms/keybase-llms.txt
- type: DomainSecurity
  url: security/keybase-domain-security.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 13
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/keybase"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/keybase/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/keybase/evidence"

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.