Tekton is a cloud-native CI/CD framework implemented as a set of Kubernetes Custom Resource Definitions and controllers under the tekton.dev API group. Tekton is a CNCF Incubating project. Its primary API surface is Kubernetes-native — Tasks, Pipelines, PipelineRuns, TaskRuns, EventListeners, Triggers, etc. — accessed through the Kubernetes API server (kubectl, client-go, the tkn CLI, and the Tekton Dashboard). Tekton itself is open-source under Apache 2.0; commercial offerings layered on Tekton (Red Hat OpenShift Pipelines, Jenkins X, Google Cloud Build private preview integrations, IBM Cloud Continuous Delivery, Pipelines-as-Code on GitOps platforms) are out of scope of the upstream project.
Tekton publishes 21 API contracts indexed on the APIs.io network, including Task CRD, and 20 more. Tagged areas include DevOps, CI/CD, Kubernetes, CNCF, and Pipelines.
Tekton’s developer surface includes documentation, getting-started guide, CLI, engineering blog, YouTube channel, release notes, and 21 more developer resources.
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.
Create-or-Update Ergonomics does not apply to this provider. The published contracts declare
no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's
denominator entirely — not scored zero. A reference or data API is not deficient for being unable to
upsert.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% 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/tekton/"><img src="https://apis.io/badge/tekton/card.svg" alt="Tekton 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 Ask about this →
Machine-Readable Auth+10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
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) Ask about this →
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
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.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
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.
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 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.
tekton.dev/v1 kind=Task — defines a series of steps that launch specific build or delivery tools, ingest specific inputs (params, workspaces, resources), and produce specific ou...
tekton.dev/v1 kind=TaskRun — instantiates a Task with specific inputs, workspace bindings, and execution parameters. The TaskRun controller runs the steps as Kubernetes pods and...
tekton.dev/v1 kind=Pipeline — defines an ordered/parallelized series of Tasks that accomplish a specific build or delivery goal. Pipelines compose Tasks via params, workspaces, ...
tekton.dev/v1 kind=PipelineRun — instantiates a Pipeline with specific param values, workspace bindings, service accounts, and timeouts. The PipelineRun controller orchestrates ...
tekton.dev/v1beta1 kind=ClusterTask — cluster-scoped variant of Task, allowing a single definition to be referenced from any namespace. Marked deprecated in favor of remote reso...
tekton.dev/v1beta1 kind=StepAction — reusable, parameterizable step definition that can be referenced from multiple Tasks, enabling tighter sharing than copy-pasting step blocks.
The Tekton Resolution API (tekton.dev/v1alpha1 kind=ResolutionRequest) and built-in resolvers (Git, Hub, Bundles, Cluster, HTTP) fetch Tasks and Pipelines from remote sources at...
triggers.tekton.dev/v1beta1 kind=EventListener — runs an HTTP server (Sink) that receives webhooks (e.g., GitHub push events), applies interceptors, and creates Pipeline/TaskRun...
triggers.tekton.dev/v1beta1 kind=Trigger — combines TriggerBindings (extracting fields from incoming events) and a TriggerTemplate (instantiating PipelineRuns/TaskRuns) used by ...
triggers.tekton.dev/v1beta1 kind=TriggerBinding (and ClusterTriggerBinding) — extracts fields from event payloads and binds them to params used by TriggerTemplates.
triggers.tekton.dev/v1beta1 kind=TriggerTemplate — declares the PipelineRun/TaskRun resources that should be instantiated when a matching event is received, parameterized by Tri...
Tekton Results provides a long-term store and a gRPC + REST API for completed PipelineRun/TaskRun records and their logs, freeing the Kubernetes etcd from acting as a CI history...
Pipelines as Code lets you store Tekton Pipeline definitions inside the same Git repository as your application code (.tekton/) and runs them on PR/push events from GitHub/GitLa...
The Tekton Dashboard exposes a web UI and a thin proxy/HTTP API over the Tekton CRDs and Tekton Results, providing browsing, log streaming, and run management capabilities.
tkn is the official Tekton command-line tool wrapping the Kubernetes API for Tekton resources — start runs, stream logs, list/describe Tasks and Pipelines, manage triggers, and ...
Tekton Hub is a public catalog of reusable Tasks and Pipelines exposed via REST API — search, fetch, and resolve community-published resources for use via the Hub resolver.
Not yet checked against Tekton's own pricing page. Compiled by API Evangelist on 2026-05-08 from tekton.dev/; confirm before you rely on a figure. A free plan or tier is listed.
Plan
Price
Open Source (Apache 2.0) free
Free
Third-Party Distributions and Managed Offerings (Reference) external
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.