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.

Every package in equinix.dev follows the same four-stage workflow. Read tools run freely. Mutating tools stop at an explicit gate the agent cannot bypass. 
intent
  →  pricing.md contract
  →  Fabric MCP read tools
  →  account preflight
  →  Terraform PR
  →  human approval
  →  MCP create/update tools
  →  observability stream

​
Discover

The agent reads the contract before proposing anything.
1

Resolve the package

The CLI loads provider.json and terraform.json from .equinix-dev/providers/<slug>/. No network call.
2

Match the metro and service profile

Read tools query the Fabric MCP server for candidate metros and service profiles. The agent picks one from the result, never invents one.
equinix_fabric_search_metros(region: "us-east")
equinix_fabric_search_service_profiles(category: "ai_inference", metro: "AS")
3

Read pricing

Estimates come from pricing.md records — never from inferred prose. Anything the agent cannot price is surfaced as quote_required.

​
Plan

The agent generates review artifacts, not infrastructure changes.

Terraform module

HCL composed against equinix/equinix v4.15 resources or terraform-equinix-fabric v0.28.1 modules.

MCP profile

mcp.json listing read tools, mutating tools, and the mutation policy (blocked_by_default_requires_human_confirmation).

Plan JSON

Architecture steps, estimate items, blockers, MCP trace, and a proposed pricing.md patch for missing records.
The full Plan output is what the workspace renders. See /api/plan on the running Fabric Planner.

​
Preflight

Five readiness gates run before any mutating MCP tool is unblocked.
The package has been installed into .equinix-dev/providers/ without any external API call. Status: pass when the manifest file exists and validates against equinix.dev/provider-package/v1.
Every action is dry-run, staged, or local-file write. No real money path. Status: pass is the only acceptable value.
The package has a Terraform profile or an explicit quote_only review-artifact mapping. Status: pass when terraform.json resolves a real provider or module reference.
Real mutations require an approved app in Equinix Developer Settings. Status: blocked until the platform admin creates and approves the app.
Ports, virtual devices, service tokens, and quote surfaces are not assumed. Status: blocked until the customer admin or account team confirms the assets exist.

​
Approve

Mutating MCP tools (equinix_fabric_create_router, equinix_fabric_create_stream, etc.) always require human confirmation outside the local demo path, regardless of preflight status. The agent cannot self-approve.
The approval gate emits a confirmation envelope with the exhaustive list of blocked_by reasons. The reviewer’s job is to resolve them and re-issue the tool call: 
{
  "tool": "equinix_fabric_create_router",
  "mode": "mutating",
  "requires_confirmation": true,
  "blocked_by": [
    "official_quote_missing",
    "developer_app_missing",
    "account_assets_missing"
  ]
}
When all blocked_by items resolve, the reviewer signs off, and the mutating tool runs against the real Equinix API for the first time.

​
Where each stage runs

Local-first

Discover, Plan, and Preflight run entirely on the developer’s machine against the local explorer at 127.0.0.1:8787.

Account-aware

Approve and any subsequent mutating tools run against the real Equinix tenant via OAuth-scoped MCP servers.