Install Jentic One Beta

Connect the 1Lookup API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 1Lookup API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F1lookup.io%2F1lookup" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F1lookup.io%2F1lookup" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with 1Lookup API.

Validate a phone number and return its line type, carrier, location, and reachability

Screen a phone number against spam, fraud, Do Not Call, and known-litigator lists

Verify an email address and enrich a contact record from an email, phone, or IP

Resolve company profiles, firmographics, and property records from a domain or address

Return SEO signals for a domain: domain authority, backlink overview, and keyword metrics

GET STARTED

Start building with 1Lookup API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use 1Lookup API for, with concrete tasks.

★ Agent-Driven Contact Verification

An AI agent connected through Jentic verifies a contact before any outreach: it validates the phone number for line type and reachability, screens it against Do Not Call and litigator lists, and confirms the email address is deliverable. Because every lookup returns the same success-or-error envelope, the agent branches cleanly on the result without custom parsing per endpoint.

Validate a phone number, screen it against the DNC and litigator lists, then verify the contact's email address and report which checks passed

Lead Enrichment Pipeline

A sales or RevOps workflow enriches a thin lead into a full record. Starting from an email address, the 1Lookup API enriches the contact, resolves the company profile and firmographics from the domain, and appends a phone number where one is known. The pipeline turns an email-only signup into a routable, scored lead without stitching together several vendors.

Enrich a contact from the `input` email address, resolve the company profile for its domain, and append a phone number if one is available

Outbound Compliance Scrubbing

Before an outbound dialer or SMS campaign runs, each number is scrubbed against Do Not Call and known-litigator lists and classified by number type so landlines and VoIP numbers are handled correctly. The 1Lookup API charges only when a lookup returns data, so numbers with no match do not consume credits during a large scrub.

Scrub a list of phone numbers against the DNC and litigator lists and classify each number as mobile, landline, or VoIP

Competitive SEO Research

A marketing agent gathers SEO intelligence on a competitor domain: it pulls domain authority, a backlink overview, keyword metrics, and search intent for a target query. The results feed content planning and link-building priorities, drawn from the same credit balance as the contact-data lookups.

Fetch the domain authority and backlink overview for a competitor domain and return keyword metrics for a target keyword

Key Endpoints

43 endpoints — the 1lookup api runs phone, email, ip, business, social, and seo lookups from a single endpoint set backed by one shared credit balance.

METHOD

PATH

DESCRIPTION

POST

/phone

Validate a phone number

POST

/email

Verify an email address

POST

/email-enrichment

Enrich a contact from an email address

POST

/ip

Look up an IP address

POST

/company-profile-lookup

Look up a company profile by domain

POST

/domain-authority

Get domain authority for a domain

POST

/reverse-phone-lookup

Reverse-look-up a phone number to a person or business

GET

/account

Read account status and credit balance

POST

/phone

Validate a phone number

POST

/email

Verify an email address

POST

/email-enrichment

Enrich a contact from an email address

POST

/ip

Look up an IP address

POST

/company-profile-lookup

Look up a company profile by domain

POST

/domain-authority

Get domain authority for a domain

POST

/reverse-phone-lookup

Reverse-look-up a phone number to a person or business

GET

/account

Read account status and credit balance

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the 1Lookup API by hand means managing a bearer token, tracking the one shared credit balance that every phone, email, IP, business, social, and SEO lookup draws from, and handling rate-limit retries yourself. Through Jentic you install once, import the 1Lookup API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The 1Lookup API carries every lookup target in the request body, so a rule bounds which operations your agent may call, not which number or domain. You choose the operations it may call, so the higher-cost lookups like mobile-finder and skip-trace are not included unless you add them.

Credential isolation

Your 1Lookup bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'validate a phone number' or 'enrich a contact from an email', and Jentic returns the matching 1Lookup operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using 1Lookup API through Jentic.

What authentication does the 1Lookup API use?

The 1Lookup API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec. You mint the token in your 1Lookup account and send it with every lookup. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt, logs, or context.

Can I verify an email and find a contact's phone number with the 1Lookup API?

Yes. Email verification confirms an address is deliverable, and the enrichment lookups resolve a contact from an email, append a mobile number from an identifier, or skip-trace a name and address to a phone number. Each lookup draws from the same shared credit balance, and a lookup with no match does not consume a credit.

What are the rate limits for the 1Lookup API?

The OpenAPI spec defines rate-limit response headers (a 429 response carries Retry-After and the remaining-request count) but does not state fixed numeric limits. Check https://www.1lookup.io for the current limits that apply to your plan.

Is there a 1Lookup MCP server?

Yes, 1Lookup offers a hosted MCP server. You can also connect the 1Lookup API directly through Jentic: your agent gets the full 43-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the 1Lookup API?

Yes. Because every lookup carries its target in the request body, you write a rule that allows just the operations the agent needs, such as phone validation and email verification, and leave out the higher-cost reverse-lookup, mobile-finder, and skip-trace operations. The agent can then run those checks and nothing else, and every call it makes is logged.

How do I enrich a contact from an email with the 1Lookup API through Jentic?

Import the 1Lookup API from the Jentic API Directory, store your bearer token once, and have your agent search Jentic for 'enrich a contact from an email'. Jentic returns the email-enrichment operation with its input schema, so the agent sends the `input` field and reads the enriched record. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Does the 1Lookup API charge credits per lookup?

Yes. One shared credit balance covers every product, most lookups cost one credit, and higher-cost lookups such as skip-trace and mobile-finder cost more. Failed processing, and lookups that return no match, consume no credits, and the account endpoint reports your current balance.

1Lookup API

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact Enrichmentbearer43 EndpointsREST

For Agents

Run phone, email, IP, business, social, and SEO lookups from one API: validate and scrub phone numbers, verify and enrich emails, resolve company profiles by domain, and pull domain SEO signals, all drawing on a single shared credit balance.

Use for: Validate the phone number +14155552671 and tell me its carrier and line type, Check whether a phone number is flagged for spam or fraud, Verify that an email address is deliverable before I send to it, Enrich a contact record from just an email address

Not supported: Does not handle sending messages, placing calls, or storing CRM records. Use for phone, email, IP, business, social, and SEO data lookups only.

The 1Lookup API runs phone, email, IP, business, social, and SEO lookups from a single endpoint set backed by one shared credit balance. It validates and classifies phone numbers, scrubs them against Do Not Call and known-litigator lists, verifies email addresses, enriches contact records from an email, phone, or IP, and resolves company profiles and firmographics by domain. It also returns social profile checks, audience demographics, and SEO signals such as domain authority, backlinks, and keyword metrics. Every response uses one success-or-error envelope, so an agent reads the same shape whichever lookup it calls.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

49%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

34%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

76%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the 1Lookup API to your agent

Capabilities

Start building with 1Lookup API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

1Lookup API

Jentic AI Readiness Score

1Lookup API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness