# HTTP Headers

**Canonical:** https://apis.io/providers/headers/  
**APIs profiled:** 1

Every HTTP header an API can speak — 302 headers assembled from the IANA HTTP Field Name Registry, 119,030 published specification files across 26,641 providers, and the regulations that reach the wire. What each header is for, how to use it, and the standard, guidance and law behind it.

## Kin Score — 3.2 / 100 (minimal)

Scored 2026-10-31 under rubric 0.25.0.

| Facet | Score |
|---|---|
| Discoverability | 39.3 |
| Contract Quality | 6.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 0.0 |
| Access Clarity | 0.0 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 0.0 (matched via fallback).

## 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 |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |

## Tags

API Design, HTTP Headers, Standards

---

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