Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Data Enrichment / DayOneLead API
DayOneLead API logo

DayOneLead API

34
AI ReadinessNon-Ready (F)34/100
See full scorecard
Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer31 EndpointsREST

For Agents

Search newly registered businesses, reveal their phone and email, and run cold email campaigns from your own mailbox. Tracks replies and CRM status across 31 endpoints.

Use for: Search for newly registered businesses in Texas in the construction category, Reveal the phone and email for a short list of leads, I want to draft a cold email campaign from a plain-language description, Launch an approved email campaign and track its stats

Not supported: Does not handle payment processing, phone or SMS outreach, or contract signing. Use for finding newly registered business leads and running email outreach only.

The DayOneLead API surfaces newly registered businesses as sales leads and reveals their phone and email on demand, spending from a daily pool of reveal credits shared with CSV export. It runs cold email campaigns from your own mailbox with a preview-and-approve step before anything sends, then collects responses into threaded conversations. A built-in CRM tracks each lead through a funnel with status labels and notes, and an AI matching profile surfaces recent picks that fit your ideal customer.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the DayOneLead API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DayOneLead 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.

1

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%2Fdayonelead.com%2Fdayonelead" | sh
2

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%2Fdayonelead.com%2Fdayonelead" | 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 DayOneLead API.

Search newly registered businesses by state, category, city, or county

Reveal verified phone and email for up to 50 leads in one call, drawing on daily reveal credits

Track each lead through a CRM funnel with status labels and notes

Draft and launch cold email campaigns from your own mailbox with a preview-and-approve step

Collect campaign responses into threaded conversations and reply in context

Group leads into carts and read recent AI-matched picks against your ideal-customer profile

Use Cases

Patterns agents use DayOneLead API for, with concrete tasks.

★ AI Agent Prospecting Assistant

An AI agent connected to DayOneLead through Jentic can search newly registered businesses by location and category, reveal contact details for the strongest matches, and stage them into the CRM funnel. Because the reveal step draws on a daily credit pool, the agent can check the remaining contact budget before spending, making it a cost-aware prospecting assistant rather than a blind scraper.

Search leads for newly registered construction businesses in Texas, check the remaining reveal credits, then reveal phone and email for the top 20 and add them to the CRM

New-Business Lead Sourcing

Sales teams targeting companies in their first weeks of operation can browse DayOneLead unlimited and filter by valid states, categories, cities, and counties. Browsing is free; only revealing phone and email spends a credit per lead, so a team can qualify a long list before committing any of its 200 daily credits to the contacts worth pursuing.

List leads filtered to restaurants registered in Florida and return their masked profiles for review before revealing any contact details

Cold Email Outreach

DayOneLead sends cold email campaigns from your own mailbox rather than a shared sending domain, and campaigns use no reveal credits. Every campaign launch and reply uses a preview-and-approve flow: the first call returns a preview and an approval token, and only a second call with confirm set to true actually sends, keeping an approval gate in front of anything that reaches a prospect's inbox.

Create a draft campaign from a description, review the returned preview, then launch it by calling launch with confirm true and the approval token

CRM Funnel Tracking

Revealed leads can be tracked through a CRM funnel with status labels and free-text notes, and the funnel tree reports how contacts are distributed across stages. This lets a team or agent manage follow-up without exporting leads to a separate CRM, keeping prospecting, outreach, and pipeline state in one place.

Set the CRM status for a revealed lead to contacted and attach a note recording the outreach date

Key Endpoints

31 endpoints — the dayonelead api surfaces newly registered businesses as sales leads and reveals their phone and email on demand, spending from a daily pool of reveal credits shared with csv export.

METHOD

PATH

DESCRIPTION

GET

/leads

Search newly registered business leads

POST

/leads/reveal

Reveal phone and email for up to 50 leads

GET

/contact-budget

Check remaining reveal credits for the day

POST

/campaigns

Create a draft campaign and return a launch approval token

POST

/campaigns/{id}/launch

Preview or launch a campaign with confirmation

GET

/replies

List reply threads with responses

PUT

/crm/{lead_id}

Set the CRM status for a lead

GET

/account

Read account summary, budget, and mailboxes

GET

/leads

Search newly registered business leads

POST

