# CPSP-PMDF
> Plataforma web institucional do Centro de Políticas de Segurança Pública da Polícia Militar do Distrito Federal (PMDF).

O CPSP-PMDF organiza fluxos administrativos e operacionais, controles de acesso, indicadores e relatórios institucionais. Esta camada de descoberta descreve somente recursos públicos. Registros operacionais, dados de usuários, documentos internos, permissões e APIs autenticadas não estão disponíveis por estes arquivos.

When to use this site: use CPSP-PMDF when an agent needs authoritative public information about the platform identity, public trust pages, machine-readable discovery resources or developer integration metadata. For REST integration, start at /api/v1 and /openapi.json. For native agent integration, use /.well-known/mcp and its server card. Do not use these resources to infer authenticated records, personnel data, internal permissions, operational databases, private API behavior or facts that are not explicitly published.

Public pages support HTML and, where negotiated, Markdown. Clients requesting Markdown should send Accept: text/markdown. Explicit .md aliases are also available for negotiable public pages. Markdown responses vary on Accept and Accept-Encoding so caches keep representations separate.

## Public REST API
- [API v1](https://cpsp-pmdf.vercel.app/api/v1): stable read-only public API index.
- [Site identity](https://cpsp-pmdf.vercel.app/api/v1/site): public CPSP-PMDF identity and verified institutional contact metadata.
- [Public resources](https://cpsp-pmdf.vercel.app/api/v1/resources): developer and agent discovery catalog.
- [API policies](https://cpsp-pmdf.vercel.app/api/v1/policies): versioning, RFC 9457 error model, deprecation and rate-limit conventions.
- [OpenAPI](https://cpsp-pmdf.vercel.app/openapi.json): OpenAPI 3.1 contract with unique operationIds and typed JSON schemas.

REST API errors use application/problem+json according to RFC 9457 and include stable code and hint extensions. The current API uses URL-path versioning under /api/v1. Breaking changes require a new major path. Deprecation is signaled with the RFC 9745 Deprecation header, and scheduled retirement uses the RFC 8594 Sunset header. Rate-limit responses expose RateLimit-Policy, RateLimit and compatibility RateLimit-Limit/Remaining/Reset fields; HTTP 429 also includes Retry-After.

## Public information
- [About](https://cpsp-pmdf.vercel.app/about): purpose, scope and public/private boundary of the CPSP-PMDF platform.
- [Contact](https://cpsp-pmdf.vercel.app/contact): verified CPSP institutional contact information published by PMDF.
- [Privacy](https://cpsp-pmdf.vercel.app/privacy): public privacy, access and agent-boundary guidance.

## Developer resources
- [Developer portal](https://cpsp-pmdf.vercel.app/developers): CPSP-PMDF API v1, Vercel, Markdown, OpenAPI, errors, versioning, rate limits and MCP discovery.
- [MCP](https://cpsp-pmdf.vercel.app/.well-known/mcp): stateless Streamable HTTP MCP endpoint. It supports the modern 2026-07-28 request model and legacy 2025 initialize compatibility; tools expose public informational data only.
- [MCP Server Card](https://cpsp-pmdf.vercel.app/.well-known/mcp/server-card.json): experimental SEP-2127 server discovery metadata.

## Discovery
- [Sitemap](https://cpsp-pmdf.vercel.app/sitemap.xml): public indexable URLs.
- [Robots](https://cpsp-pmdf.vercel.app/robots.txt): crawler guidance and protected path exclusions.
- [Markdown home](https://cpsp-pmdf.vercel.app/index.md): explicit Markdown representation of the public home page.