New features, improvements, and fixes to the CaseVine API and platform, in reverse chronological order.
New account creation is now scored by reCAPTCHA v3. Low-scoring, automated signup attempts are rejected before an account or API key is provisioned, cutting down on throwaway trial abuse. Legitimate users see nothing — there is no checkbox or challenge to solve.
Case Alerts — email notifications when new federal litigation matches an entity you watch — is no longer Pro-only. Trial accounts can now create up to three active alerts; Pro accounts remain unlimited. Existing alerts are unaffected.
Regenerating a sandbox (cv_test_) or live (cv_live_) key now invalidates the old credential in place and records who rotated which key, and when. Rotate a leaked key from the dashboard without opening a support ticket.
Signed-in accounts that have not yet accepted the current Terms of Service and Privacy Policy are prompted to review and agree before the dashboard and API keys activate. New signups accept during onboarding, so this only catches edge cases.
A live status page now reports the health of the CaseVine API, PACER production and sandbox connectivity, and the database. It auto-refreshes every 60 seconds and is backed by the same /health endpoint used by our internal monitoring.
Party search now enforces per-key rate limits to keep the API responsive under load. Trial keys are capped at their monthly search allowance, while Pro keys flow into tiered, metered overage once the included volume is used — so a burst of traffic degrades gracefully instead of hard-failing.
Pro subscribers can now cancel directly from the billing page. Cancellations take effect at the end of the current billing period rather than immediately, so you keep paid access through the time you have already paid for. You can resubscribe at any time.
We added Google Analytics 4 (via @next/third-parties) with custom events and pseudonymous user IDs to understand how the product is used and where onboarding can improve. The collection is disclosed in our Privacy Policy.