For Agents
Find and profile companies: search by name and country, get a company profile and corporate hierarchy with provenance, and read contact previews without spending reveal credits.
Use for: Search for companies by name and country, Get a company profile with its data provenance, Retrieve a company's corporate-group hierarchy, Find contact previews for a company
Not supported: Does not reveal email or mobile credits, send outreach, or store your data. Use for company lookups, corporate hierarchy, and contact previews only.
The EntityReach API finds and profiles companies for workspaces with activated API access. An agent searches companies by name and country, retrieves a company profile with data provenance, reads the available corporate-group hierarchy, and pulls contact previews for a company. Each successful request, including an empty search, consumes one monthly unit, and contact discovery returns previews without spending email or mobile reveal credits.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EntityReach 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%2Fentityreach.com%2Fentityreach" | 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%2Fentityreach.com%2Fentityreach" | 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 EntityReach API.
Search for companies by name and country
Retrieve a company profile with data provenance
Read a company's available corporate-group hierarchy with provenance
Find contact previews for a company without spending email or mobile reveal credits
Patterns agents use EntityReach API for, with concrete tasks.
★ Agent company lookup with provenance
An agent researching a prospect searches EntityReach by name and country, picks the right match, and retrieves the company profile with data provenance so it can cite where each field came from. The search and profile operations are discovered through Jentic by intent, so the agent resolves a company to a profile without reading the reference docs.
Search for a company by name and country, then retrieve the best match's profile and note the provenance of key fields
Corporate hierarchy mapping
Map a company's ownership by reading its available corporate-group hierarchy with provenance. An agent can take a company id and build the parent and subsidiary structure for a diligence or account-planning task.
Retrieve a company's corporate-group hierarchy and list its parent and subsidiary entities with provenance
Contact discovery without burning credits
Preview the contacts at a company without spending email or mobile reveal credits by calling the contacts operation, which supports page and role parameters. An agent can scan who is reachable at an account before deciding where to spend reveal credits elsewhere.
Fetch contact previews for a company filtered by role, and list the reachable contacts without revealing email or mobile
4 endpoints — the entityreach api finds and profiles companies for workspaces with activated api access.
METHOD
PATH
DESCRIPTION
/companies
Find companies by name and country
/companies/{id}
Get a company profile with provenance
/companies/{id}/group
Get the available corporate hierarchy
/companies/{id}/contacts
Find contact previews for a company
/companies
Find companies by name and country
/companies/{id}
Get a company profile with provenance
/companies/{id}/group
Get the available corporate hierarchy
/companies/{id}/contacts
Find contact previews for a company
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 the EntityReach API by hand means handling its bearer companies:read key (shaped er_live_), staying under its per-workspace request limit, and tracking the monthly unit each request consumes yourself. Through Jentic you install once, import the EntityReach API from the API Directory, store the key once, and your agent calls it.
Permission scoping
EntityReach puts the company id in the URL path (/companies/{id}), so a rule can pin your agent to one company: it can read that company's profile, group, and contacts and nothing else. You choose the operations it may call, so any you leave out stay off.
Credential isolation
Your EntityReach 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 'search companies by name' or 'get a company profile', and Jentic returns the matching EntityReach operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using EntityReach API through Jentic.
What authentication does the EntityReach API use?
Per its OpenAPI spec, the EntityReach API authenticates with a bearer companies:read key (shaped er_live_ followed by 64 hex characters), created by a workspace owner with active API access. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I search for companies with the EntityReach API?
Yes. The search operation finds companies by name and country, and from a match you can retrieve the company profile, its corporate-group hierarchy, and contact previews, all returned with data provenance.
What are the rate limits for the EntityReach API?
The OpenAPI spec notes 60 valid requests per minute per workspace, and each successful request, including an empty search, consumes one monthly unit that resets at 00:00 UTC on the first of the month. Failed provider requests refund the unit but still count toward the per-minute limit.
Is there an EntityReach MCP server?
You don't need an MCP server to give your agent the EntityReach API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the search, profile, group, and contacts operations it needs.
Can I limit what my agent is allowed to do with the EntityReach API?
Yes. Because EntityReach carries the company id in the URL path, you can pin a rule to one company and allow only the profile and contacts operations, so the agent reads that company and nothing else. Any operations you leave out stay off, and every call the agent makes is logged.
How do I look up a company through Jentic?
Search Jentic for 'search companies by name', and it returns the EntityReach search operation with its input schema; your agent supplies the name and country and calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED