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.

pricing.md is the commercial contract for an agent. It’s deliberately written in Markdown with structured YAML records so an LLM can consume it without hallucinating a price.

​
Record format

Each record is a fenced YAML block under a section heading. The heading is the human-readable label; the block is the agent-readable truth. 
record_type: price
product: fabric_cloud_router
metro: Ashburn
package: BASIC
mrc_usd: 900
availability: available_for_estimate
agent_instruction: use_for_directional_estimate_only

​
Required fields

FieldTypeNotes
record_typeenumprice, missing_price, quote_required
productstringResource/product slug, lowercase snake_case
metrostringIATA-style code or human label
packagestringTier or SKU label (e.g. BASIC, Standard)
mrc_usdnumberMonthly recurring cost in USD. Required for record_type: price.
availabilityenumavailable_for_estimate, limited, quote_required
agent_instructionenumSee below

​
Agent instructions

The single most important field. It tells the agent how to use the record.

use_for_directional_estimate_only

Safe to quote in a plan. The agent can include this in the visible MRC total. Never represented as binding.

require_account_team_confirmation_before_apply

Quotable as directional, but the plan must surface a blocker that the account team confirms before any mutating call runs.

quote_required

Do not estimate. The plan emits a missing-price blocker and proposes a pricing.md patch.

local_demo_only

Used by demo packages that don’t represent a real commercial surface. The agent treats the price as illustrative.

​
Missing price patch

When the agent finds a record record_type: missing_price, it proposes a pricing.md patch alongside the plan output. The patch is itself a record, with status: quote_required and a reason. 
+ ## Proposed Pricing Gaps
+
+ ### Groq private provider connection
+ record_type: missing_price
+ product: provider_private_connection
+ status: quote_required
+ reason: provider-specific commercial terms not in the public catalog
+
+ ### Fabric Observability stream
+ record_type: missing_price
+ product: fabric_observability_stream
+ status: account_permission_required
The reviewer is expected to either (a) source the price and upgrade the patch to record_type: price, or (b) accept the quote_required and route to the account team.

​
Real Equinix Fabric examples

record_type: price
product: fabric_cloud_router
metro: Ashburn
package: BASIC
mrc_usd: 900
availability: available_for_estimate
agent_instruction: use_for_directional_estimate_only

​
Versioning

Every pricing.md declares its contract version at the top: 
# pricing.md
version: v2026-05-01
legal_status: non_binding_estimate
The agent refuses to use any record from a pricing.md it can’t read the version of. Bumping the version is a deliberate, audited action.

​
Why Markdown?

Two reasons:
  1. Reviewers read it as docs. A finance partner doesn’t need to parse JSON. A YAML block under a Markdown heading is legible and diffable in a PR.
  2. Agents parse YAML reliably. Mixing the human-readable exposition (the heading and the prose) with the agent-readable record (the YAML block) gives both audiences exactly what they need without forking the file.