# API Proxies

**Canonical:** https://apis.io/providers/api-proxies/  
**Website:** https://apievangelist.com  
**APIs profiled:** 0

An index and topic collection covering reverse-proxy and edge-proxy software used in front of APIs, including HTTP reverse proxies, edge proxies, load balancers, caching proxies, and service mesh sidecars. API proxies sit between API consumers and upstream services to provide TLS termination, routing, rate limiting, observability, traffic shaping, caching, authentication enforcement, and resilience features such as retries and circuit breaking. This collection includes general-purpose reverse proxies like NGINX, HAProxy, Caddy, Apache HTTP Server, Traefik, and Varnish, edge and service mesh proxies like Envoy, Linkerd2-proxy, Istio, Consul Connect, and AWS App Mesh, and proxy-oriented gateways like KrakenD, Tyk, Ambassador, Emissary, and Apache APISIX that overlap with the API gateway category but operate primarily as L7 proxies.

## Kin Score — 9.6 / 100 (minimal)

Scored 2026-10-17 under rubric 0.24.0. Trend: flat (+0.1 from 9.5).

| Facet | Score |
|---|---|
| Discoverability | 48.2 |
| Contract Quality | 14.7 |
| Contract Governance | 0.0 |
| Operational Transparency | 5.3 |
| Developer Ergonomics | 9.5 |
| Access Clarity | 0.0 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 4.9 (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 |

## Use cases (7)

- **API Edge Termination** — Front internal APIs with NGINX, HAProxy, or Envoy to handle TLS, HTTP/2, HTTP/3, compression, and request normalization before requests reach application servers.
- **Multi-Cluster Ingress** — Use Envoy Gateway, Emissary, Ambassador, or Traefik as Kubernetes ingress controllers to expose APIs running across multiple clusters and namespaces.
- **Service Mesh East-West Traffic** — Deploy Istio, Linkerd, or Consul Connect to manage service-to-service API calls with mTLS, retries, and traffic policy inside a Kubernetes cluster.
- **Global API Acceleration** — Front public APIs with Cloudflare, Fastly, or Akamai to terminate connections at the edge, cache safe responses, and absorb DDoS traffic.
- **Canary and Progressive Delivery** — Use proxy-based traffic splitting in Envoy, Istio, or Linkerd to shift a percentage of API traffic to a new version and roll back on error budget breach.
- **Legacy API Modernization** — Place HAProxy, NGINX, or Apache HTTP Server in front of legacy SOAP or HTTP services to add TLS, modern auth, rate limiting, and observability without rewriting the backend.
- **API Migration and Strangler Pattern** — Use a reverse proxy to gradually route traffic from a legacy monolith API to new microservice APIs based on path or header rules.

## Tags

Reverse Proxy, Edge Proxy, API Proxy, Service Mesh Sidecar, Load Balancer, HTTP Proxy, Ingress

---

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