API terms of use
This is the plain-language summary of the terms that govern use of the Dockase API. It is short because the rules are simple: use the API to build things for your users, don't use it to rebuild the corpus. By creating an API key you agree to these terms.
1.No bulk export or scraping
The API is for answering questions in your product, not for copying the corpus. Do not systematically harvest judgments, statutes, citations, or embeddings — in bulk, at scale, or through automated scraping. Per-request rate limits are not a download quota.
2.Caching is limited to 30 days
You may cache API responses for at most 30 days. After that, delete the cached copy or refresh it from the API. The law changes — treatments get overruled and statutes get amended — and stale legal data is how bad advice happens.
3.Attribution: "Powered by Dockase"
Wherever API results are displayed to end users, you must show the attribution "Powered by Dockase" in a visible and legible form. This applies to search results, judgment text, citation data, and anything derived from them.
4.No competing datasets
You may not use the API — or anything derived from it — to build, train, benchmark, or populate a competing legal dataset, search index, or research product. Using embeddings from amicus-embed-ng-v1 inside your own product is fine; using our data to recreate our product is not.
5.Enforcement
We monitor usage patterns. Violating these terms may result in suspension or termination of your API access, effective immediately, without refund. If you are unsure whether a use case is allowed, ask us at support@dockase.com before you build it.
Questions about a specific use case? Email support@dockase.com.