Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Keep Network website screenshot

Keep Network

Keep Network is a privacy-focused blockchain infrastructure project that merged with NuCypher in 2021 to form the Threshold Network. Its flagship product is tBTC, a decentralized, trust-minimized bridge that tokenizes Bitcoin as the TBTC ERC-20 token so it can be used across Ethereum DeFi without centralized custodians. Keep originally provided off-chain "keeps" — private data containers secured by a threshold ECDSA signing network and a random beacon — enabling confidential data to be used on public protocols. The developer surface is on-chain Solidity smart contracts plus first-party JavaScript/TypeScript client libraries published under the @keep-network npm scope; there is no hosted REST API. This profile was surfaced as a VC portfolio company and enriched from the project's public GitHub org, npm packages, blog, and security.txt.

human only

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.

Kin Score

API Evangelist profiles Keep Network the way a machine reads it — 2 machine-readable artifacts, 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 — Keep Network scores 11.4/100 (minimal), with a separate agent-readiness read of 7/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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 11.4/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 2.6 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 7/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 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 3 / 3

How we profile Keep Network

Each block below is one kind of artifact we hold for Keep Network. 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 2

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.

Keep Network Domain Security

TLSv1.3 · DMARC

SECURITY

Keep Network Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Every other property we hold for Keep Network — 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.

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Operate 1

Status, limits, changes, and where to get help

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/keep-network · machine-readable index on apis.io