Knative

Knative is a CNCF graduated platform that extends Kubernetes to provide serverless capabilities. It consists of Serving for deploying and scaling serverless workloads with automatic scale-to-zero, and Eventing for building event-driven architectures with declarative event routing and delivery. Knative abstracts away infrastructure complexity so developers can focus on writing code.

Knative publishes 13 API contracts indexed on the APIs.io network, including Brokers API, Channels API, Configurations API, and 10 more. Tagged areas include Auto-Scaling, Cloud-Native, Event-Driven, Graduated, and Kubernetes.

The Knative catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 2 Spectral governance rulesets.

Knative’s developer surface includes authentication, documentation, getting-started guide, engineering blog, changelog, and 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

47.1/100 developing ▬ flat Agent 23/100 agent aware Front door AI 3/6 light Heartbeat 100/100 alive self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

2 published contracts

Auto-Scaling Cloud-Native Event-Driven Graduated Kubernetes Serverless

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Software Release & Deployment Management

BC-4210

APIs

POST /apis/serving.knative.dev/v1/namespaces/{namespace}/services

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 47.1/100 · developing

Contract Quality 11.2 / 16

Developer Ergonomics 6.3 / 13

Access Clarity 1.0 / 13

Operational Transparency 3.3 / 8

Contract Governance 1.1 / 8

Discoverability 4.2 / 7

Regulatory Posture 2.5 / 15

Open Source Surface 10.0 / 10

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/knative/"><img src="https://apis.io/badge/knative/card.svg" alt="Knative on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 7.9 — up to +18.4 composite points
Contract Governance scores 13.6 — up to +10.4 composite points
Developer Ergonomics scores 48.8 — up to +10.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/knative/apis.yml: open an issue on github.com/api-evangelist/knative to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Official CLIs on Package Managers	standard	47.6	-	-
OpenSSF Best Practices Badge Holders	standard	47.6	-	-
Artifact Hub Cloud-Native Packages	standard	47.6	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 13

Individual APIs this provider publishes, each with its own machine-readable definition.

Knative Functions

Knative Functions enables developers to create, build, and deploy stateless, event-driven functions as Knative Services using the func CLI or the kn func plugin. Functions can b...

Knative CLI (kn)

The Knative CLI (kn) provides a command-line interface for creating and managing Knative resources including Services, Revisions, Routes, event sources, and Brokers. It simplifi...

Knative Brokers API

Knative Broker resources collect pools of events that can be consumed using Triggers. Brokers provide event routing with filtering, guaranteed delivery, and dead-letter sink sup...

Knative Channels API

Knative Channel resources represent a generic pub/sub messaging channel. Channels receive events and fan them out to all Subscriptions. The default channel implementation uses a...

Knative Configurations API

Knative Configuration resources maintain the desired state for a deployment by capturing container templates. Each update to a Configuration creates a new immutable Revision.

Knative DomainMappings API

Knative DomainMapping resources map a custom domain name to a Knative Service, enabling services to be served under custom hostnames with automatic TLS certificate provisioning.

Knative Revisions API

Knative Revision resources are immutable snapshots of application code and configuration at a point in time. Revisions are created by Configuration updates and are the actual un...

Knative Routes API

Knative Route resources manage the network endpoints and traffic distribution across Revisions. Routes support percentage-based traffic splitting for canary deployments and name...

Knative Subscriptions API

Knative Subscription resources define a delivery destination for events sent to a Channel. Each Subscription routes events from a Channel to a subscriber destination with option...

Knative Triggers API

Knative Trigger resources define filtered delivery options for events arriving at a Broker. A Trigger selects events by attribute filters and routes matching events to a destina...

Knative APIS API

The Apis API from Knative — 2 operation(s) for apis.

Knative Event Sources API

Knative event source resources connect external event producers to the eventing mesh. Built-in sources include ApiServerSource for Kubernetes API events, PingSource for schedule...

Knative Event Types API

Knative EventType resources maintain a catalog of event types that can be consumed from Brokers. EventTypes help consumers discover what events are available without inspecting ...

