Hyperprobe
Hyperprobe is a runtime data platform for AI-native software development, built by a San Francisco team in Y Combinator's Summer 2026 batch. It lets developers and coding agents (Cursor, Claude Code, Codex, opencode, Windsurf) set live, non-breaking breakpoints in running production services directly from the IDE — capturing exact variable snapshots, injecting logs, and tracing call stacks without pausing threads, redeploying, or changing source code. Probes are read-only and non-blocking with under 1% overhead, and PII is redacted in-process before any data leaves the container's memory boundary (password, secret, token, authorization, cookie, key, signature, ssn and creditCard patterns are masked by default). Hyperprobe ships in-process SDKs for Node.js (@hyperprobe/node-sdk), Java (a bytecode-instrumentation agent), and Python (hyperprobe-agent), a VS Code extension, and an official Model Context Protocol (MCP) server (@hyperprobe/mcp-server) that lets AI assistants autonomously register conditional probes and read real runtime evidence instead of flat logs. The platform can run fully self-hosted via Docker Compose. Originally added to the API Evangelist network as a Y Combinator portfolio lead, this profile has been enriched from Hyperprobe's public developer surface.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Hyperprobe 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 — Hyperprobe scores 19.4/100 (emerging), with a separate agent-readiness read of 15/100 (agent aware). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Hyperprobe
Each block below is one kind of artifact we hold for Hyperprobe. 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.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
hyperprobe-mcp.yml
MCP SERVERSecurity 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 Hyperprobe — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hyperprobe · machine-readable index on apis.io