Developer
$99/month
50 contractor checks per billing month included; $2.00 per additional check.
- Contractor-readiness REST access
- Private organization-bound API key
- Postman and server-to-server workflows
CONTRACTOR READINESS API
Catch contractor readiness gaps before they cost your team another handoff.
Bring project-specific contractor checks into your software. Get a readiness result, supporting checks, blockers, and next actions for covered requirements.
Contractor checks are a focused API product. Full permit-package analysis is a separate $499 purchase.
DIRECT API PRICING
Choose the volume your workflow needs.
Growth
$499/month
500 contractor checks per billing month included; $1.00 per additional check.
- Contractor-readiness REST access
- Private organization-bound API key
- Postman and server-to-server workflows
Scale
$1,499/month
2,500 contractor checks per billing month included; $0.50 per additional check.
- Contractor-readiness REST access
- Private organization-bound API key
- Postman and server-to-server workflows
Monthly fee charged at the start of each billing period. Overage is billed after usage. Included checks reset each billing month and do not roll over. Prices are in USD; applicable taxes may be added. The plans differ by usage allowance, not broader partner permissions.
Know what you are checking.
Contractor readiness compares contractor and project information against supported requirements. Published coverage starts with South Carolina commercial contractor requirements and covered Charleston and Horry County local authorization gates. Check the coverage endpoint before submitting a project; supported rules and available evidence determine the result.
Results can be ready, blocked, or manual_review. Missing evidence stays unresolved. A readiness result is not a municipal permit approval, and jurisdiction resolution is not a promise of verified local-code coverage.
One billable check is a recorded contractor-readiness assessment. Coverage discovery and jurisdiction context are not full permit-package analyses. Reuse the same Idempotency-Key when retrying the same assessment.
From plan to first request.
- Choose a plan, then sign in or verify your Permit Sheriff organization.
- Review the monthly fee and usage terms in Stripe Checkout.
- Return to the developer portal after entitlement activation and create your private API key.
- Use the key in Postman as permitSheriffApiKey or in your server integration. Check coverage, then submit a contractor-readiness assessment.
One product, clearly defined access paths.
Direct API + Postman
Buy the plans above through Stripe. Postman is a request and testing client; it does not provide a separate paid entitlement.
RapidAPI
Subscribe through the RapidAPI listing under its own prices and terms. Its marketplace credentials and billing are separate; a RapidAPI subscription does not activate a direct Stripe API plan.
Partner integrations
AWS Marketplace, Autodesk, and Procore workflows have separate commercial and integration requirements. This subscription does not grant broader permit-analysis permissions or imply partner approval.
Technical scope and trust boundaries
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, 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; 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.
What the result establishes
Supported analysis returns findings, evidence references where available, processing status, and next actions. Inspect unresolved items and coverage limits before relying on a result. A ready Permit Intelligence Packet means the work product is assembled, not that a municipality has approved the permit.
Jurisdiction resolution reports available context and trust state; it is not a promise of verified local-code coverage. Unavailable context stays unavailable. Use the deployed discovery and tools/list responses to determine which tools your credential can use. Missing signatures, timestamps, or other verification records must not be treated as verified.
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.