Astronomer
Astronomer is the company behind Astro, a fully managed data operations platform powered by Apache Airflow. Astro lets data teams author, orchestrate, run, and observe data pipelines (DAGs) at scale across a managed control plane and data plane. The Astro Platform API is a production-ready REST API for programmatic control of Astro resources — Organizations, Workspaces, Deployments, Clusters, Users, Teams, role-based access control, API tokens, deploys, and environment objects — authenticated with bearer API tokens. Astronomer also ships the Astro CLI, an official Terraform provider, the Astro Python SDK, a documentation MCP server, and Astro Runtime, its distribution of Apache Airflow.
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 Astronomer the way a machine reads it — 21 machine-readable artifacts across 15 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 — Astronomer scores 57.5/100 (developing), with a separate agent-readiness read of 62/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.
How we profile Astronomer
Each block below is one kind of artifact we hold for Astronomer. 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 15
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.
Astronomer AgentToken API
The AgentToken API from Astronomer — 2 operation(s) for agenttoken.
Astronomer AllowedIpAddressRange API
The AllowedIpAddressRange API from Astronomer — 4 operation(s) for allowedipaddressrange.
Astronomer ApiToken API
The `apitoken` object represents a single API token within your Organization. API tokens are used to authenticate automated tools and processes to your Organization. They have v...
Astronomer Authorization API
The Authorization API from Astronomer — 1 operation(s) for authorization.
Astronomer Cluster API
A `cluster` object represents an Astro cluster, which is a Kubernetes cluster that hosts the infrastructure required to run Deployments. Make requests to `cluster` endpoints to ...
Astronomer Deploy API
The Deploy API from Astronomer — 4 operation(s) for deploy.
Astronomer Deployment API
The `deployment` object represents an Astro Deployment, which is a hosted Airflow environment that is powered by all core Airflow components, including schedulers and workers. M...
Astronomer Environment API
The Environment API from Astronomer — 3 operation(s) for environment.
Astronomer Invite API
The Invite API from Astronomer — 2 operation(s) for invite.
Astronomer Options API
The Options API from Astronomer — 2 operation(s) for options.
Astronomer Organization API
The `organization` object contains the metadata and configurations of an Astro Organization. It does not include objects within the Organization, such as users and clusters. Mak...
Astronomer Role API
The Role API from Astronomer — 4 operation(s) for role.
Astronomer Team API
The `team` object represents an Astro Team, which is a group of users that share the same permissions across your Organization and Workspaces. Make requests to `team` endpoints ...
Astronomer User API
The `user` object represents a user account in your Astro Organization. Astro creates a new `user` object whenever you invite a user by email or add a user to Astro through an i...
Astronomer Workspace API
The `workspace` object represents an Astro Workspace, which is a collection of Deployments that can be accessed by a specific group of users. It contains metadata about a Worksp...
Scroll within the panel for all 15 ·
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.
astronomer-mcp.yml
MCP SERVERSecurity 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.
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.
Resources
Every other property we hold for Astronomer — 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 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/astronomer · machine-readable index on apis.io