For AI developers
Hand a customer off safely. PolicyShark completes the protected scan.
Your assistant can initiate a scan without handling a policy document. Create one handoff URL, send the customer to PolicyShark, and let them upload and consent on our site.
Privacy boundary
We do not accept customer documents through intermediaries; consent and upload happen only on our site, so our Privacy Pledge stays verifiable.
Accepted request fields
JSON only: src, state, renewal, and optional email. Sources normalize to claude, chatgpt, perplexity, gemini, or other. State must be a U.S. postal abbreviation and renewal uses YYYY-MM-DD.
Do not send documents, files, policy contents, SSN, VIN, driver license, address, phone, name, insurer, or coverage fields. Multipart and document-like payloads are rejected.
Create a handoff
POST https://policyshark.ai/api/agents/handoffs
Content-Type: application/json
{"src":"claude","state":"GA","renewal":"2026-11-01","email":"optional@example.com"}The response includes an unguessable handoffUrl. Open it in the customer’s browser. It pre-fills the allowed fields on /scan, tags the eventual case with your source, and can be used once. Unused handoffs expire after 14 days.
Limits and outcomes
The endpoint permits 12 creation attempts per hour for a request fingerprint. With an email, an active handoff or actual case for the same normalized email and renewal date is not duplicated. Without an email, no dedupe is attempted so unrelated customers are not merged.
PolicyShark is a comparison and switching service, not an insurance brokerage. A handoff starts no broker request, does not promise quotes or savings, and does not replace customer consent.