GitHub Actions
APIs for GitHub Actions - automation and CI/CD platform.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles GitHub Actions the way a machine reads it — 154 machine-readable artifacts across 11 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 — GitHub Actions scores 79.1/100 (exemplar), with a separate agent-readiness read of 74/100 (agent native). 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 GitHub Actions
Each block below is one kind of artifact we hold for GitHub Actions. 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 11
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.
GitHub Actions Artifacts API
Download and manage workflow run artifacts
GitHub Actions Cache API
Manage workflow dependency caches
GitHub Actions Jobs API
Access information about workflow jobs
GitHub Actions OIDC API
Manage OIDC subject claim customization
GitHub Actions Permissions API
Control Actions enablement and permissions
GitHub Actions Secrets API
Manage encrypted secrets for Actions
GitHub Actions Self-Hosted Runner Groups API
Manage runner groups for organizations
GitHub Actions Self-Hosted Runners API
Manage self-hosted runners for workflows
GitHub Actions Variables API
Create and manage workflow variables
GitHub Actions Workflow Runs API
Manage and monitor workflow run executions
GitHub Actions Workflows API
Manage workflow files and workflow runs
Scroll within the panel for all 11 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
GitHub Actions API
POSTMANOpen 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).
GitHub Actions API
OPEN COLLECTIONArazzo Workflows 12
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOGitHub Actions Approve a Pending Deployment
Get a run, find its pending deployment environments, approve them, then poll the run to completion.
ARAZZOGitHub Actions Cancel a Workflow Run and Confirm
Get a run, request cancellation, poll until it is no longer in progress, and force-cancel if it gets stuck.
ARAZZOGitHub Actions Collect Workflow Run Artifacts
Find the latest run for a repository, confirm it, list its artifacts, and resolve a download URL.
ARAZZOGitHub Actions Dispatch and Track a Workflow Run
Manually dispatch a workflow, find the run it created, poll until it completes, then list its jobs.
ARAZZOGitHub Actions Inspect Failed Job Logs
Find the latest failed run, list its jobs, get the failing job, and resolve its log download URL.
ARAZZOGitHub Actions Prune Repository Caches
Read cache usage, list the largest caches, and delete the largest one by id to reclaim space.
ARAZZOGitHub Actions Register a Self-hosted Runner
List the available runner application binaries, mint a registration token, then list the repository's runners.
ARAZZOGitHub Actions Re-run Failed Jobs and Track
Find the most recent failed run, re-run only its failed jobs, and poll the run until it completes again.
ARAZZOGitHub Actions Share an Organization Secret with Selected Repositories
Fetch the org public key, create or update a selected-visibility org secret, scope it to repositories, and list them.
ARAZZOGitHub Actions Upsert a Repository Secret
Fetch the repository public key, create or update an encrypted secret, then confirm it exists.
ARAZZOGitHub Actions Upsert a Repository Variable
Look up a repository variable by name and either create it or update it, then read it back.
ARAZZOScroll within the panel for all 12 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
github-actions-mcp.yml
MCP SERVERPricing 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.
Github Actions 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.
Github Actions Finops
FINOPSFeatures 10
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.
Scroll within the panel for all 10 ·
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.
Github Actions 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.
GitHub Actions API Rules
SPECTRALGitHub Actions API Rules
SPECTRALJSON Schema 34
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.
ActionsCacheEntry
JSON SCHEMAActionsCacheUsage
JSON SCHEMAActionsDefaultWorkflowPermissions
JSON SCHEMAActionsOrganizationPermissions
JSON SCHEMAActionsPublicKey
JSON SCHEMAActionsRepositoryPermissions
JSON SCHEMAActionsSecret
JSON SCHEMAActionsVariable
JSON SCHEMAArtifact
JSON SCHEMAAuthenticationToken
JSON SCHEMAGitHub Actions Cache Entry
JSON SCHEMADeployment
JSON SCHEMAEnvironmentApproval
JSON SCHEMAJob
JSON SCHEMAJobStep
JSON SCHEMAMinimalRepository
JSON SCHEMAOidcCustomSubOrg
JSON SCHEMAOidcCustomSub
JSON SCHEMAOrgActionsSecret
JSON SCHEMAPendingDeployment
JSON SCHEMAGitHub Actions Workflow Run
JSON SCHEMARunnerApplication
JSON SCHEMARunnerGroup
JSON SCHEMARunnerLabel
JSON SCHEMAGitHub Actions Self-Hosted Runner
JSON SCHEMAGitHub Actions Secret
JSON SCHEMASelfHostedRunner
JSON SCHEMASimpleCommit
JSON SCHEMASimpleUser
JSON SCHEMAGitHub Actions Variable
JSON SCHEMAWorkflowRun
JSON SCHEMAWorkflowRunUsage
JSON SCHEMAWorkflow
JSON SCHEMAWorkflowUsage
JSON SCHEMAScroll within the panel for all 34 ·
JSON Structure 29
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.
Github Actions Actions Cache Entry Structure
JSON STRUCTUREGithub Actions Actions Cache Usage Structure
JSON STRUCTUREGithub Actions Actions Public Key Structure
JSON STRUCTUREGithub Actions Actions Repository Permissions Structure
JSON STRUCTUREGithub Actions Actions Secret Structure
JSON STRUCTUREGithub Actions Actions Variable Structure
JSON STRUCTUREGithub Actions Artifact Structure
JSON STRUCTUREGithub Actions Authentication Token Structure
JSON STRUCTUREGithub Actions Deployment Structure
JSON STRUCTUREGithub Actions Environment Approval Structure
JSON STRUCTUREGithub Actions Job Step Structure
JSON STRUCTUREGithub Actions Job Structure
JSON STRUCTUREGithub Actions Minimal Repository Structure
JSON STRUCTUREGithub Actions Oidc Custom Sub Org Structure
JSON STRUCTUREGithub Actions Oidc Custom Sub Structure
JSON STRUCTUREGithub Actions Org Actions Secret Structure
JSON STRUCTUREGithub Actions Pending Deployment Structure
JSON STRUCTUREGithub Actions Runner Application Structure
JSON STRUCTUREGithub Actions Runner Group Structure
JSON STRUCTUREGithub Actions Runner Label Structure
JSON STRUCTUREGithub Actions Self Hosted Runner Structure
JSON STRUCTUREGithub Actions Simple Commit Structure
JSON STRUCTUREGithub Actions Simple User Structure
JSON STRUCTUREGithub Actions Workflow Run Structure
JSON STRUCTUREGithub Actions Workflow Run Usage Structure
JSON STRUCTUREGithub Actions Workflow Structure
JSON STRUCTUREGithub Actions Workflow Usage Structure
JSON STRUCTUREScroll within the panel for all 29 ·
Examples 29
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.
Github Actions Job Example
EXAMPLEScroll within the panel for all 29 ·
Security Posture 4
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.
Github Actions Trust Center
SOC 1 Type 2, SOC 2 Type 2, SOC 3, ISO/IEC 27001:2013, ISO/IEC 42001:2023, CSA STAR Level 2, FedRAMP LI-SaaS (ATO)
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 6
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.
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Scroll within the panel for all 8 ·
Resources
Every other property we hold for GitHub Actions — 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 6
Portal, sign-up, and the first successful call
Documentation 10
Reference material describing how the API behaves
Scroll within the panel for all 10 ·
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 17
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 17 ·
Build 9
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 9 ·
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Learn 1
Tutorials, courses, talks, and written guidance
Operate 6
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
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/github-actions · machine-readable index on apis.io