Developers

Public endpoints for the compliance guide inventory.

There is one public REST API for the guide corpus. State pages, locality overlays, and normalized filing variants all resolve through the same canonical path lookup, with discovery documents layered around it.

OpenAPI

https://api.compliancehippo.com/openapi.json

Machine-readable contract for the public content API.

MCP

https://api.compliancehippo.com/mcp

POST-only JSON-RPC endpoint for agents that need to list or fetch pages.

Pages

https://api.compliancehippo.com/api/v1/pages

Lightweight inventory of guide records exposed on the public site.

State endpoint

Access this state via our REST API

Every state guide is fetched through the same lookup route: GET /api/v1/pages/by-path?path=.... When you arrive here from a state page, this example is preloaded automatically.

Example state: Texas
Guide title: Texas local permits and assumed name filings
Canonical path: /states/texas/local-permits-and-assumed-name-filings

curl -s "https://api.compliancehippo.com/api/v1/pages/by-path?path=%2Fstates%2Ftexas%2Flocal-permits-and-assumed-name-filings"

This request example was populated from a state guide shortcut.

Current contract

What the first API version returns

GET /api/v1/pages returns page paths, page kinds, jurisdiction metadata, source counts, profile counts, descriptions, status, and timestamps.
GET /api/v1/pages/by-path?path=... returns the full page payload for a canonical route, including tracked official source rows and normalized filing profiles when a page covers multiple variants.
GET /openapi.json, GET /.well-known/api-catalog, and GET /llms.txt support discovery.

GET https://api.compliancehippo.com/api/v1/pages
GET https://api.compliancehippo.com/api/v1/pages/by-path?path=/guides/annual-report-calendar
GET https://api.compliancehippo.com/openapi.json
GET https://compliancehippo.com/llms.txt