Authentication depends on the consumer or delegated operator workflow. For a person shopping with an assistant, start with consumer discovery. Public consumer umbrella prefill does not require an operator API key; later operations have their own authentication and consent requirements. Connected assistants follow the authentication rules for their connection.
The key issuance instructions below apply to authorized delegated operators.
Key issuance
POST /api/agent/key/requestsends a 6-digit OTP to the operator email.POST /api/agent/key/confirmexchanges the OTP for a bearer token.POST /api/agent/key/rotaterotates the active token and invalidates the old one.
Which flows need which key
- Delegated umbrella purchase uses a bearer key.
New homeowners application and quote workflows are unavailable. Existing homeowners policy support remains available through the authorized intake or account context.
Rate limits
The public discovery document advertises two baseline limits:
- authenticated operator traffic: 30 requests per minute
- IP fallback traffic: 8 requests per minute
Build retries with backoff, avoid guessing endpoint names, and start from the discovery document or OpenAPI map instead of probing the API surface.
Recovery and operational notes
- Store keys in a secret manager and distribute them to runtime agents out of band.
- Rotate keys proactively before expiry.
- Use a real operator or integrator email for key issuance, never a customer's intake email.
Next steps
- Learn: Read What Coverage Cat does, browse insurance guides, or scan the FAQ.
- Estimate: Use the home insurance calculator, umbrella insurance calculator, or carrier price comparison.
- Compare: Start a Coverage Cat quote comparison when you want licensed broker help and real quotes.
- Integrate: Explore the Coverage Cat Agent API hub, the discovery document, and the OpenAPI spec.