Contour
A Kubernetes ingress controller using Envoy proxy that provides dynamic configuration updates and advanced routing capabilities for managing external access to services in a cluster.
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 Contour the way a machine reads it — 64 machine-readable artifacts across 9 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 — Contour scores 47.8/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 Contour
Each block below is one kind of artifact we hold for Contour. 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 9
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.
Contour Kubernetes Ingress API
Contour's support for the standard Kubernetes Ingress v1 resource, enabling basic ingress use cases such as host-based and path-based routing to backend services. Contour watche...
Contour ExtensionService API
Kubernetes Custom Resource Definition for binding gRPC-based extension services to the Contour API. ExtensionService resources allow external components to implement Contour API...
Contour Configuration API
Contour's ContourConfiguration Custom Resource Definition (v1alpha1) that provides cluster-scoped configuration of a Contour instance, including ingress settings, TLS defaults, ...
Contour Gateway API
Namespace-scoped resources that describe network infrastructure instances that route traffic. Each Gateway is associated with a GatewayClass and defines listeners for inbound tr...
Contour GatewayClass API
Cluster-scoped resources that define the controller responsible for managing Gateways of a particular class. GatewayClass is analogous to IngressClass in the legacy Ingress API.
Contour HTTPProxy API
Operations for managing Contour HTTPProxy custom resources in a Kubernetes cluster. HTTPProxy resources define ingress routing rules for HTTP and HTTPS traffic.
Contour HTTPRoute API
Namespace-scoped resources that define HTTP routing rules, mapping HTTP/HTTPS requests to backend Kubernetes services based on host, path, headers, and other criteria.
Contour TLSCertificateDelegation API
Operations for managing TLSCertificateDelegation resources that allow certificates in one namespace to be used by HTTPProxy resources in other namespaces.
Contour TLSRoute API
Namespace-scoped resources that define TLS routing rules for routing TLS connections based on SNI hostname to backend services.
Scroll within the panel for all 9 ·
Open Collections 2
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).
Contour Gateway API
OPEN COLLECTIONContour HTTPProxy 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.
Contour 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.
Contour Finops
FINOPSSemantic 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.
Contour Context
JSON-LDSpectral Rules 3
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.
JSON Schema 43
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.
AuthorizationServer
JSON SCHEMACondition
JSON SCHEMACORSPolicy
JSON SCHEMADetailedCondition
JSON SCHEMAGateway
JSON SCHEMAGatewayClass
JSON SCHEMAGatewayClassList
JSON SCHEMAGatewayList
JSON SCHEMAHeaderMatchCondition
JSON SCHEMAHeadersPolicy
JSON SCHEMAHeaderValue
JSON SCHEMAHTTPBackendRef
JSON SCHEMAContour HTTPProxy
JSON SCHEMAHTTPProxyList
JSON SCHEMAHTTPProxySpec
JSON SCHEMAHTTPProxyStatus
JSON SCHEMAHTTPRoute
JSON SCHEMAHTTPRouteFilter
JSON SCHEMAHTTPRouteList
JSON SCHEMAHTTPRouteMatch
JSON SCHEMAHTTPRouteRule
JSON SCHEMAInclude
JSON SCHEMAListener
JSON SCHEMAListenerStatus
JSON SCHEMAMatchCondition
JSON SCHEMAObjectMeta
JSON SCHEMAParentReference
JSON SCHEMAQueryParameterMatchCondition
JSON SCHEMARateLimitPolicy
JSON SCHEMARetryPolicy
JSON SCHEMARoute
JSON SCHEMASecretObjectReference
JSON SCHEMAService
JSON SCHEMAStatus
JSON SCHEMASubCondition
JSON SCHEMATCPProxy
JSON SCHEMATimeoutPolicy
JSON SCHEMATLS
JSON SCHEMATLSCertificateDelegation
JSON SCHEMATLSCertificateDelegationList
JSON SCHEMATLSRoute
JSON SCHEMATLSRouteList
JSON SCHEMAVirtualHost
JSON SCHEMAScroll within the panel for all 43 ·
JSON Structure 1
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.
Contour Structure
JSON STRUCTURESecurity Posture 1
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.
Resources
Every other property we hold for Contour — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/contour · machine-readable index on apis.io