Skip to content
Get started

Introduction

One API for phone, email, IP, company and registry lookups. Connect an AI client in a minute, or call it from your own code.

1lookup.dev is a data lookup API. One key and one credit balance give you 79 products that validate and enrich contact, company and network data. Every product takes a small JSON body and returns the same JSON envelope, so what you learn on one endpoint applies to all of them.

Get started

Connect your AI

Sign in through the browser.

All setup options

Add 1lookup.dev as a custom connector in Claude and sign in through the browser.

Connector URL
https://mcp.1lookup.dev/mcp
  1. Open the connector settings in Claude and choose to add a custom connector.
  2. Name it 1lookup and paste the connector URL.
  3. Approve the sign-in page that opens, then enable the connector in a new chat.
Using another MCP client? Point it at:
https://mcp.1lookup.dev/mcp

Build directly with the API

Every product is one POST endpoint. Send the identifier you have, read the result, and check the meta block for what the call cost.

  1. Create an API key

    Create an account, open API & MCP in the dashboard and create a key. Live keys start with 1lk_live_ and spend credits from your plan. Plans start at $29 a month.

  2. Send a request

    The base URL is https://api.1lookup.dev. Each product lives at /v1/{product-slug}. Send your key as a Bearer token and the input as JSON.

    Request
    curl -X POST https://api.1lookup.dev/v1/phone-validation \
      -H "Authorization: Bearer YOUR_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"phone_number":"+15125550142"}'
  3. Read the response

    Every endpoint returns the same envelope. data holds the product result, and meta tells you what the call cost and what is left.

    200 OK
    {
      "success": true,
      "data": {
        "phone_number": "+15125550142",
        "valid": true,
        "line_type": "mobile",
        "carrier": {
          "name": "Example Wireless",
          "ocn": "6010",
          "lrn": "+15125550000",
          "ported": true
        },
        "location": {
          "city": "Austin",
          "state": "TX",
          "country": "US",
          "timezone": "America/Chicago"
        },
        "dnc": {
          "listed": false,
          "dno": false
        },
        "risk": {
          "level": "low",
          "factors": []
        }
      },
      "meta": {
        "credits_used": 1,
        "credits_remaining": 999,
        "cached": false,
        "request_id": "req_8f3a2c1e9b7d"
      }
    }
    successboolean

    true when the lookup ran. A false response carries an error object instead of data.

    dataobject

    The product result. Its fields are documented on each endpoint page.

    meta.credits_usedinteger

    Credits charged for this call. 0 for cached repeats, misses on match-priced products and failures.

    meta.credits_remaininginteger

    Your balance after the call.

    meta.cachedboolean

    true when the result came from the 7-day cache.

    meta.request_idstring

    Quote this when you contact support.

Request options

These optional fields are accepted by every endpoint, alongside the product's own fields.

freshboolean

Skip the 7-day cache and run a new lookup. Charged as a normal lookup.

referencestring

Your own identifier, echoed back in meta and shown in lookup history.

What you can look up

The 79 products are grouped by the kind of data they return. Each group links to its endpoints in the API reference.

Where next