Argo
Argo is a collection of open-source Kubernetes-native tools for workflows, events, CI/CD, and progressive delivery. The project includes Argo Workflows (container-native workflow engine), Argo CD (declarative GitOps continuous delivery), Argo Events (event-driven automation framework), and Argo Rollouts (progressive delivery with canary and blue-green strategies). Argo is a CNCF graduated project governed by the Linux Foundation.
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 Argo the way a machine reads it — 200 machine-readable artifacts across 14 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 — Argo scores 54.1/100 (developing), with a separate agent-readiness read of 54/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 Argo
Each block below is one kind of artifact we hold for Argo. 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 14
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.
Argo Events API
Kubernetes-native API for the Argo Events event-driven automation framework. Exposes CRD-based resources including EventSource, EventBus, and Sensor for triggering Argo Workflow...
Argo Rollouts API
Kubernetes CRD-based API for Argo Rollouts progressive delivery controller. Provides Rollout and AnalysisTemplate resources for managing canary and blue-green deployment strateg...
Argo Applications API
Operations for creating, querying, syncing, and deleting Argo CD GitOps applications.
Argo Clusters API
Operations for registering and managing target Kubernetes clusters for application deployment.
Argo Cron Workflows API
Operations for managing scheduled cron workflows
Argo Info API
Server information and version endpoints
Argo Projects API
Operations for managing Argo CD projects that provide governance and access control for applications.
Argo Repositories API
Operations for registering and managing Git and Helm chart repositories used as application sources.
Argo Session API
Authentication operations for obtaining and invalidating bearer tokens.
Argo Settings API
Operations for reading Argo CD server configuration and settings.
Argo Version API
Server version information endpoint.
Argo Workflow Archives API
Operations for accessing archived workflow records
Argo Workflow Templates API
Operations for managing reusable workflow templates
Argo Workflows API
Operations for managing workflow executions
Scroll within the panel for all 14 ·
Open Collections 2
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).
Argo CD API
OPEN COLLECTIONArgo Workflows 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.
Argo Plans Pricing
PLANSRate 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.
Argo 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.
Argo 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.
Argo Workflows
Container-native workflow engine for orchestrating parallel jobs and ML pipelines on Kubernetes.
Argo CD
Declarative GitOps continuous delivery tool that syncs Kubernetes application state from Git.
Argo Events
Event-driven automation framework supporting 20+ event sources to trigger Kubernetes workflows.
Argo Rollouts
Progressive delivery controller with canary, blue-green, and experiment strategies for Kubernetes.
CNCF Graduated
All four Argo projects are CNCF graduated, ensuring production-quality governance and stability.
Kubernetes-Native
All tools are implemented as Kubernetes CRDs and controllers, integrating natively with the platform.
Event 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.
Argo Events
Argo Events is a Kubernetes-native event-driven automation framework that listens to over 20 event sources and triggers Argo Workflows, Kubernetes objects, HTTP requests, and ot...
ASYNCAPISemantic 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.
Argo Context
JSON-LDSpectral Rules 3
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.
JSON Schema 52
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.
Argo CD Application Spec
JSON SCHEMAAppProject
JSON SCHEMAApplicationDestination
JSON SCHEMAApplicationList
JSON SCHEMAApplication
JSON SCHEMAApplicationSource
JSON SCHEMAApplicationSpec
JSON SCHEMAApplicationStatus
JSON SCHEMAClusterList
JSON SCHEMACluster
JSON SCHEMAProjectList
JSON SCHEMARepositoryList
JSON SCHEMARepository
JSON SCHEMASettings
JSON SCHEMASyncPolicy
JSON SCHEMASyncRequest
JSON SCHEMAVersionMessage
JSON SCHEMAArgo Rollout Spec
JSON SCHEMAArgo Workflow Spec
JSON SCHEMAArguments
JSON SCHEMAArtifact
JSON SCHEMACronWorkflowCreateRequest
JSON SCHEMACronWorkflowList
JSON SCHEMACronWorkflow
JSON SCHEMACronWorkflowSpec
JSON SCHEMACronWorkflowStatus
JSON SCHEMACronWorkflowUpdateRequest
JSON SCHEMADAGTask
JSON SCHEMAInfoResponse
JSON SCHEMAInputs
JSON SCHEMALogEntry
JSON SCHEMANodeStatus
JSON SCHEMAObjectMeta
JSON SCHEMAOutputs
JSON SCHEMAParameter
JSON SCHEMARetryStrategy
JSON SCHEMATemplate
JSON SCHEMAVersion
JSON SCHEMAWorkflowCreateRequest
JSON SCHEMAWorkflowList
JSON SCHEMAWorkflowResubmitRequest
JSON SCHEMAWorkflowResumeRequest
JSON SCHEMAWorkflowRetryRequest
JSON SCHEMAWorkflow
JSON SCHEMAWorkflowSpec
JSON SCHEMAWorkflowStatus
JSON SCHEMAWorkflowStep
JSON SCHEMAWorkflowStopRequest
JSON SCHEMAWorkflowTemplateCreateRequest
JSON SCHEMAWorkflowTemplateList
JSON SCHEMAWorkflowTemplate
JSON SCHEMAWorkflowTemplateUpdateRequest
JSON SCHEMAScroll within the panel for all 52 ·
JSON Structure 52
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.
Argo Application Structure
JSON STRUCTUREArgo Cd App Project Structure
JSON STRUCTUREArgo Cd Application Destination Structure
JSON STRUCTUREArgo Cd Application List Structure
JSON STRUCTUREArgo Cd Application Source Structure
JSON STRUCTUREArgo Cd Application Spec Structure
JSON STRUCTUREArgo Cd Application Status Structure
JSON STRUCTUREArgo Cd Application Structure
JSON STRUCTUREArgo Cd Cluster List Structure
JSON STRUCTUREArgo Cd Cluster Structure
JSON STRUCTUREArgo Cd Project List Structure
JSON STRUCTUREArgo Cd Repository List Structure
JSON STRUCTUREArgo Cd Repository Structure
JSON STRUCTUREArgo Cd Settings Structure
JSON STRUCTUREArgo Cd Sync Policy Structure
JSON STRUCTUREArgo Cd Sync Request Structure
JSON STRUCTUREArgo Cd Version Message Structure
JSON STRUCTUREArgo Rollout Structure
JSON STRUCTUREArgo Workflow Structure
JSON STRUCTUREArgo Workflows Arguments Structure
JSON STRUCTUREArgo Workflows Artifact Structure
JSON STRUCTUREArgo Workflows Cron Workflow Create Request Structure
JSON STRUCTUREArgo Workflows Cron Workflow List Structure
JSON STRUCTUREArgo Workflows Cron Workflow Spec Structure
JSON STRUCTUREArgo Workflows Cron Workflow Status Structure
JSON STRUCTUREArgo Workflows Cron Workflow Structure
JSON STRUCTUREArgo Workflows Cron Workflow Update Request Structure
JSON STRUCTUREArgo Workflows Dag Task Structure
JSON STRUCTUREArgo Workflows Info Response Structure
JSON STRUCTUREArgo Workflows Inputs Structure
JSON STRUCTUREArgo Workflows Log Entry Structure
JSON STRUCTUREArgo Workflows Node Status Structure
JSON STRUCTUREArgo Workflows Object Meta Structure
JSON STRUCTUREArgo Workflows Outputs Structure
JSON STRUCTUREArgo Workflows Parameter Structure
JSON STRUCTUREArgo Workflows Retry Strategy Structure
JSON STRUCTUREArgo Workflows Template Structure
JSON STRUCTUREArgo Workflows Version Structure
JSON STRUCTUREArgo Workflows Workflow Create Request Structure
JSON STRUCTUREArgo Workflows Workflow List Structure
JSON STRUCTUREArgo Workflows Workflow Resubmit Request Structure
JSON STRUCTUREArgo Workflows Workflow Resume Request Structure
JSON STRUCTUREArgo Workflows Workflow Retry Request Structure
JSON STRUCTUREArgo Workflows Workflow Spec Structure
JSON STRUCTUREArgo Workflows Workflow Status Structure
JSON STRUCTUREArgo Workflows Workflow Step Structure
JSON STRUCTUREArgo Workflows Workflow Stop Request Structure
JSON STRUCTUREArgo Workflows Workflow Structure
JSON STRUCTUREArgo Workflows Workflow Template List Structure
JSON STRUCTUREArgo Workflows Workflow Template Structure
JSON STRUCTUREScroll within the panel for all 52 ·
Examples 52
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.
Argo Application Example
EXAMPLEArgo Cd App Project Example
EXAMPLEArgo Cd Application Example
EXAMPLEArgo Cd Cluster Example
EXAMPLEArgo Cd Cluster List Example
EXAMPLEArgo Cd Project List Example
EXAMPLEArgo Cd Repository Example
EXAMPLEArgo Cd Settings Example
EXAMPLEArgo Cd Sync Policy Example
EXAMPLEArgo Cd Sync Request Example
EXAMPLEArgo Rollout Example
EXAMPLEArgo Workflow Example
EXAMPLEScroll within the panel for all 52 ·
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.
GitOps Platform
Combine Argo CD and Argo Workflows for a complete Git-driven DevOps platform on Kubernetes.
Machine Learning Pipelines
Use Argo Workflows to orchestrate multi-step ML training, evaluation, and deployment pipelines.
Event-Driven Automation
Use Argo Events to trigger workflows based on webhooks, schedules, messaging, and cloud events.
Progressive Delivery
Use Argo Rollouts for safe canary and blue-green deployments with automated analysis and rollback.
CI/CD on Kubernetes
Build complete CI/CD pipelines natively on Kubernetes using Argo Workflows and Argo CD together.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Helm
Argo CD natively renders Helm charts; Argo Workflows can execute Helm operations as steps.
Kustomize
Argo CD supports Kustomize overlays for environment-specific application configuration.
Prometheus
All Argo tools expose Prometheus metrics for monitoring workflow and deployment health.
Slack
Argo CD and Argo Workflows support Slack notifications for deployment and workflow events.
GitHub
Deep integration with GitHub webhooks for triggering workflows and CD syncs.
Amazon S3
Argo Workflows uses S3 as an artifact repository for passing data between workflow steps.
Resources
Every other property we hold for Argo — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
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
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/argo · machine-readable index on apis.io