Acceptable use policy
Use amodb data in your own apps, websites, bots and research, and cache it to save requests. Do not share or publish keys, resell raw API access or bulk dumps, open extra accounts to raise your rate, or probe and overload the service. Breaking these rules can suspend a key or close an account.
You may
- Show amodb data in your apps, websites, media servers, bots and internal tools.
- Cache responses on your side to save requests and speed up your product.
- Use the data for research and analysis.
- Show images from
img.amodb.devnext to the matching records.
You may not
- Share, sell or publish your keys, or put them in client side code.
- Resell or give away raw API access, for example by running a proxy that others call with their own requests.
- Publish bulk dumps of API responses as a dataset.
- Open extra accounts or rotate keys to get more than your plan rate.
- Send traffic meant to overload the service, scan for weak points or get around the rate limit.
- Try to find out or call the upstream sources behind amodb.
- Use the data for unlawful content, spam or to mislead people.
- Present your product as TMDB, IMDb, OMDb or amodb, or suggest that any of them endorse it.
What happens on a breach
- We contact you at your account email when the breach allows it.
- We may suspend the key. It returns HTTP 401 with
status_code10. - For serious or repeated breaches we close the account. Prepaid time is not refunded.
Report abuse
If you find a leaked amodb key or see abuse of the service, write to support@amodb.dev. Include where you found it.