Acceptable use

Last updated September 27, 2026

Effective [ACCEPTABLE USE EFFECTIVE DATE]

These rules are part of the terms of service. They cover what you do with the service and with the records it returns, and the technical limits every key works under. The API enforces the limits and answers with the error named next to each. URAKIMON can suspend an account that breaks any rule, as the terms describe.

1. Lawful use

You must use URAKIMON and records only for lawful purposes and in line with the laws that apply to you, including data protection, consumer protection, anti-spam, competition, and intellectual property law. You may not use the service to break the law or to help someone else break it, or for anything libellous, fraudulent or deceptive.

2. People and personal data

Records can contain information about people. For that information you must have a lawful basis for what you do with it, tell people what the law requires you to tell them, keep it secure, and keep it only as long as you need it. In particular, you may not use records to:

profile or single out people by health, religion or beliefs, ethnicity, political views, trade union membership, sex life or sexual orientation, or criminal records, or infer any of these;
identify people from their face, voice or other biometric traits, or build biometric templates;
stalk, harass, intimidate, threaten or bully anyone, or publish someone's private information (their home address, private phone number or email, or similar) to expose or target them;
decide whether a person is eligible for credit, insurance, employment, housing or a similar benefit, or supply information for such decisions, as a consumer report or otherwise;
re-identify people where a source shows information without a name, or combine records to reveal who is behind an anonymous post or review;
send unsolicited messages, emails or calls, or build contact lists for them, without a lawful basis and the consent the law requires;
sell, license, share or publish personal information from records as a dataset, a list or in bulk;
keep using information about someone after they have objected to your use of it or asked you to remove it, unless the law lets you refuse.

You must answer the requests that people send you about their information in records (access, correction, deletion, objection) as the data protection laws that apply to you require. People in records explains what URAKIMON itself does.

3. Content and rights

You may not use records in a way that infringes anyone's copyright, database right, trademark, right of publicity or other right, or in breach of terms you yourself have accepted with a source. You may not present records as coming from, or endorsed by, a source or URAKIMON when they are not, or impersonate anyone.

4. Protecting the service

You may not attack, overload, probe or get around the limits of URAKIMON or of any source through URAKIMON; use it to gain access to any account, system or data you are not allowed to reach; share or sell your keys; open accounts to claim trials more than once; or send harmful code through it.

5. What a request may name

Every URL in a request must belong to the source you call: URLs sent to Amazon must be Amazon URLs, and so on. A request that names a URL on another host is refused with 400, and the message names the host.
A webhookUrl must be a public http or https address. An address that points at a private, local or internal network is never called.

6. Limits

Requests: 120 per minute for a new account, shared by all its keys. Past it, the API answers 429 with a Retry-After header.
Jobs: 2 running at once and 10 waiting per key. A further job is refused with 429 until one finishes.
Requests that bill nothing because of what was sent (invalid inputs, searches that find nothing): 20,000 a day, and 2,000 MB of data for them, per account. Records you are billed for never count, and neither do our own failures.
Webhook deliveries: up to 1,000 per key per UTC day.

Paid work has no cap: records you are billed for are limited only by your credit.

7. Keys

Send a key in the x-api-key header. A key in a URL's query string is refused.
After 20 requests with a wrong or missing key from one address within a minute, that address is refused with 429 until the minute passes.

8. Trial credit

A mailbox gets the trial credit once. Disposable and relay mail domains get none, and one network gets at most 2 trials in 30 days. Trial credit has the details.

9. Reporting misuse

To report misuse of URAKIMON or of records, write to [LEGAL EMAIL]. For your own information in records, see People in records; for copyright, see Copyright.

10. Changes to these rules

When this page changes, we post the new version here at least 30 days before it applies, and the effective date at the top changes with it. A change that the law, a court or an authority requires can apply sooner, from when we post it.