# Terraform Registry Module & Provider Lookup (`m_ctim/terraform-registry-lookup`) Actor

Look up latest version, download count, and source repo for any Terraform module or provider via the official Terraform Registry API.

- **URL**: https://apify.com/m\_ctim/terraform-registry-lookup.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Terraform Registry Module & Provider Lookup

Look up the latest version, download count, and source repo for any
Terraform module or provider, via the official [Terraform Registry
API](https://developer.hashicorp.com/terraform/registry/api-docs).

Built for DevOps and platform engineering teams checking module/provider
versions and adoption without checking registry.terraform.io by hand.

### Input

```json
{
  "modules": ["terraform-aws-modules/vpc/aws"],
  "providers": ["hashicorp/aws"]
}
```

| Field | Type | Description |
|---|---|---|
| `modules` | array of strings | Terraform modules to look up, each as `"namespace/name/provider"`, e.g. `"terraform-aws-modules/vpc/aws"`. Default `["terraform-aws-modules/vpc/aws"]`. |
| `providers` | array of strings | Terraform providers to look up, each as `"namespace/name"`, e.g. `"hashicorp/aws"`. Leave empty to skip provider lookups. |

At least one of `modules` or `providers` must be non-empty.

### Output

One record per requested module or provider:

```json
{
  "type": "module",
  "ref": "terraform-aws-modules/vpc/aws",
  "found": true,
  "namespace": "terraform-aws-modules",
  "name": "vpc",
  "provider": "aws",
  "latestVersion": "6.6.1",
  "description": "Terraform module to create AWS VPC resources",
  "downloads": 206669261,
  "verified": false,
  "publishedAt": "2026-04-02T20:22:11.071125Z",
  "sourceUrl": "https://github.com/terraform-aws-modules/terraform-aws-vpc"
}
```

A malformed ref (wrong number of `/`-separated segments) or an
unrecognized module/provider returns `{ "found": false, ... }` rather
than failing the whole run.

### How it works

Direct calls to the official Terraform Registry API
(`registry.terraform.io/v1`) — no proxy, no key, no scraping.

### Pricing note

Billed per **lookup** (one run) at a flat rate, regardless of how many
modules/providers are requested.

### Related products

- [Docker Hub Image Tracker](https://github.com/timmKal01/docker-hub-image-tracker)
- [Homebrew Package Lookup](https://github.com/timmKal01/homebrew-package-lookup)

# Actor input Schema

## `modules` (type: `array`):

One or more Terraform modules to look up, each as "namespace/name/provider", e.g. "terraform-aws-modules/vpc/aws".

## `providers` (type: `array`):

One or more Terraform providers to look up, each as "namespace/name", e.g. "hashicorp/aws". Leave empty to skip provider lookups.

## Actor input object example

```json
{
  "modules": [
    "terraform-aws-modules/vpc/aws"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "modules": [
        "terraform-aws-modules/vpc/aws"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("m_ctim/terraform-registry-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "modules": ["terraform-aws-modules/vpc/aws"] }

# Run the Actor and wait for it to finish
run = client.actor("m_ctim/terraform-registry-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "modules": [
    "terraform-aws-modules/vpc/aws"
  ]
}' |
apify call m_ctim/terraform-registry-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/terraform-registry-lookup"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/yWRMj8tr02O71kO3w/builds/3Bm717HUDOxnNVWvV/openapi.json