Free lookup tools that need no account

A free tool is a normal lookup with no charge and a per-visitor limit. The pages on the free tools page call the same lookups that the API runs, so a result you see in the browser has the same fields as the one your code would receive.

The same lookups are also reachable without a key from code. The HTTP endpoint is POST https://YOUR_API_HOST/v1/public/tools/<product>, and the MCP server at https://YOUR_API_HOST/v1/mcp offers only the free tools when you connect with no Authorization header. One lookup is deliberately left out: website-scraper, which returns full page text, needs a key and credits.

There is one page per tool, and two tools can sit on the same product. The email domain check, for example, backs both the email domain checker and the DMARC checker. The last column is what the same lookup costs through the API when it finds something, so you can estimate a workload before you create a key.

The IP address lookup, the phone number validator and the site files checker are good first stops: each one runs a live lookup on a value you type, and the page explains how to read the result.

By default a visitor can make 5 free lookups per 60 seconds and 25 per day. The two transports share one allowance, so calling the HTTP endpoint and the keyless MCP server does not double it. Listing the MCP tools costs nothing.

• Who counts as a visitor: the client address the API sees. An IPv6 visitor is counted by its /64 block, so rotating inside one block does not reset the count.
• The daily count resets at midnight UTC. A call that a cap refuses is not counted against the daily allowance.
• website_contacts_scraper crawls at most 3 pages without a key, whatever page count you ask for.
• A shared daily capacity and a small concurrency cap protect paying traffic. If you hit either, the response says so and tells you to retry or use a key.

When a limit is reached the answer is a rate_limited error with the number of seconds to wait. These are the default values, and the numbers above are read from the same constants the API uses.

Both paths run the same code: one lookup engine, the same input check, the same data sources. What changes is around the lookup, as the table shows.

Because the free cache is shared and the API cache is per account, running a lookup in the browser does not make the same lookup free on your key. The first keyed lookup of a value is a normal one.

Stay on the free tools while you are checking what a lookup returns. Move to a key when you need more than 25 lookups a day, when you want website-scraper, when you want your balance and usage in the response, or when the lookup belongs inside a signup form, a CRM job or an agent. Here is the same IP lookup both ways.

1curl -X POST https://YOUR_API_HOST/v1/public/tools/ip \
2  -H "Content-Type: application/json" \
3  -d '{"ip":"8.8.8.8"}'

1curl -X POST https://YOUR_API_HOST/v1/ip \
2  -H "Authorization: Bearer $LOOKVALID_API_KEY" \
3  -H "Content-Type: application/json" \
4  -d '{"ip":"8.8.8.8"}'

The body you send is identical. The keyed call costs 1 credit when it finds something and adds the credit fields to the answer. To set it up, follow the quickstart and run the keyed call yourself.