# PlatPhorm SitemapOps

SitemapOps is the route evidence engine for PlatPhormNews: it validates public routes, sitemaps, robots files, feeds, llms files, OpenAPI specs, MCP manifests, well-known policy files, canonicals, and source packets for SearchOps, TrustOps, AgentOps, and the root graph.

## Public-safe surfaces
- /
- /dashboard
- /services
- /scans
- /sitemaps
- /robots
- /feeds
- /openapi
- /mcp
- /llms
- /well-known
- /dead-links
- /canonicals
- /route-evidence
- /network-graph
- /trustops
- /searchops
- /agentops
- /reports
- /integrations
- /docs
- /api/docs
- /api/v1/webhooks/events
- /api/v1/trace/links
- /faq
- /api/health
- /api/v1/health
- /openapi.yaml
- /openapi.json
- /llms.txt
- /llms-full.txt
- /llms-index.json
- /robots.txt
- /sitemap.xml
- /sitemap-main.xml
- /sitemap-index.xml
- /rss.xml
- /feed.xml
- /atom.xml
- /manifest.webmanifest
- /.well-known/mcp.json
- /.well-known/agents.json
- /.well-known/agent-policy.json
- /.well-known/ai-policy.json
- /.well-known/ai-plugin.json
- /.well-known/security.txt
- /.well-known/trust.json

## Protected actions
Protected mutating, publishing, full-crawl, registry, report publishing, and export actions require PLATPHORM_API_KEY. Accepted headers are Authorization: Bearer $PLATPHORM_API_KEY and X-PlatPhorm-API-Key: $PLATPHORM_API_KEY.

## Primary integrations
- PlatPhorm Root Graph: https://platphormnews.com (Canonical network topology and public service manifest)
- Base Sitemap Index: https://base.platphormnews.com (Crawlable public sitemap index source)
- SearchOps: https://searchops.platphormnews.com (Crawl packet consumer and source validation)
- TrustOps: https://trustops.platphormnews.com (Route policy evidence consumer)
- AgentOps: https://agentops.platphormnews.com (Agent discovery and action policy consumer)
- MCP Registry: https://mcp.platphormnews.com (Capability registry and MCP validation)
- PlatPhorm API: https://api.platphormnews.com (Platform API surface validation)
- Spec Workbench: https://spec.platphormnews.com (Schema and contract validation)
- BrowserOps: https://browserops.platphormnews.com (Browser journey and UI route validation)
- Evals: https://evals.platphormnews.com (Route and discovery scorecards)
- Docs: https://docs.platphormnews.com (Public report publishing)
- Sheets: https://sheets.platphormnews.com (Route matrix exports)
- Trace: https://trace.platphormnews.com (Trace-linked evidence and span inspection)
- Monitor: https://monitor.platphormnews.com (Availability and uptime correlation)
- WebhookLab: https://webhooks.platphormnews.com (Webhook event validation)
- AgentUI: https://agentui.platphormnews.com (Agent-facing flow validation)
- Claws: https://claws.platphormnews.com (Remediation workflow handoff)
- OpenContent: https://opencontent.platphormnews.com (Public content route evidence)
- Dictionary: https://dictionary.platphormnews.com (Term and route vocabulary references)

## Machine interfaces
- OpenAPI JSON: https://sitemapops.platphormnews.com/openapi.json
- OpenAPI YAML: https://sitemapops.platphormnews.com/openapi.yaml
- MCP endpoint: https://sitemapops.platphormnews.com/api/mcp
- LLMS index: https://sitemapops.platphormnews.com/llms-index.json
- Webhook event audit: https://sitemapops.platphormnews.com/api/v1/webhooks/events
- Trace link audit: https://sitemapops.platphormnews.com/api/v1/trace/links

Updated: 2026-07-18T15:01:56.164Z

## SitemapOps validation capabilities
- Sitemap and sitemap-index XML validation
- Robots policy validation
- RSS and Atom validation
- llms.txt, llms-full.txt, and llms-index.json validation
- OpenAPI route validation
- MCP manifest and endpoint validation
- Well-known policy validation
- Canonical URL and dead-link dry-run evidence
- SearchOps, TrustOps, and AgentOps packet generation
- Root graph dry-run update packets
- WebhookLab event emission with server-side PLATPHORM_API_KEY when configured
- Trace link audit records for operator handoff

## Public/protected boundary
Web dashboard, public-safe discovery, browser-based operations, trusted-domain discovery, standard route compliance, Vercel metadata capture, trace inspection, and agentic workflow discovery are intentionally supported for public read-only debugging and operator workflows. Mutating, administrative, ingestion, replay, fork, remediation, deployment, sync, test-triggering, reporting, and write actions require PLATPHORM_API_KEY.

## Trace policy
SitemapOps accepts and propagates W3C Trace Context for cross-site checks. Public packets include trace identifiers and never include secrets, cookies, Authorization, X-PlatPhorm-API-Key, raw request bodies, or raw x-vercel-ja4-digest values.

## platphormctl examples
- platphormctl site inspect sitemapops
- platphormctl mcp validate sitemapops
- platphormctl policy inspect sitemapops
- platphormctl sitemapops scan-root --dry-run
- platphormctl sitemapops scan-service root --dry-run
- platphormctl sitemapops validate-sitemap https://platphormnews.com/sitemap.xml
- platphormctl sitemapops validate-robots https://platphormnews.com/robots.txt
- platphormctl sitemapops searchops-source --dry-run
- platphormctl sitemapops trustops-source --dry-run
- platphormctl sitemapops agentops-source --dry-run