# HTTP/2

**Canonical:** https://apis.io/providers/http-2/  
**Website:** https://http2.github.io/  
**APIs profiled:** 0

HTTP/2 is the second major version of the Hypertext Transfer Protocol, defined by the IETF in RFC 7540 and standardized in 2015. It optimizes use of network resources and reduces perceived latency by introducing a binary framing layer over a single TCP connection, with full request and response multiplexing across independent bidirectional streams. HTTP/2 uses HPACK header compression to eliminate redundant header data, credit-based flow control via WINDOW_UPDATE frames, stream prioritization through dependencies and weights, and server push via PUSH_PROMISE frames to proactively deliver anticipated resources. Core frame types include DATA, HEADERS, PRIORITY, RST_STREAM, SETTINGS, PUSH_PROMISE, PING, and GOAWAY, with the protocol preserving the existing HTTP semantics of methods, status codes, and headers while transforming how they are transported on the wire.

## Kin Score — 6.8 / 100 (minimal)

Scored 2026-08-21 under rubric 0.12.0. Trend: flat (+0.0 from 6.8).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 2.6 |
| Developer Ergonomics | 7.1 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Tags

Binary Framing, HPACK, HTTP, HTTP/2, IETF, Multiplexing, Networking, Performance, Protocol, RFC 7540, Server Push

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/http-2/). Scores are computed from the provider's own public artifacts under a published rubric.