Qpoint

Qpoint is a security and observability company that uses eBPF to give teams full visibility and control over egress and service-to-service traffic without proxies, sidecars, or code changes. Its product line includes qtap (a lightweight eBPF sensor that captures pre-encrypted HTTPS traffic and the originating process context), Qplane (a cloud-managed control plane and dashboard), qscan (an artifact/PII scanner), and qcontrol (agentic-AI security controls, in beta). Qpoint exposes its telemetry through a Connect RPC / gRPC data plane, a hosted Model Context Protocol (MCP) server for AI agents, plugin SDKs in Rust, C, and Zig, and OpenTelemetry/Prometheus integrations. Backed by Bloomberg Beta and Uncork Capital.

Qpoint is listed with 1 API on the APIs.io network. Tagged areas include Company, Security, Observability, eBPF, and Network Traffic.

Qpoint’s developer surface includes documentation, getting-started guide, quickstart, engineering blog, pricing, signup flow, CLI, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

36.1/100 thin ▬ flat Agent 19/100 agent aware Front door AI 6/6 dominant Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers

Company Security Observability eBPFNetwork TrafficEgress ControlAI Agents MCP gRPC

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 36.1/100 · thin

Contract Quality 5.1 / 21

Developer Ergonomics 11.3 / 17

Access Clarity 3.1 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 3.2 / 15

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 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 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/qpoint/"><img src="https://apis.io/badge/qpoint/card.svg" alt="Qpoint on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 24.0 — up to +19.0 composite points
Access Clarity scores 18.4 — up to +16.3 composite points
Operational Transparency scores 18.4 — up to +10.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/qpoint/apis.yml: open an issue on github.com/api-evangelist/qpoint to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Buf Schema Registry (public Protocol Buffers modules, gRPC / ConnectRPC schema publishers)	distribution	9.6 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

gRPC

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

APIs 1

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

Qpoint Data Plane (Connect/gRPC)

Connect RPC / gRPC services backing Qpoint's control plane: an event store service and the qscan scheduler service, with shared protobuf types for connections, requests, issues,...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Qpoint MCP Server

Remote MCP server at pulse.qpoint.io over HTTP.

MCP SERVER

Security Posture 2

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

Qpoint Authentication

http-bearer/apiKey/oauth2 · 3 schemes

SECURITY

Qpoint Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

Quickstart

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

CLI

SDKs

Packages

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Compliance

Compliance

Operate 1

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

Pricing

Pricing

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: qpoint
name: Qpoint
description: Qpoint is a security and observability company that uses eBPF to give teams full visibility and control over
  egress and service-to-service traffic without proxies, sidecars, or code changes. Its product line includes qtap (a lightweight
  eBPF sensor that captures pre-encrypted HTTPS traffic and the originating process context), Qplane (a cloud-managed control
  plane and dashboard), qscan (an artifact/PII scanner), and qcontrol (agentic-AI security controls, in beta). Qpoint exposes
  its telemetry through a Connect RPC / gRPC data plane, a hosted Model Context Protocol (MCP) server for AI agents, plugin
  SDKs in Rust, C, and Zig, and OpenTelemetry/Prometheus integrations. Backed by Bloomberg Beta and Uncork Capital.
url: https://raw.githubusercontent.com/api-evangelist/qpoint/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bloomberg-beta
- uncork-capital
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  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-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
image: https://www.qpoint.io/favicon.svg
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Company
- Security
- Observability
- eBPF
- Network Traffic
- Egress Control
- AI Agents
- MCP
- gRPC
tags_raw:
- Company
- Security
- Observability
- eBPF
- Network Traffic
- Egress Control
- Agentic AI
- MCP
- gRPC
apis:
- name: Qpoint Data Plane (Connect/gRPC)
  description: 'Connect RPC / gRPC services backing Qpoint''s control plane: an event store service and the qscan scheduler
    service, with shared protobuf types for connections, requests, issues, PII, and tags.'
  humanURL: https://docs.qpoint.io/
  baseURL: https://api.qpoint.io
  properties:
  - type: Protobuf
    name: EventStore v1 (proto)
    url: grpc/qpoint-eventstore-v1-main.proto
  - type: Protobuf
    name: Qscan v1 Scheduler (proto)
    url: grpc/qpoint-qscan-v1-main.proto
  - type: APIReference
    url: https://docs.qpoint.io/appendix/qpoint-data-schema-reference.md
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.qpoint.io/
- type: DeveloperPortal
  url: https://docs.qpoint.io/
- type: Documentation
  url: https://docs.qpoint.io/
- type: GettingStarted
  url: https://docs.qpoint.io/getting-started
- type: Quickstart
  url: https://docs.qpoint.io/guides/qtap-guides/getting-started/qtap-starter-configuration-stdout-only.md
- type: GitHubOrganization
  url: https://github.com/qpoint-io
- type: Blog
  url: https://www.qpoint.io/blog/
- type: Pricing
  url: https://www.qpoint.io/pricing/
- type: SignUp
  url: https://app.qpoint.io/
- type: MCPServer
  url: mcp/qpoint-mcp.yml
- type: CLI
  url: cli/qpoint-cli.yml
- type: SDKs
  url: packages/qpoint-packages.yml
- type: Packages
  url: packages/qpoint-packages.yml
- type: Authentication
  url: authentication/qpoint-authentication.yml
- type: DomainSecurity
  url: security/qpoint-domain-security.yml
- type: Conformance
  url: conformance/qpoint-conformance.yml
- type: Compliance
  url: https://docs.qpoint.io/security-and-compliance.md
- type: Lifecycle
  url: lifecycle/qpoint-lifecycle.yml
- type: ChangeLog
  url: changelog/qpoint-changelog.yml
- type: LLMsTxt
  url: llms/qpoint-llms.txt
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 20
  pass: local-v1

Qpoint API — frequently asked questions

Does Qpoint have an API?

Yes. APIs.io lists 1 API from Qpoint, including Qpoint Data Plane (Connect/gRPC).

How do I authenticate with the Qpoint API?

Qpoint uses bearer-token authentication (http-bearer/apiKey/oauth2 · 3 schemes). The details are profiled on APIs.io as Qpoint Authentication.

Does Qpoint have an MCP server?

Yes. APIs.io lists 1 MCP server for Qpoint: Remote MCP server at pulse.qpoint.io over HTTP.

Is the Qpoint API ready for AI agents?

Qpoint has a Kin Score of 36.1 out of 100 (thin) and an Agent Readiness score of 18.9 (agent-aware), scored by API Evangelist on 2026-11-06.

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/qpoint"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.