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.
Install Jentic One Beta
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.
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" | shStep 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 instanceJentic 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.
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
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
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
/leads
Search newly registered business leads
/leads/reveal
Reveal phone and email for up to 50 leads
/contact-budget
Check remaining reveal credits for the day
/campaigns
Create a draft campaign and return a launch approval token
/campaigns/{id}/launch
Preview or launch a campaign with confirmation
/replies
List reply threads with responses
/crm/{lead_id}
Set the CRM status for a lead
/account
Read account summary, budget, and mailboxes
/leads
Search newly registered business leads
/leads/reveal
Reveal phone and email for up to 50 leads
/contact-budget
Check remaining reveal credits for the day
/campaigns
Create a draft campaign and return a launch approval token
/campaigns/{id}/launch
Preview or launch a campaign with confirmation
/replies
List reply threads with responses
/crm/{lead_id}
Set the CRM status for a lead
/account
Read account summary, budget, and mailboxes
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>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.
Alternatives and complements available in the Jentic catalogue.
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