Scroll for all 13

Postman Collections 11

Ready-to-run Postman collections for exercising this provider's APIs.

Knative Eventing Apis API

POSTMAN

Knative Eventing Apis Brokers API

POSTMAN

Knative Eventing Apis Channels API

POSTMAN

Knative Eventing Apis Configurations API

POSTMAN

Knative Eventing Apis DomainMappings API

POSTMAN

Knative Eventing Apis EventSources API

POSTMAN

Knative Eventing Apis EventTypes API

POSTMAN

Knative Eventing Apis Revisions API

POSTMAN

Knative Eventing Apis Routes API

POSTMAN

Knative Eventing Apis Subscriptions API

POSTMAN

Knative Eventing Apis Triggers API

POSTMAN

Scroll for all 11

Open Collections 13

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Knative Eventing Apis API

OPEN COLLECTION

Knative Eventing Apis Brokers API

OPEN COLLECTION

Knative Eventing Apis Channels API

OPEN COLLECTION

Knative Eventing Apis Configurations API

OPEN COLLECTION

Knative Eventing Apis DomainMappings API

OPEN COLLECTION

Knative Eventing API

OPEN COLLECTION

Knative Eventing Apis EventSources API

OPEN COLLECTION

Knative Eventing Apis EventTypes API

OPEN COLLECTION

Knative Eventing Apis Revisions API

OPEN COLLECTION

Knative Eventing Apis Routes API

OPEN COLLECTION

Knative Serving API

OPEN COLLECTION

Knative Eventing Apis Subscriptions API

OPEN COLLECTION

Knative Eventing Apis Triggers API

OPEN COLLECTION

Scroll for all 13

Knative API pricing

Not yet checked against Knative's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Knative's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Knative Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Knative Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Knative

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Knative Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Knative Eventing CloudEvents

Knative Eventing uses HTTP POST requests conforming to the CloudEvents specification to deliver events between event sources, Brokers, Triggers, Channels, and Subscriptions. Eve...

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Knative Context

2 classes · 21 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Knative — asyncapi rules

8 rules · 7 warnings 1 info

SPECTRAL

Knative — jsonschema rules

6 rules · 4 warnings 2 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

Knative Eventing Resources

0 properties

JSON SCHEMA

Knative Serving Resources

0 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Knative Authentication

http · 1 scheme

SECURITY

Knative Domain Security

TLSv1.3 · HSTS

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Knative Agentic Access

42 operations · 20 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

JSONLD

JSONLD

Build 4

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

PostmanWorkspace

PostmanWorkspace

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

Access & Security 3

Authentication, authorization, and security posture

SecurityPolicy

SecurityPolicy

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 5

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Releases

ChangeLog

Community

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

License

License

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: knative
name: Knative
description: Knative is a CNCF graduated platform that extends Kubernetes to provide serverless capabilities. It consists
  of Serving for deploying and scaling serverless workloads with automatic scale-to-zero, and Eventing for building event-driven
  architectures with declarative event routing and delivery. Knative abstracts away infrastructure complexity so developers
  can focus on writing code.
url: https://knative.dev
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/knative.png
x-docs-platform: mkdocs
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
tags:
- Auto-Scaling
- Cloud-Native
- Event-Driven
- Graduated
- Kubernetes
- Serverless
tags_raw:
- Auto-Scaling
- Cloud Native
- Event-Driven
- Graduated
- Kubernetes
- Serverless
created: '2026-03-16'
modified: '2026-05-19'
specificationVersion: '0.23'
type: Index
apis:
- aid: knative:knative-functions
  name: Knative Functions
  description: Knative Functions enables developers to create, build, and deploy stateless, event-driven functions as Knative
    Services using the func CLI or the kn func plugin. Functions can be written in multiple languages and are automatically
    deployed as auto-scaling Knative Services that respond to HTTP requests or CloudEvents.
  humanURL: https://knative.dev/docs/functions/
  properties:
  - type: Documentation
    url: https://knative.dev/docs/functions/
  - type: GettingStarted
    url: https://knative.dev/docs/getting-started/about-knative-functions/
  - type: GitHubRepository
    url: https://github.com/knative/func
  tags:
  - CLI
  - Event-Driven
  - Functions
  - Serverless
