Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Scalelist 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%2Fscalelist.com%2Fscalelist" | 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%2Fscalelist.com%2Fscalelist" | 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 Scalelist API.
Find a verified work email from first_name or full_name plus company_domain or company_name, charged 1 credit only when found
Find a direct mobile number from linkedin_profile_url, linkedin_id, an email, or a name and company, at 10 credits per number found
List the professional emails known at a company by domain or company name, with a limit of up to 100
Search for people by job_titles, seniority, industries, locations, company_domains, skills, and exclusion filters, paging with page
GET STARTED
Size an audience with the people count operation for 1 credit per call before paying for profiles
Run bulk email, phone, or people jobs of up to 100 per call and collect results by webhook_url or by polling with job_id
Check which industry names a search will match, getting resolved, unresolved, or unverified with suggestions
Patterns agents use Scalelist API for, with concrete tasks.
★ AI agent enriching a lead list
An agent handed a list of names and companies searches Jentic for 'find a work email', loads the single email lookup, and runs each person through it, or sends up to 100 at once to the bulk operation with a webhook_url and an Idempotency-Key. It then fills in emails only where one was found, since credits are charged only on a hit, and the Scalelist key is injected at call time.
POST /api/v1/email/find/single with first_name Jane, last_name Doe, and company_domain acme.com, and return the email if one is found
Building a prospect audience
Sales teams define their ideal buyer and need a list. People search combines filters where values inside one list are OR and separate fields are AND, such as seniority VP or Director with industries Banking or Insurance in a set of locations. The count operation sizes the audience for 1 credit per call before any profiles are bought, and the industry resolver confirms which industry names will actually filter.
POST /api/v1/people/count with seniority ['VP'], job_functions ['Engineering'], and locations [{country: 'Germany'}], and if under 500 run POST /api/v1/people/search with the same filters
Getting a direct mobile number
For high-value outreach a phone number matters more than an email. The mobile lookup accepts any one of a LinkedIn profile URL or numeric linkedin_id, an email, or a name and company, with job_title and city to sharpen the match, and costs 10 credits per number found. Bulk phone jobs take up to 100 people per call.
POST /api/v1/phone/find/single with linkedin_profile_url https://www.linkedin.com/in/janedoe and return the mobile number if found
15 endpoints — the scalelist api finds verified work emails and direct mobile numbers for the people you want to reach, running each lookup through a waterfall of data providers and charging only when it finds something.
METHOD
PATH
DESCRIPTION
/api/v1/email/find/single
Find an email address
/api/v1/email/find/bulk
Find up to 100 emails in bulk
/api/v1/email/find/domain
Find emails by company domain
/api/v1/phone/find/single
Find a mobile number
/api/v1/people/search
Search for people
/api/v1/people/count
Count matching people
/api/v1/email/verify/single
Verify an email address
/api/v1/account
Get account plan and credit balance
/api/v1/email/find/single
Find an email address
/api/v1/email/find/bulk
Find up to 100 emails in bulk
/api/v1/email/find/domain
Find emails by company domain
/api/v1/phone/find/single
Find a mobile number
/api/v1/people/search
Search for people
/api/v1/people/count
Count matching people
/api/v1/email/verify/single
Verify an email address
/api/v1/account
Get account plan and credit balance
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Scalelist by hand means sending an x-api-key header, handling anyOf input rules for names, companies, and LinkedIn identifiers, and running bulk jobs with webhooks, polling, and Idempotency-Key retries. Through Jentic you install once, import Scalelist from the API Directory, store the key once, and your agent calls it.
Permission scoping
Scalelist carries the person and company inside the request body, so rules bound which operations your agent may call, such as single email lookups, not which people it looks up. You choose the operations it may call, so credit-heavy ones like phone lookups or bulk people search are not included unless you add them.
Credential isolation
Your Scalelist 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 a work email' or 'search for people by job title', and Jentic returns the matching Scalelist operation with its input schema, including which name and company fields it needs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Scalelist API through Jentic.
What authentication does the Scalelist API use?
Per its OpenAPI spec, the Scalelist API uses an API key sent in the x-api-key header, and a missing or unrecognised key returns 401. You create the key on the API keys page of your Scalelist account. Through Jentic the key is stored by your own instance and attached at call time, so it stays out of the agent's context.
How much does a Scalelist lookup cost?
Per the spec, a work email costs 1 credit, a mobile number 10 credits, and a person profile 1 credit, charged only when something is found. A people count costs 1 credit per call however large the audience, and polling bulk results does not consume credits.
How do bulk lookups work in Scalelist?
Bulk email, phone, and people operations accept up to 100 requests per call and return a task id straight away. Supply webhook_url to have results POSTed when the batch finishes, or poll the matching GET operation with job_id. Send an Idempotency-Key header to retry safely.
What are the rate limits for the Scalelist API?
The OpenAPI spec does not specify rate limits. Check the Scalelist reference at https://api.scalelist.com/llms.txt for current limits.
Is there a Scalelist MCP server?
You don't need an MCP server to give your agent Scalelist. Jentic connects it directly from the API Directory: import it, store your Scalelist key once, and your agent calls the email, phone, and people operations when it needs them.
How do I find a work email with Scalelist through Jentic?
Search Jentic for 'find a work email', load the single email lookup, and execute POST /api/v1/email/find/single with first_name or full_name plus company_domain or company_name. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Scalelist API?
Yes. Allow only POST /api/v1/email/find/single and POST /api/v1/people/count, and the agent can look up one email at a time and size audiences, while the 10-credit phone lookups and bulk jobs stay outside its rule. Every call it makes is logged.
For Agents
Find verified work emails and mobile numbers from a name and company or a LinkedIn URL, list emails at a company domain, and search or count people by title, seniority, industry, and location.
Use for: Find the work email for Jane Doe at acme.com, Get the mobile number for this LinkedIn profile, List all known emails at stripe.com, Search for VPs of Engineering at fintech companies in Germany
Not supported: Does not send emails, place calls, or store contacts in a CRM. Use for finding and verifying work emails, mobile numbers, and people profiles only.
The Scalelist API finds verified work emails and direct mobile numbers for the people you want to reach, running each lookup through a waterfall of data providers and charging only when it finds something. It finds an email from a name and a company, a mobile number from a LinkedIn profile, an email, or a name and company, and the known emails at a company domain with no names needed. People search builds audiences by job title, seniority, industry, location, company, and dozens of other filters, with a count call to size an audience first. Single lookups return directly, and bulk jobs of up to 100 deliver results by webhook or polling.
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>