For Agents

Machine-readable SIMD, SGP, chain-governance, activation, and validator-readiness surfaces.

What You Can Ask

📋 SIMD Proposals

• "What is SIMD-0185?"
• "Show all SIMDs in Review status"
• "Which SIMDs are Activated?"

⚖️ SGP Chain Governance

• "What is SGP-0003?"
• "Which SGPs are in Voting?"
• "Show its chain phase and tally"

⚡ Feature Gates

• "Is SIMD-0185 active on mainnet-beta?"
• "What's pending on mainnet-beta?"
• "Active on devnet but not mainnet-beta?"

🔧 Validator Readiness & Stake

• "Which version needed for SIMD-0185?"
• "Is the network ready for the upgrade?"
• "What % of stake runs Firedancer?"
• "How much stake on Agave 3.1.x?"
• "What's the supermajority version?"

Quick Start

Start with the proposal kind, then follow its own evidence model: SIMD lifecycle and rollout, or SGP chain phase and document provenance.

Open a specific SIMD

https://simd.watch/simd/0185

Query SGP chain governance

curl "https://simd.watch/api/v1/sgps?chainPhase=voting"

Query SIMDs programmatically

curl "https://simd.watch/api/v1/simds?status=Review&limit=5"

Supporting APIs:

/api/v1/features?network=mainnet&status=pending /sgp/:routeId · /api/v1/sgps/:canonicalId /api/v1/stake

Agent Skill

Download the skill file and add it to your agent's skills directory. Compatible with Anthropic AgentSkills format.

Install skill

curl -o SKILL.md https://simd.watch/skill.md

📄 View SKILL.md

Canonical Objects

simd.watch has two canonical proposal kinds: SIMD and SGP. Their lifecycle, identity, and evidence fields remain separate.

📋 SIMD Proposal

Number, title, status (Idea→Activated), author, category, source links

⚖️ SGP Chain-Governance Proposal

Canonical Proposal PDA, document revision, official chain phase, raw tally, and source freshness

⚡ Feature Gate

On-chain activation state per cluster (Devnet/Testnet/Mainnet)

🌐 Cluster Activation

Per-network rollout status with activation epochs

🔧 Validator Readiness

Version compatibility (Agave/Firedancer/Jito) and stake distribution

Agent Workflows

• Open a specific SIMD detail page by number → /simd/0185
• Check whether a feature is active on mainnet (mainnet-beta) → /api/v1/features?network=mainnet&status=active
• Compare devnet / testnet / mainnet-beta activation state side-by-side → /compare
• Inspect validator readiness before recommending rollout action → /readiness
• Review risk tags and required actions for upcoming activations → /risks
• Check minimum client versions across feature gates → /matrix
• Monitor pending features approaching mainnet-beta activation → /changes
• Check SFDP floor gate policy and epoch compliance → /floor
• Review read-only SGP chain-governance state and document provenance → /governance
• Open a unique SGP by its number → /sgp/0003
• Fetch one canonical SGP by returned PDA → /api/v1/sgps/:canonicalId
• View validator-version rollout signals (not a vote) → /adoption
• Get upgrade/rollback commands for validators → /runbook
• Explore SIMD dependency graph → /dependencies
• Get AI-generated summary for any SIMD → POST /api/ai-summary

Backing APIs

These APIs expose proposal and operational evidence. Choose the SIMD or SGP endpoint first; never infer one proposal kind's status from the other.

GET /api/v1/simds

Primary

List all SIMDs with filtering. Use this when your starting point is a SIMD id, title, lifecycle status, or proposal-centric workflow.

status Review | Accepted | Activated

category Core Protocol | ...

q search by number/title/author

id specific SIMD number (e.g. 0185)

limit 1–500 (default 500)

format json | csv

GET /api/v1/simds/:id

Primary

Get a specific SIMD with enriched feature gate data. Example: /api/v1/simds/0185

GET /api/v1/sgps

Governance

Read-only SGP documents plus finalized mainnet governance state. Each record exposes routeId for human links and canonicalId for API and chain operations. Filter by q, chainPhase, and actionOpen; paginate with limit, offset, and meta.pagination.nextOffset. Reuse meta.pagination.snapshot after page one and restart from offset 0 on HTTP 409. Amounts are decimal strings; support is not a For-vote percentage.

GET /api/v1/sgps/:id

Canonical SGP

Get one SGP by canonical Proposal PDA or stable document id. Numeric aliases redirect only when the authoritative catalog proves a unique match.

GET /api/v1/features

