Published evidence remains behind the same public gates used by the dashboard.
Evidence-ready data, with its boundaries attached.
PolicyWatcher exposes a small anonymous, read-only integration surface for public evidence metadata, portable evidence collections, cross-cloud agent briefs and the curated Observatory registry. The contract keeps publication gates, review cadence and source limits visible to the system consuming it.
Observatory records identify their local curation mode and manual review timestamp.
There is no route here for admin records, credentials, raw content or operational diagnostics.
Six machine endpoints and one continuity workbench.
The six API endpoints accept `GET`, permit cross-origin read access without credentials, and apply bounded public-data and rate policies. The browser-local continuity workbench calls only the published change-event feed after an explicit user action.
Integration manifest
/api/v1/manifestLists the current public data sources, allowed parameters, evidence gates, cache window and API boundaries.
curl https://policywatcher.online/api/v1/manifestOpen endpoint Observatory registry
/api/v1/observatory?lang=enReturns localized sources, curated signals, scheduled events and the registry review context. Use `lang=it` for Italian.
curl "https://policywatcher.online/api/v1/observatory?lang=en"Open endpoint Evidence collection bundle
/api/v1/evidence-collectionsResolves 1–12 canonical public change IDs into deterministic evidence bundles or a vendor-neutral human-review handoff. Personal titles, review states, assignees and due dates are never accepted.
?changes={id},{id}&format=handoffBuild a bounded request Published change events
/api/v1/change-eventsReturns already-public policy change events with stable event IDs and an opaque forward cursor. It does not send notifications or confirm delivery.
?limit=25&lang=en&cursor={opaque}Open event feed Open continuity lab Webhook verification kit
/api/v1/webhook-verification-kitPublishes the HMAC-SHA256 receiver contract, a public test-only vector and Node/Python examples. The public route does not register endpoints; a separate deployment-configured pilot can deliver eligible public events.
Open local verifierReceiver conformance suite
/api/v1/webhook-conformance-suitePublishes eight deterministic positive and negative receiver cases covering every documented decision code. It does not test a live endpoint or delivery path.
Run locallyNeed a tenant boundary? Use API v2.
API v2 adds Microsoft Entra authentication, an allowlisted tenant claim, an Azure API Management policy and a Power Platform connector package. It remains read-only and does not replace v1.
Agent Evidence Gateway
/api/v1/agent/openapi.jsonThree flattened public operations for Microsoft 365 Copilot, Vertex AI Agent Builder and Amazon Quick source packages.
Open agent contractEnterprise API v2 contract
/api/v2/openapi.jsonThe contract is public; data routes require an Entra token with the expected tenant, audience and delegated scope or application role.
Open v2 contractIntegration options
/integrationsCompare API v1, the agent gateway, Enterprise API v2, Azure, Power Platform, Microsoft 365, Google Cloud, AWS, Word and planned private collaboration paths.
Choose a surfacePublished sources remain explicit.
The manifest describes the established public data routes too. It does not turn them into unrestricted database access.
/api/companies/api/compare/api/changes/api/policies/{policyId}/api/source-suspensions/api/source-continuity/api/v1/observatory/api/v1/evidence-collections/api/v1/change-events/api/v1/webhook-verification-kit/api/v1/webhook-conformance-suite/api/trends/api/matrixConnect to the evidence, not around it.
Use API v1 for anonymous public reading and API v2 for a controlled Entra tenant pilot. The readiness kit and conformance suite let receivers test the candidate signature contract locally. Subscriptions, signed outbound delivery and write operations remain future roadmap work.