Spree Commerce docs for AI coding agents: build headless B2B and marketplace ecommerce on its APIs.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"spree-commerce-developer-docs-for-ai-agents","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 4 h ago | mcp initialize | ok | 200 | 477 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 13 h ago | mcp initialize | ok | 200 | 453 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 21 h ago | mcp initialize | ok | 200 | 299 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 29 h ago | mcp initialize | ok | 200 | 453 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 2 d ago | mcp initialize | ok | 200 | 297 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 2 d ago | mcp initialize | ok | 200 | 329 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 2 d ago | mcp initialize | ok | 200 | 395 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 3 d ago | mcp initialize | ok | 200 | 403 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 3 d ago | mcp initialize | ok | 200 | 298 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
| 3 d ago | mcp initialize | ok | 200 | 406 ms | server Spree Commerce documentation 1.0.0 · protocol 2025-06-18 · 3 tools |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.