List feature gates with SIMD metadata and activation status across Devnet, Testnet, and Mainnet-Beta.

network mainnet | testnet | devnet

status active | pending | inactive

format json | csv

limit 1–500

Response includes: simdNumber, simdUrl, per-network status, activation epochs, min validator versions

GET /api/v1/stake

Stake-weighted validator version distribution (mainnet). Returns total stake, version breakdown with stake amount, percentage, and validator count.

GET /api/epoch-info

Current epoch info for a specific cluster. Returns epoch number, slots remaining, and cache status.

cluster mainnet | testnet | devnet (required)

Example: /api/epoch-info?cluster=mainnet

POST /api/ai-summary

LLM

AI-generated structured summary for any SIMD. Returns 4 sections: why it matters, what's changing, who's affected, and good to know.

simdUrl GitHub URL of the SIMD (required)

structured true for JSON output

locale en | ko | ja | zh-CN (default: en)

fetchHistory true to get proposal history + PR summary

Rate limited: 10 req/min per IP. Responses are cached on disk with no expiry.

POST /api/feature-tracking

LLM

Deep feature tracking — timeline, GitHub issues/PRs, network details, and AI-generated analysis for a specific feature gate.

featureId feature gate public key (required)

simdNumber SIMD number (e.g. "0185")

feature feature object with name/description

Rate limited: 10 req/min per IP. Cached: mainnet-active = permanent, others = 24h.

Web Pages

Canonical SIMD and SGP detail routes are SSR-rendered standalone pages. The homepage loads the SGP collection as a freshness-bounded client enhancement, so agents should use the JSON APIs for complete machine processing.

/ Unified proposal collection — filterable SIMD and SGP cards plus feature-gate views

/simd/:id Canonical SIMD detail page with source-backed summary, proposal history, and community comments

/sgp/:number Canonical numbered SGP detail page; ambiguous records use their returned routeId

/changes Weekly changelog — SIMD status changes, feature gate activations, client releases

/readiness Epoch countdown, pending feature activations, required client version checks

/risks Risk tags for feature gates — Upgrade Required, Epoch Sensitive, Activation Risk

/matrix Client version matrix — minimum Agave/Firedancer/Jito versions per feature gate

/compare Side-by-side SIMD comparison — network status, version requirements, proposal details

/dependencies SIMD cross-references and dependency graph — hub proposals and document relationships

/governance Chain governance — SGP documents, on-chain phase/tally, and source integrity

/adoption Validator version adoption signal — separate from chain-governance voting

/floor SFDP floor gate policy — required minimum client versions per epoch with compliance status

/runbook Validator runbooks — upgrade, rollback, and verification commands for Agave/Firedancer/Jito

/api-docs Interactive API documentation with live examples

Discovery

Standard discovery endpoints for AI crawlers and agents.

📄 skill.md

Anthropic AgentSkills format

📋 llms.txt

LLM discovery standard

🤖 robots.txt

AI crawler rules

Hosted MCP: not currently exposed. Use the revision-aware JSON APIs and skill.md; do not assume a documented page is an MCP transport.

Pages vs APIs

• Show to humans → /simd/:id, /changes, /readiness, /risks, /governance

• Machine processing → /api/v1/simds, /api/v1/sgps, /api/v1/features, /api/v1/stake, /api/epoch-info

• Validator ops → /runbook, /floor, /matrix

• Research / analysis → /compare, /dependencies, /api/ai-summary

Agent Posture

Name the proposal kind explicitly: "Show me SIMD-0185", "Which SGPs are in Voting?", "What's pending on mainnet-beta?".

Keep SIMD lifecycle, SGP chain phase, and validator-version adoption as separate facts.

Limitations

• Not a full governance forum mirror
• Not a replacement for raw RPC or official release notes
• Use canonical SIMD or SGP routes for human-facing links; use APIs for structured data

Notes

• No authentication required
• Data is refreshed on a cache / revalidation cycle (~5 min)
• Start with a SIMD or SGP number; retain SGP canonicalId for API and chain operations
• Human links use /simd/:id and the returned /sgp/:routeId
• Public data APIs (simds, sgps, features, stake): no auth, no hard rate limit (recommended: ≤1 req/min)
• LLM-backed endpoints (ai-summary): rate-limited (10 req/min per IP)
• Data sourced from: Solana RPC, svmgov mainnet, Agave Wiki, SIMD GitHub, SGP GitHub, SFDP API, and client releases
• SGP chain data refreshes independently from proposal-document data; inspect each source freshness field