Apache HTTP Server
Apache HTTP Server (httpd) is the world's most widely used web server software. It serves static and dynamic content, acts as a reverse proxy and load balancer, and exposes a mod_status monitoring API and balancer-manager management interface for operational visibility.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Apache HTTP Server the way a machine reads it — 43 machine-readable artifacts across 3 APIs, 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 — Apache HTTP Server scores 51.2/100 (developing), with a separate agent-readiness read of 39/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 Apache HTTP Server
Each block below is one kind of artifact we hold for Apache HTTP Server. 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.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Apache HTTP Server Configuration Reference
Configuration directive reference for Apache HTTP Server covering VirtualHost, mod_ssl, mod_rewrite, mod_proxy, and all core directives for web server, proxy, and SSL configurat...
Apache HTTP Server Balancer API
Load balancer management
Apache HTTP Server Status API
Server status and metrics
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Apache HTTP Server Status API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apache Httpd Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Apache Httpd Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
mod_status Monitoring
Real-time server status endpoint providing request rates, worker states, and CPU usage.
mod_proxy Reverse Proxy
Full-featured reverse proxy with HTTP, HTTPS, WebSocket, and AJP protocol support.
mod_proxy_balancer Load Balancing
Load balancing across backend servers with byrequests, bytraffic, and bybusyness algorithms.
mod_ssl TLS Termination
TLS/SSL termination with client certificate authentication and OCSP stapling support.
mod_rewrite URL Rewriting
Powerful rule-based URL rewriting engine for redirects, proxying, and access control.
Virtual Hosting
Name-based and IP-based virtual hosting for serving multiple domains from a single server.
CGI and FastCGI
CGI and FastCGI support for dynamic content generation with external applications.
.htaccess Per-Directory Config
Per-directory configuration files for decentralized access control and configuration.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Apache Httpd Status Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Apache HTTP Server API Rules
SPECTRALApache HTTP Server API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 4
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Httpd Balancermember Structure
JSON STRUCTUREHttpd Proxybalancer Structure
JSON STRUCTUREHttpd Serverstatus Structure
JSON STRUCTUREHttpd Virtualhost Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Httpd Balancermember Example
EXAMPLEHttpd Proxybalancer Example
EXAMPLEHttpd Serverstatus Example
EXAMPLEHttpd Virtualhost Example
EXAMPLESecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Static Web Hosting
Serve HTML, CSS, JavaScript, and media files with high performance and caching headers.
Reverse Proxy for Applications
Proxy requests to application servers (Node.js, Python, Java) with SSL termination.
Load Balancing
Distribute traffic across multiple backend application instances with health checking.
API Gateway
Route and transform API requests using mod_rewrite and mod_proxy rules.
Legacy CGI Application Hosting
Run legacy CGI or PHP applications via mod_cgi, mod_fcgid, or mod_php.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
mod_php
Embeds PHP interpreter directly in the Apache process for PHP application hosting.
Tomcat AJP Connector
AJP protocol integration with Apache Tomcat for Java web application proxying.
Let's Encrypt / Certbot
Automated TLS certificate provisioning with Certbot and the mod_md module.
Nginx
Often deployed alongside Nginx, with Nginx handling static files and Apache handling dynamic content.
ModSecurity WAF
ModSecurity web application firewall module for OWASP rule-based request filtering.
Resources
Every other property we hold for Apache HTTP Server — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/apache-httpd · machine-readable index on apis.io