Lookups should be boring
Checking a phone number, verifying an email or pulling a company record is plumbing. It should be one request, one predictable price and one response shape. 1lookup.dev exists to make 79 of those jobs that boring.
Why one API
A team that validates phone numbers soon needs to verify emails. Then score signups. Then enrich the accounts that convert, screen the vendors it pays and check the carriers it books. Each of those is usually a different provider, with its own contract, key, quota, dashboard and response format.
That sprawl is the problem we set out to remove. One key. One balance of credits that works on everything. One place to see what was looked up and what it cost. The catalog is wide on purpose, so the next job is an endpoint you already have access to.
We are an independent service and are not affiliated with other companies that have similar names. You can reach us at 1lookup@volods.com.
How we decide things
Publish the price
Every product lists what it costs in credits. You should be able to price a workload from a public page, not from a sales call.
Charge for answers
If we fail, you do not pay. If a match-priced product finds nothing, you do not pay. If you ask the same question twice in a week, you do not pay twice.
Name the source
Where data comes from an official registry, the response says which one. Where a figure is an estimate, it is labeled as an estimate.
One shape for everything
The same envelope, the same auth and the same error format across the whole catalog, so the second product takes minutes to add.
Built for agents too
An AI assistant is now a first-class user of an API. The MCP server is not an afterthought. It exposes the full catalog.
Say what it is not for
Some data is sensitive. We publish what our products may not be used for and gate the ones that need a closer look.
Run your first lookup in two minutes
Create a key, pick a plan and call any product in the catalog. Plans start at $29 a month.