- aid: knative:knative-cli
  name: Knative CLI (kn)
  description: The Knative CLI (kn) provides a command-line interface for creating and managing Knative resources including
    Services, Revisions, Routes, event sources, and Brokers. It simplifies tasks like traffic splitting and autoscaling configuration
    without requiring direct YAML editing.
  humanURL: https://knative.dev/docs/client/
  properties:
  - type: Documentation
    url: https://knative.dev/docs/client/
  - type: GitHubRepository
    url: https://github.com/knative/client
  tags:
  - CLI
  - Developer Tools
  - Kubernetes
- aid: knative:knative-brokers-api
  name: Knative Brokers API
  description: Knative Broker resources collect pools of events that can be consumed using Triggers. Brokers provide event
    routing with filtering, guaranteed delivery, and dead-letter sink support. The default broker implementation uses an in-memory
    channel.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - Brokerage
  tags_raw:
  - Brokers
  properties:
  - type: OpenAPI
    url: openapi/knative-brokers-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-channels-api
  name: Knative Channels API
  description: Knative Channel resources represent a generic pub/sub messaging channel. Channels receive events and fan them
    out to all Subscriptions. The default channel implementation uses an in-memory channel.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - Channels
  properties:
  - type: OpenAPI
    url: openapi/knative-channels-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-configurations-api
  name: Knative Configurations API
  description: Knative Configuration resources maintain the desired state for a deployment by capturing container templates.
    Each update to a Configuration creates a new immutable Revision.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - Configurations
  properties:
  - type: OpenAPI
    url: openapi/knative-configurations-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-domainmappings-api
  name: Knative DomainMappings API
  description: Knative DomainMapping resources map a custom domain name to a Knative Service, enabling services to be served
    under custom hostnames with automatic TLS certificate provisioning.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - DomainMappings
  properties:
  - type: OpenAPI
    url: openapi/knative-domainmappings-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-revisions-api
  name: Knative Revisions API
  description: Knative Revision resources are immutable snapshots of application code and configuration at a point in time.
    Revisions are created by Configuration updates and are the actual units that are scaled.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - Revisions
  properties:
  - type: OpenAPI
    url: openapi/knative-revisions-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-routes-api
  name: Knative Routes API
  description: Knative Route resources manage the network endpoints and traffic distribution across Revisions. Routes support
    percentage-based traffic splitting for canary deployments and named route targets.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - Routes
  properties:
  - type: OpenAPI
    url: openapi/knative-routes-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-subscriptions-api
  name: Knative Subscriptions API
  description: Knative Subscription resources define a delivery destination for events sent to a Channel. Each Subscription
    routes events from a Channel to a subscriber destination with optional reply and dead-letter handling.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - Subscription
  tags_raw:
  - Subscriptions
  properties:
  - type: OpenAPI
    url: openapi/knative-subscriptions-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-triggers-api
  name: Knative Triggers API
  description: Knative Trigger resources define filtered delivery options for events arriving at a Broker. A Trigger selects
    events by attribute filters and routes matching events to a destination such as a Knative Service.
  humanURL: https://knative.dev/docs/serving/
  tags:
  - Triggers
  properties:
  - type: OpenAPI
    url: openapi/knative-triggers-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-apis-api
  name: Knative APIS API
  description: The Apis API from Knative — 2 operation(s) for apis.
  humanURL: https://knative.dev/docs/functions/
  tags: []
  tags_raw:
  - Apis
  properties:
  - type: OpenAPI
    url: openapi/knative-apis-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-event-sources-api
  name: Knative Event Sources API
  description: Knative event source resources connect external event producers to the eventing mesh. Built-in sources include
    ApiServerSource for Kubernetes API events, PingSource for scheduled events, and SinkBinding for injecting sink URIs into
    workloads.
  humanURL: https://knative.dev/docs/functions/
  tags:
  - Event Sources
  properties:
  - type: OpenAPI
    url: openapi/knative-event-sources-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