/leads/reveal

Reveal phone and email for up to 50 leads

GET

/contact-budget

Check remaining reveal credits for the day

POST

/campaigns

Create a draft campaign and return a launch approval token

POST

/campaigns/{id}/launch

Preview or launch a campaign with confirmation

GET

/replies

List reply threads with responses

PUT

/crm/{lead_id}

Set the CRM status for a lead

GET

/account

Read account summary, budget, and mailboxes

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

D

DayOneLead API

- Non-Ready (F)
34/100
70
Foundational Compliance
50
Developer Experience & Jentic Compatibility
14
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
47
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
70

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4
80%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

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.

50

Developer Experience & Jentic Compatibility

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

Grade: C-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

0%

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.

14

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
3%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

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

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

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.

60

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).

47

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: D+Signals: 1
47%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring DayOneLead by hand means handling its bearer-token auth and its two-step preview-and-approve flow for launching campaigns and sending replies yourself. Through Jentic you install once, import DayOneLead from the API Directory, store the token once, and your agent calls it.

Permission scoping

DayOneLead carries lead ids and campaign ids in the URL path and request body, but the cleanest bound for it is by operation: a rule can let your agent search and reveal leads while campaign launch, reply sending, and CRM deletion stay out of its reach. You choose the operations it may call, so nothing sends to a prospect unless you add that operation.

Credential isolation

Your DayOneLead API key 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 'find newly registered business leads' or 'reveal contact details', and Jentic returns the matching DayOneLead operation with its input schema so the agent calls the right endpoint without reading the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Apollo.io API

→

Larger B2B contact and company database with built-in email sequencing, versus DayOneLead's focus on newly registered businesses.

Choose Apollo when you need broad firmographic coverage and multi-step email sequences rather than a feed of just-registered companies.

Alternative

Snov.io API

→

Email finder and cold email drip tool across any company, versus DayOneLead's new-business lead feed.

Choose Snov.io when prospects are not necessarily newly registered and you want email verification plus drip campaigns.

Complementary

AeroLeads API

→

Finds business contact details for named people and companies, complementing DayOneLead's registration-based discovery.

Use AeroLeads to enrich a lead whose contact details DayOneLead does not surface, or to cross-check a revealed email.

Complementary

FullEnrich API

→

Waterfall contact enrichment that stacks multiple providers for email and phone, complementing DayOneLead's single-source reveal.

Use FullEnrich when a DayOneLead reveal returns no contact and you want to try additional enrichment providers.

FAQs

Specific to using DayOneLead API through Jentic.

Is there a DayOneLead MCP server?

You don't need an MCP server to give your agent DayOneLead. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the lead search, reveal, campaign, and CRM operations. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

Can I limit what my agent is allowed to do with DayOneLead?

Yes. Write a rule that allows the lead search and reveal operations but not campaign launch or reply sending, so the agent can build and enrich a prospect list while outreach stays under your manual approval, and every call it makes is logged.

What authentication does the DayOneLead API use?

The DayOneLead API authenticates with a bearer token per its OpenAPI spec: a personal API key in the dl_live_ format from your dashboard, or an OAuth access token, sent in the Authorization header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only at call time.

Can I reveal lead phone numbers and emails with the DayOneLead API?

Yes. The reveal operation returns phone and email for up to 50 leads in a single call and spends one of your 200 daily reveal credits per lead, which are shared with CSV export. Searching and browsing leads is unlimited and spends no credits, and you can check the remaining budget before revealing.

What are the rate limits for the DayOneLead API?

The OpenAPI spec does not specify request-rate limits, but it does enforce a daily quota of 200 reveal credits shared between contact reveals and CSV export; campaigns send from your own mailbox and use no credits. Check dayonelead.com for current limits and plan details.

How do I launch a cold email campaign with the DayOneLead API through Jentic?

Create a draft campaign to get a preview and an approval token, review it, then call the campaign launch operation with confirm set to true and the token to send from your own mailbox. In Jentic, search for 'launch a cold email campaign', store your API key once, and the agent runs both steps. To run it on your own infrastructure, install Jentic One from its GitHub repo.

GET STARTED

Start building with DayOneLead API

Explore with Jentic One
View OpenAPI Document