One API key for every lookup
LookValid is one API key and one credit balance for many lookup products: phone numbers, email domains, IP addresses, domains and websites. You call a product, get a JSON answer, and spend credits only when the lookup finds something.
curl -X POST https://YOUR_API_HOST/v1/ip \
-H "Authorization: Bearer $LOOKVALID_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ip":"203.0.113.7"}'
const response = await fetch("https://YOUR_API_HOST/v1/ip", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOKVALID_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"ip": "203.0.113.7"
}),
});
const result = await response.json();
if (!response.ok) throw new Error(`${result.error.code}: ${result.error.fix}`);
console.log(result.found, result.data, result.credits_charged);
import os
import requests
response = requests.post(
"https://YOUR_API_HOST/v1/ip",
headers={"Authorization": f"Bearer {os.environ['LOOKVALID_API_KEY']}"},
json={
"ip": "203.0.113.7",
},
timeout=30,
)
result = response.json()
if not response.ok:
raise RuntimeError(f"{result['error']['code']}: {result['error']['fix']}")
print(result["found"], result["data"], result["credits_charged"])
Set up your agent
Hand your coding agent the playbook at /get-started.md. It gets a key, installs the MCP server and makes a first call.
Set up LookValid for me. Fetch https://lookvalid.com/get-started.md and follow it.
- QuickstartGet a key and make your first request in cURL, Node.js or Python.
- MCP serverGive your agent every lookup as a tool, on the same key and balance.
- API referenceEvery endpoint, its request body, its fields and what it costs.
- ClaudeAdd the MCP server to Claude Code with one command, or as a connector in the Claude apps.
- CursorAdd the MCP server to Cursor with a key read from your environment.
- MCP sign-inConnect a client with a browser approval and short-lived tokens instead of a stored key.
What's new
The latest changes to LookValid. The full list is in the changelog.
- MCP server for AI agents
The MCP server speaks streamable HTTP, takes your API key as a bearer token and exposes every lookup as a tool, plus
get_accountfor your balance and keys. - Documentation, OpenAPI and llms.txt
The documentation covers the base URL and authentication. A plain-text guide for agents is at
https:/./ lookvalid.com/ llms.txt - 14 lookups on one key
One API key and one credit balance now cover these lookups. Each is a POST to its own path under https://YOUR_API_HOST.
Lookups
Every lookup takes the same API key and spends from one credit balance. The API reference lists all of them.
- Phone Numbering-Plan ValidationChecks a phone number against its country's numbering plan and returns E.164, national and international formats, the country and the number type the plan assigns (mobile, fixed line, toll free, VoIP and others).
- Email Domain CheckChecks the domain behind an email address: MX records, SPF and DMARC policies, and whether the address uses a disposable domain, a free mailbox provider or a role mailbox such as info@ or support@.
- IP IntelligenceLocation and network details for an IPv4 or IPv6 address (country, region, city, time zone, ASN and network owner) with risk flags from open lists such as Tor exit nodes and cloud provider ranges.
- Domain AgeRegistration, last update and expiry dates, registrar and age in days for a domain, from the registry's public RDAP service.
- Website Contacts ScraperReads a domain's public pages and returns the email addresses, phone numbers and social profile links they publish.
- Site Files CheckerReads the files a site publishes for crawlers, SEO tools and AI agents (robots.txt, its sitemaps, llms.txt, llms-full.txt, security.txt and ai.txt) and explains each one in plain words: present or missing, parse errors and warnings, robots.txt groups and rules with a URL tester, which known AI crawlers are allowed, sitemap URL counts and families, sitemap URLs that robots.txt blocks, llms.txt structure and security.txt required fields and expiry.