Terraform
HashiCorp Terraform is an open-source infrastructure-as-code tool that enables teams to define, provision, and manage cloud infrastructure using a declarative configuration language (HCL). HCP Terraform and Terraform Enterprise expose a comprehensive REST API for automating workspace management, runs, state, policies, and access control.
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 Terraform the way a machine reads it — 41 machine-readable artifacts across 9 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 — Terraform scores 57.4/100 (developing), with a separate agent-readiness read of 71/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 Terraform
Each block below is one kind of artifact we hold for Terraform. 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 9
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.
Terraform Modules API
Browse and search Terraform modules in the public registry
Terraform Organizations API
Manage HCP Terraform organizations
Terraform Policies API
Manage Sentinel and OPA policies
Terraform Projects API
Manage projects within organizations
Terraform Runs API
Manage Terraform runs and plan/apply lifecycle
Terraform State Versions API
Manage workspace state versions
Terraform Teams API
Manage teams and memberships
Terraform Variables API
Manage workspace and variable sets
Terraform Workspaces API
Manage infrastructure workspaces
Scroll within the panel for all 9 ·
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).
HCP Terraform API
OPEN COLLECTIONTerraform Registry API
OPEN COLLECTIONArazzo Workflows 13
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.
Terraform Audit a Namespace's Published Modules
List everything a namespace publishes, then read the flagship module's versions and download metrics.
ARAZZOTerraform Audit an Organization's Full Inventory
Sweep an organization for its projects, workspaces, teams, and policies in one pass.
ARAZZOTerraform Find and Cancel a Stuck Run
Locate an in-flight run on a workspace, cancel it, and unlock the workspace.
ARAZZOTerraform Destroy Infrastructure and Delete the Workspace
Queue a destroy run, apply it, then delete the emptied workspace.
ARAZZOTerraform Discover a Registry Module and Vet It
Search the public registry for a module, read its latest version, and check its versions and download counts.
ARAZZOTerraform Push a New State Version Under Lock
Lock a workspace, read its current state serial, upload a new state version, and unlock.
ARAZZOTerraform Onboard a Sentinel or OPA Policy
Check whether a policy already exists in an organization, create it if not, and read it back.
ARAZZOTerraform Onboard a Project and Its First Workspace
Create a project in an organization, place a workspace in it, and list the project's workspaces.
ARAZZOTerraform Onboard a Team into an Organization
Check an organization's teams for a name, create the team if missing, and read it back.
ARAZZOTerraform Pin a Module to a Specific Version and Resolve Its Source
Compare a module's latest version against the version you intend to pin, then resolve that exact version's download source.
ARAZZOTerraform Plan a Run and Apply or Discard It
Queue a run, poll the plan to completion, then confirm or throw it away.
ARAZZOTerraform Provision a Workspace with Initial Variables
Verify an organization, create a workspace, seed its variables, and read it back.
ARAZZOTerraform Upsert a Workspace Variable
Set a workspace variable to a value whether or not it already exists.
ARAZZOScroll within the panel for all 13 ·
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.
terraform-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.
Terraform 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.
Terraform Finops
FINOPSSemantic 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.
Terraform 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.
Terraform API Rules
SPECTRALTerraform 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.
Terraform Run
JSON SCHEMATerraform Workspace
JSON SCHEMAJSON Structure 1
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.
Terraform Workspace 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 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 Terraform — 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
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 18
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 18 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
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/terraform · machine-readable index on apis.io