Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.equinix.dev/llms.txt

Use this file to discover all available pages before exploring further.

This is a concept demo. Some of what equinix.dev shows today is built on real Equinix sources (the Terraform provider, Fabric modules, MCP docs, Agent Factory). The packaging layer — the catalog, the equinix.dev CLI, the Local Explorer, the Agent Kit contract — is a staged product vision, not a shipped Equinix product.
This page exists so a reviewer can quickly tell which claims are backed by official Equinix sources and which are concept-only.

​
Real Equinix sources

These are the surfaces every package in this catalog maps onto. Each link goes to a real, public Equinix repository or docs page.

terraform-provider-equinix

equinix/equinix v4.15 — the official Terraform provider. Resources for Fabric (cloud router, connection, network, port, service profile, service token, streams, alert rules, attachments, subscriptions, precision time), Network Edge (devices, BGP, links, SSH users, files, ACL templates), and Metal (project, device, VLAN, VRF, reserved IP, SSH key, virtual circuit).

terraform-equinix-fabric

terraform-equinix-fabric v0.28.1 — reusable modules for cloud-router connections, port connections, virtual-device connections, Metal connections, streaming observability, route filters, route aggregations, service-token connections, and routing protocols.

Equinix MCP servers

Documented as private beta. Two endpoints: https://mcp.equinix.com/fabric and https://mcp.equinix.com/peeringInsights. Equinix docs describe Claude Desktop, Cursor, VS Code, and other OAuth-capable remote MCP clients as supported.

agent-factory

Public Equinix repo with Fabric and Network Edge schemas plus run-once, scheduled, and event-driven agent catalogs.
Every package’s Terraform mapping points at one of these four. If a package can’t, it carries status: "concept" or status: "no_terraform_surface" so the reviewer knows.

​
What’s a concept (not yet shipped)

These are the equinix.dev artifacts that exist in this demo but are not an existing Equinix product:
The unified provider catalog, the equinix-dev CLI, the Homebrew tap shape (equinix/equinix/equinix-dev), and the .equinix-dev/ project state are all proposed. The local tap in this repo lets you evaluate the packaging without uploading anything.
The six-file package shape (provider.json, terraform.json, mcp.json, readiness.json, pricing.md, llms.txt) is a proposed contract. It’s modeled after how Stripe / Vercel / Linear package developer integrations, but Equinix has not yet shipped a production Agent Kit.
The equinix-dev dev local API mirror at 127.0.0.1:8787 is inspired by Cloudflare’s Local Explorer. It exposes the same shape a future remote api.equinix.dev could expose. Local-only today.
The npx skills add ./equinix-agent-skills install path is a prototype based on emerging skill-package conventions. There is no public Equinix skill registry today.
Sample organization, equinix-cust-104233, and the Apr 22, 2026 · Local Explorer mirror reads incident on the Status page are illustrative. Replace with real names before any external showing.

​
How packages declare their honesty

Each provider.json carries a private_beta flag and each terraform.json carries a status that’s machine-checkable. 
{
  "slug": "equinix/fabric-cloud-router",
  "private_beta": true,
  "terraform": {
    "status": "official_resource",
    "provider": "equinix/equinix",
    "version_constraint": "~> 4.15"
  }
}
A reviewer can grep the catalog for "status": "concept" to see exactly what’s not real.

​
Before any external showing

1

Replace fictional names

The Sample organization org, the Apr 22 incident, and any quoted testimonials must be replaced with real Equinix design-partner names (with permission) or removed.
2

Verify version constraints

equinix/equinix v4.15 and terraform-equinix-fabric v0.28.1 are the versions this demo was built against. Check the upstream repos and bump if needed.
3

Prune `concept` packages

Decide which staged long-tail packages graduate to the public catalog and which stay private.
4

Decide on the public CLI install path

Either ship a real equinix/equinix Homebrew tap or change the docs to a different distribution shape (a tarball, a Vercel-style npx, or an Equinix-managed installer).