Woodpecker CI
Woodpecker CI is a free, open-source (Apache-2.0) continuous integration and delivery engine, forked from Drone and maintained by a community organization on GitHub. It is self-hosted: an operator runs a Woodpecker server plus one or more agents (Docker, Kubernetes, or local backends) against a Git forge — GitHub, GitLab, Gitea, Forgejo, or Bitbucket. Pipelines are declared in `.woodpecker/` YAML workflow files validated by a published JSON Schema, and every server exposes a documented Swagger 2.0 REST API under /api covering repositories, pipelines, secrets, registries, crons, agents, forges, orgs and users, plus Server-Sent Event streams for pipeline events and step logs. Agents talk to the server over a published gRPC/protobuf contract. A first-party Go client library (woodpecker-go), a woodpecker-cli command line tool, DEB/RPM packages, container images and a Helm chart are all published by the project.
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 Woodpecker CI the way a machine reads it — 29 machine-readable artifacts across 1 API, 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 — Woodpecker CI scores 41.3/100 (developing), with a separate agent-readiness read of 23/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Woodpecker CI's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/woodpecker-ci/"
title="Woodpecker CI on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/woodpecker-ci.svg"
alt="Woodpecker CI Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/woodpecker-ci/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/woodpecker-ci/"
title="Woodpecker CI on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/woodpecker-ci/card.svg"
alt="Woodpecker CI Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Woodpecker CI
Each block below is one kind of artifact we hold for Woodpecker CI. 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 22
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.
Woodpecker CI Agents API
The Agents API from Woodpecker CI — 5 operation(s) for agents.
Woodpecker CI Badges API
The Badges API from Woodpecker CI — 2 operation(s) for badges.
Woodpecker CI Events API
The Events API from Woodpecker CI — 1 operation(s) for events.
Woodpecker CI Forges API
The Forges API from Woodpecker CI — 2 operation(s) for forges.
Woodpecker CI Organization API
The Organization API from Woodpecker CI — 1 operation(s) for organization.
Woodpecker CI Organization permissions API
The Organization permissions API from Woodpecker CI — 1 operation(s) for organization permissions.
Woodpecker CI Organization registries API
The Organization registries API from Woodpecker CI — 2 operation(s) for organization registries.
Woodpecker CI Organization secrets API
The Organization secrets API from Woodpecker CI — 2 operation(s) for organization secrets.
Woodpecker CI Orgs API
The Orgs API from Woodpecker CI — 3 operation(s) for orgs.
Woodpecker CI Pipeline logs API
The Pipeline logs API from Woodpecker CI — 4 operation(s) for pipeline logs.
Woodpecker CI Pipeline queues API
The Pipeline queues API from Woodpecker CI — 5 operation(s) for pipeline queues.
Woodpecker CI Pipelines API
The Pipelines API from Woodpecker CI — 7 operation(s) for pipelines.
Woodpecker CI Process profiling and debugging API
The Process profiling and debugging API from Woodpecker CI — 9 operation(s) for process profiling and debugging.
Woodpecker CI Registries API
The Registries API from Woodpecker CI — 2 operation(s) for registries.
Woodpecker CI Repositories API
The Repositories API from Woodpecker CI — 10 operation(s) for repositories.
Woodpecker CI Repository cron jobs API
The Repository cron jobs API from Woodpecker CI — 2 operation(s) for repository cron jobs.
Woodpecker CI Repository registries API
The Repository registries API from Woodpecker CI — 2 operation(s) for repository registries.
Woodpecker CI Repository secrets API
The Repository secrets API from Woodpecker CI — 2 operation(s) for repository secrets.
Woodpecker CI Secrets API
The Secrets API from Woodpecker CI — 2 operation(s) for secrets.
Woodpecker CI System API
The System API from Woodpecker CI — 5 operation(s) for system.
Woodpecker CI User API
The User API from Woodpecker CI — 4 operation(s) for user.
Woodpecker CI Users API
The Users API from Woodpecker CI — 2 operation(s) for users.
Scroll within the panel for all 22 ·
Pricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
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.
Woodpecker Ci Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Woodpecker Ci Events
ASYNCAPIJSON Schema 1
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.
Woodpecker CI configuration file
JSON SCHEMASecurity Posture 3
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.
Resources
Every other property we hold for Woodpecker CI — 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 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/woodpecker-ci · machine-readable index on apis.io
This is an independent, third-party profile of Woodpecker CI, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.