Coverage Cat OAuth and Agent Auth

Coverage Cat auth docs for user-claimed OAuth access, ID-JAG exchange, OTP compatibility flows, and delegated-flow guardrails.

Coverage Cat AuthOAuth 2.0Bearer Required

Coverage Cat issues user-scoped OAuth bearer tokens through a service-owned claim ceremony anchored to the operator inbox. The resulting access token identifies the operator or integration, not the end customer.

Machine-readable clients should start with /auth.md, /agent/identity, and the OAuth metadata documents; humans can still use the OTP endpoints and legacy /agent/auth compatibility flow documented below. Runtime agents should never perform setup with a customer's email.

Coverage Cat auth model

Coverage Cat exposes both public and authenticated surfaces:

  • Public: /api/agent, /api/agent/openapi.yaml, /openapi.json, /ai/skills, the runtime markdown skills, and the developer portal.
  • Authenticated: delegated umbrella purchase endpoints.

Machine-readable auth discovery

Coverage Cat also publishes a machine-readable auth surface for agents:

  • /auth.md
  • /developers/get-api-key
  • /.well-known/oauth-protected-resource
  • /.well-known/oauth-authorization-server
  • /agent/identity, /agent/identity/claim, /oauth2/token, and /oauth2/revoke
  • /agent/auth, /agent/auth/claim, and /agent/auth/revoke for compatibility

The primary path is a user-claimed OAuth flow that returns a short-lived id-jag identity assertion and then exchanges it for an access_token. The compatibility path still supports direct OTP claims for either a short-lived access_token or a longer-lived api_key.

OTP setup flow

Use the operator or integrator email, never the end-customer email. If you are reading this in a browser and want the human-readable walkthrough first, open /developers/get-api-key.

curl -X POST https://www.coveragecat.com/api/agent/key/request   -H "Content-Type: application/json"   -d '{"email":"you@yourco.com"}'

Then confirm the code and receive the key:

curl -X POST https://www.coveragecat.com/api/agent/key/confirm   -H "Content-Type: application/json"   -d '{"email":"you@yourco.com","otp":"123456"}'

Rotate with the existing bearer key:

curl -X POST https://www.coveragecat.com/api/agent/key/rotate   -H "Authorization: Bearer ccop_..."

Where Coverage Cat requires bearer auth

  • POST /api/agent/umbrella/draft
  • POST /api/agent/umbrella/quotes
  • POST /api/agent/umbrella/select
  • POST /api/agent/umbrella/bind
  • POST /api/agent/umbrella/status
  • POST /api/agent/umbrella/attach

Coverage Cat auth guardrails

  • Store the issued key in a server-side secret manager.
  • Do not embed the key in browser code or customer-visible prompts.
  • Do not use shared environment keys where Coverage Cat explicitly requires operator-issued keys.
  • Read /developers/auth before issuing a live umbrella operator key.

Multi-language starter samples

Coverage Cat’s shopper-safe consumer discovery document is the fastest starting point for a personal shopping agent. From there, call the consumer-prefill flow instead of sending the shopper straight to /umbrella.

curl https://www.coveragecat.com/api/consumer
curl -X POST https://www.coveragecat.com/api/consumer/umbrella/prefill \
  -H "Content-Type: application/json" \
  -H "Coverage-Cat-API-Version: v1" \
  -H "Idempotency-Key: demo-consumer-prefill-1" \
  -d '{"credit_consent_pending":true,"intake":{"full_name":"Taylor Example","email":"taylor@example.test","address":{"street":"123 Main St","city":"San Francisco","state":"CA","zip":"94107"}}}'
const discovery = await fetch("https://www.coveragecat.com/api/consumer").then((response) => response.json());
console.log(discovery.preferred_openapi_url);
import requests

discovery = requests.get("https://www.coveragecat.com/api/consumer", timeout=30).json()
print(discovery["preferred_openapi_url"])