- aid: knative:knative-event-types-api
  name: Knative Event Types API
  description: Knative EventType resources maintain a catalog of event types that can be consumed from Brokers. EventTypes
    help consumers discover what events are available without inspecting Broker contents directly.
  humanURL: https://knative.dev/docs/functions/
  tags:
  - Event Types
  properties:
  - type: OpenAPI
    url: openapi/knative-event-types-api-openapi.yml
  - type: Documentation
    url: https://knative.dev/docs/serving/
  - type: Reference
    url: https://knative.dev/docs/serving/reference/serving-api/
  - type: GitHubRepository
    url: https://github.com/knative/serving
  - type: JSONSchema
    url: json-schema/knative-serving-schema.json
  - type: Documentation
    url: https://knative.dev/docs/eventing/
  - type: Reference
    url: https://knative.dev/docs/eventing/reference/eventing-api/
  - type: GitHubRepository
    url: https://github.com/knative/eventing
  - type: AsyncAPI
    url: asyncapi/knative-cloudevents-asyncapi.yml
  - type: JSONSchema
    url: json-schema/knative-eventing-schema.json
common:
- type: Plans
  url: plans/knative-plans-pricing.yml
- type: RateLimits
  url: rate-limits/knative-rate-limits.yml
- type: FinOps
  url: finops/knative-finops.yml
- type: CapabilityMap
  url: capabilities/knative-capability-edges.yml
  name: Knative Business Capability Map
- type: IssueTracker
  url: https://github.com/knative/func/issues
- type: Releases
  url: https://github.com/knative/func/releases
- type: SecurityPolicy
  url: https://github.com/knative/func/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/knative/func/blob/main/CODE-OF-CONDUCT.md
- type: ContributionGuide
  url: https://github.com/knative/func/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/knative/func/blob/main/LICENSE
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/knative/overview
- type: AgenticAccess
  url: agentic-access/knative-agentic-access.yml
- type: DomainSecurity
  url: security/knative-domain-security.yml
- type: Authentication
  url: authentication/knative-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/knative
- type: JSONLD
  url: json-ld/knative-context.jsonld
  name: Knative JSON-LD Context
  description: Linked data context mapping Knative resources to standard vocabularies.
- type: Website
  name: Knative Website
  description: Official Knative project website.
  url: https://knative.dev/
- type: Documentation
  name: Knative Documentation
  description: Official Knative documentation.
  url: https://knative.dev/docs/
- type: GettingStarted
  name: Knative Getting Started
  description: Guide for installing and getting started with Knative.
  url: https://knative.dev/docs/getting-started/
- type: Blog
  name: Knative Blog
  description: Project blog and announcements.
  url: https://knative.dev/blog/
- type: ChangeLog
  name: Knative Release Notes
  description: Release notes and changelog for Knative.
  url: https://knative.dev/docs/reference/relnotes/
- type: GitHubOrganization
  name: Knative GitHub Organization
  description: GitHub organization hosting all Knative source code.
  url: https://github.com/knative
- type: GitHubRepository
  name: Knative Docs Repository
  description: Source repository for Knative documentation.
  url: https://github.com/knative/docs
- type: Community
  name: Knative Community
  description: Community resources, working groups, and how to get involved.
  url: https://knative.dev/community/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Knative API — frequently asked questions

Does Knative have an API?

Yes. APIs.io lists 13 APIs from Knative, including Knative Functions, Knative CLI (kn) and Knative Brokers API, and 10 more.

Is there an OpenAPI specification for the Knative API?

Yes. APIs.io indexes 11 OpenAPI specifications for Knative, each linked for download from this page.

How do I authenticate with the Knative API?

Knative uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Knative Authentication.

How much does the Knative API cost?

APIs.io lists 3 pricing plans for Knative, with each plan's price, limits and inclusions under Pricing on this page.

Is the Knative API ready for AI agents?

Knative has a Kin Score of 47.1 out of 100 (developing) and an Agent Readiness score of 23.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/knative"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/knative/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/knative/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.