Developer platform
Put governed permit intelligence inside your software.
Use Permit Sheriff through scoped REST and MCP access without giving up the evidence, tenancy, and decision-control boundaries that make the core product trustworthy. Self-service Direct API access is intentionally narrower than the broader partner platform.
Two developer access paths
Permit Sheriff's broader partner platform and its self-service Direct API share the same governed backend, but they do not expose the same permissions.
- Partner integrations can be provisioned with scoped permit-analysis, permit-read, contractor-verification, jurisdiction-resolution, usage, MCP, and webhook capabilities as applicable.
- Self-service Direct API credentials currently persist the narrow contractor.verify and jurisdiction.resolve scopes. Authentication expands them only to the minimum partner.read + contractor.verify + jurisdiction.resolve runtime permissions.
- A Direct API subscription does not silently grant the broader partner-agent scopes.
REST, MCP, and signed webhooks
The versioned partner surface supports tenant-bound REST workflows, stateless MCP tools, and signed retryable webhook delivery for supported events. Availability depends on the credential's explicit scopes. The self-service Direct API key supports contractor readiness and explicit jurisdiction resolution through its narrow REST/MCP permissions; broader partner tools require separately provisioned scopes.
Designed for software and AI agents
Permit Sheriff can sit behind construction platforms, internal automation, and AI agents while preserving organization boundaries, idempotency, evidence provenance, and the same fail-closed trust rules used in the application. Broader partner integrations are provisioned deliberately rather than inferred from a self-service plan.
Direct API plans
The current self-service Direct API plans are Developer at $99/month, Growth at $499/month, and Scale at $1,499/month. They issue tenant-bound contractor-readiness credentials with explicit jurisdiction-resolution access; contractor-verification usage is metered as applicable. Broader partner-agent scopes are a separate provisioning boundary. Direct API subscriptions are separate from the Permit Sheriff Operations application plan.
Trust boundary
- Partner credentials are tenant-bound and revocable.
- Authenticated callers cannot select an arbitrary foreign tenant.
- Accepted analysis requests are idempotent to prevent duplicate billable work.
- Browser-originated MCP calls are restricted to explicitly allowed origins.
- Discovery and AI assistance do not silently become verified regulatory authority.