35 surfaces
9 human pages and 26 machine routes from declared registries.
Developer and agent docs
Public dam knowledge, in documented formats.
Read curated records locally, page through live USACE NID data, inspect the source catalog, or use the MCP server. All current operations are public and read-only.
5 MCP tools
4 resources and 2 prompts from one registry.
Discovery
OpenAPI, LLM files, RSS, Atom, and sitemaps.
Boundary
9 public capability classes; 9 protected action classes.
Live platform evidence
Network registration status
This bounded public check reads the canonical root graph, base sitemap index, and BrowserOps trust validator. Missing registration is shown as pending—not silently treated as success.
Checking the public registries…
Dam data API
The default response uses the local curated educational set. Add source=nid for the live USACE Feature Service. Live queries are bounded to 500 records per page, validate state and hazard filters, block arbitrary upstream URLs, time out, and expose a next offset.
GET https://dam.platphormnews.com/api/dams
GET https://dam.platphormnews.com/api/dams?q=hoover
GET https://dam.platphormnews.com/api/dams?source=nid&state=VA&limit=100
GET https://dam.platphormnews.com/api/dams?source=nid&hazard=H&offset=500Hazard filter codes: H high, S significant, L low, U undetermined.
MCP JSON-RPC
GET returns transport metadata. POST accepts one JSON-RPC 2.0 request or a batch of up to 50. The registry exposes real read-only dam and source operations; no placeholder or write tool is advertised.
POST https://dam.platphormnews.com/api/mcp
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_featured_dams",
"arguments": { "query": "Colorado" }
}
}9 public read capability classes
- interactive map and learning pages
- curated educational dam records
- bounded public USACE NID queries
- live NID inventory counts
- source and integration catalogs
- health, route compliance, and network evidence
- OpenAPI and discovery documents
- RSS and Atom feeds
- MCP introspection and read-only tools
9 protected action classes
- mutations
- ingestion
- publishing
- replay and fork
- workflow runs
- browser and eval test triggers
- report generation
- registry or trusted-domain changes
- deployment and administrative actions
Standard routes
Every route below is declared in the health registry and implemented by this service.
RoutePurpose
/api/healthPublic-safe service health
/api/v1/healthVersioned service health
/api/docsOpenAPI document
/api/damsCurated and live NID dam search
/api/sourcesDam-data source catalog
/api/integrationsPublic feed and API integrations
/api/network-statusLive root graph, sitemap index, and BrowserOps trust evidence
/api/statsLive NID inventory counts
/api/mcpMCP metadata and JSON-RPC transport
/openapi.yamlOpenAPI 3.1 contract
/openapi.jsonOpenAPI 3.1 JSON contract
/llms.txtConcise machine guide
/llms-full.txtComplete machine guide
/llms-index.jsonMachine-readable discovery index
/robots.txtCrawler policy
/sitemap.xmlPublic page sitemap
/sitemap-index.xmlSitemap index
/rss.xmlResource updates feed
/feed.xmlRSS compatibility alias
/atom.xmlAtom resource feed
/manifest.webmanifestWeb app manifest
/.well-known/mcp.jsonMCP discovery
/.well-known/agents.jsonAgent discovery
/.well-known/ai-plugin.jsonAI plugin compatibility discovery
/.well-known/security.txtSecurity contact and policy
/.well-known/trust.jsonPublic/protected trust policy
Authentication and trust
DamWatch USA currently offers no public mutation, ingestion, replay, report-generation, or administrative endpoint. If such actions are added, they must accept only Authorization: Bearer $PLATPHORM_API_KEY or X-PlatPhorm-API-Key: $PLATPHORM_API_KEY. Keys, authorization headers, cookies, sessions, and raw IP addresses are never included in public outputs.