Ansible Playbooks
A curated collection of APIs, tools, and platforms for managing and executing Ansible playbooks for IT automation, configuration management, and orchestration. Covers the Ansible Automation Platform, AWX, Galaxy, Automation Hub, Runner, and Semaphore APIs that power modern infrastructure automation workflows.
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 Ansible Playbooks the way a machine reads it — 49 machine-readable artifacts across 18 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 — Ansible Playbooks scores 56.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Ansible Playbooks
Each block below is one kind of artifact we hold for Ansible Playbooks. 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 18
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.
Ansible Automation Platform API
REST API for Ansible Automation Platform (formerly Ansible Tower/AWX) to manage playbooks, inventories, credentials, job templates, and job execution at enterprise scale. Suppor...
AWX API
AWX is the open-source upstream project for Ansible Automation Platform, providing a web-based UI, REST API, and task engine for Ansible. The AWX API offers programmatic access ...
Ansible Runner API
Ansible Runner is a Python library and CLI tool that provides a stable and consistent interface for executing Ansible playbooks programmatically from within other applications a...
Ansible Galaxy API
Ansible Galaxy is the community hub for sharing Ansible roles and collections. The Galaxy REST API enables searching, downloading, and publishing Ansible content. Supports v1 (r...
Ansible Automation Hub API
Red Hat Ansible Automation Hub is the enterprise content hub for certified Ansible collections, roles, and execution environments. The API provides access to Red Hat certified a...
Ansible Semaphore API
Ansible Semaphore is an open-source modern web UI and REST API for running Ansible playbooks. It provides project management, task scheduling, access control, and a clean interf...
Ansible Playbooks Auth API
OAuth2 token management.
Ansible Playbooks Credentials API
The Credentials API from Ansible Playbooks — 1 operation(s) for credentials.
Ansible Playbooks Hosts API
The Hosts API from Ansible Playbooks — 1 operation(s) for hosts.
Ansible Playbooks Inventories API
The Inventories API from Ansible Playbooks — 2 operation(s) for inventories.
Ansible Playbooks Job Templates API
The Job Templates API from Ansible Playbooks — 3 operation(s) for job templates.
Ansible Playbooks Jobs API
The Jobs API from Ansible Playbooks — 4 operation(s) for jobs.
Ansible Playbooks Organizations API
The Organizations API from Ansible Playbooks — 2 operation(s) for organizations.
Ansible Playbooks Projects API
The Projects API from Ansible Playbooks — 3 operation(s) for projects.
Ansible Playbooks Schedules API
The Schedules API from Ansible Playbooks — 1 operation(s) for schedules.
Ansible Playbooks Users API
The Users API from Ansible Playbooks — 1 operation(s) for users.
Ansible Playbooks Workflow Job Templates API
The Workflow Job Templates API from Ansible Playbooks — 2 operation(s) for workflow job templates.
Ansible Playbooks Workflow Jobs API
The Workflow Jobs API from Ansible Playbooks — 1 operation(s) for workflow jobs.
Scroll within the panel for all 18 ·
Open 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).
Ansible Automation Controller Playbooks 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.
Ansible Playbooks 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.
Ansible Playbooks Finops
FINOPSFeatures 6
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.
Playbook Execution via API
Launch, monitor, and cancel Ansible playbook runs programmatically via REST API with support for extra vars, limits, and tags.
Inventory Management
Create and manage dynamic and static inventories with groups, hosts, and host variables through the API.
Credential Storage
Securely store SSH keys, cloud credentials, and vault passwords in encrypted credential objects accessible to jobs.
Workflow Templates
Chain multiple job templates into orchestrated workflows with conditional success/failure branching.
Scheduling
Schedule playbook runs on recurring schedules using rrule-based calendar expressions.
Collections and Role Management
Discover, download, and manage Ansible collections and roles from Galaxy, Automation Hub, or private repositories.
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.
Ansible Playbooks Context
JSON-LDSpectral Rules 1
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.
Ansible Playbooks API Rules
SPECTRALJSON Schema 2
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.
Inventory
JSON SCHEMAPlaybookJob
JSON SCHEMAJSON Structure 2
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.
Ansible Playbooks Inventory Structure
JSON STRUCTUREAnsible Playbooks Playbook Job Structure
JSON STRUCTUREExamples 2
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.
Security Posture 2
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.
Use Cases 5
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.
Infrastructure Provisioning
Automate the provisioning of cloud resources, VMs, and bare-metal servers using Ansible playbooks triggered via API.
Configuration Management
Enforce consistent configuration state across server fleets by scheduling and executing configuration playbooks via API.
CI/CD Pipeline Integration
Trigger Ansible playbook runs as deployment steps within Jenkins, GitLab CI, GitHub Actions, and other CI/CD platforms.
Compliance and Remediation
Run compliance playbooks on demand or on schedule to detect and remediate drift from desired security baseline states.
Network Automation
Automate network device configuration, firmware upgrades, and compliance checks using Ansible network collections via the API.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Red Hat OpenShift
Deploy and configure OpenShift clusters and workloads using Ansible Automation Platform integrated with OpenShift pipelines.
ServiceNow
Trigger Ansible job templates from ServiceNow ITSM workflows for automated ticket remediation and change management.
GitHub Actions
Use the Ansible Automation Platform GitHub Action to trigger playbook runs as part of GitHub CI/CD workflows.
Terraform
Combine Terraform for infrastructure provisioning with Ansible for post-provisioning configuration management.
Splunk
Use Ansible collections to configure Splunk deployments and automate security alert remediation workflows.
Resources
Every other property we hold for Ansible Playbooks — 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 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ansible-playbooks · machine-readable index on apis.io