Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Datahyena Public 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%2Fdatahyena.com%2Fdatahyena" | 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%2Fdatahyena.com%2Fdatahyena" | 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 Datahyena Public API.
List recent funding events across private-market companies
Track acquisitions and the companies involved in each deal
Monitor executive moves to see who changed roles and where
Retrieve a chronological event timeline for a single company
Fetch event timelines for a batch of companies in one request
GET STARTED
Look up investors and the companies they are associated with
Patterns agents use Datahyena Public API for, with concrete tasks.
★ Deal-Flow Monitoring Agent
An AI agent watches private-market activity for a venture or corporate-development team. It lists new funding events and acquisitions, cross-references the companies involved, and builds a running digest. The agent discovers each Datahyena operation through Jentic by intent, so it reads funding events and acquisitions without hardcoding the endpoint paths.
List the latest funding events and acquisitions, then compile a digest of the companies that raised or were acquired
Investor Research
An analyst needs the activity profile of an investor and the companies they are associated with. The agent looks up the investor, then pulls the event timeline for each company to show how recent each event is. Datahyena returns the investor and company records read-only, so the agent assembles the profile without writing any data back.
Look up an investor by name and return the companies they are linked to with each company's event timeline
Executive-Move Alerts
A sales or recruiting team wants to know when leaders change roles at target accounts. The agent lists executive moves, filters to the companies on its watchlist, and surfaces the relevant changes. Because the endpoint is read-only, the agent polls it on a schedule and reports new moves.
List recent executive moves and return only those at companies on a given watchlist
7 endpoints — the datahyena api serves read-only market intelligence on private-company activity, listing funding events, acquisitions, and executive moves alongside the companies and investors behind them.
METHOD
PATH
DESCRIPTION
/v1/funding-events
List funding events
/v1/acquisitions
List acquisitions
/v1/exec-moves
List executive moves
/v1/companies
List companies
/v1/companies/timeline
Get a single company's event timeline
/v1/companies/timeline
Get event timelines for multiple companies
/v1/investors
List investors
/v1/funding-events
List funding events
/v1/acquisitions
List acquisitions
/v1/exec-moves
List executive moves
/v1/companies
List companies
/v1/companies/timeline
Get a single company's event timeline
/v1/companies/timeline
Get event timelines for multiple companies
/v1/investors
List investors
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Datahyena by hand means issuing an API key, sending it in the X-API-Key header on every request, and parsing its JSON list responses yourself. Through Jentic you install once, import Datahyena from the API Directory, store the key once, and your agent calls it.
Permission scoping
Datahyena is read-only, so the strongest rule is which datasets your agent may read: you can allow funding events and acquisitions while leaving investor or executive-move lookups out unless you add them. You choose the operations it may call.
Credential isolation
Your Datahyena 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 list recent funding events or get a company timeline, and Jentic returns the matching Datahyena 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 Datahyena Public API through Jentic.
What authentication does the Datahyena API use?
The Datahyena API authenticates with an API key sent in the X-API-Key request header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's prompt or logs.
Can I track funding events with the Datahyena API?
Yes. The funding-events operation lists funding rounds raised by private-market companies, and the acquisitions operation covers M&A activity. Combine either with the company timeline operation to see how recent each event is for a specific company.
What are the rate limits for the Datahyena API?
The OpenAPI spec does not publish rate limits for the Datahyena API. Check Datahyena's own API documentation for the current per-key limits before scheduling frequent polling.
Can I limit what my agent is allowed to do with the Datahyena API?
Yes. Datahyena is read-only, so a rule can allow just the datasets the agent needs, such as funding events and acquisitions, while leaving investor and executive-move lookups out unless you add them. Every call the agent makes is logged.
How do I pull a company timeline with the Datahyena API through Jentic?
Search Jentic for an intent like get a company event timeline, store your Datahyena key once, and your agent calls the timeline operation for a single company or the bulk variant for a list. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Datahyena MCP server?
You don't need an MCP server to give your agent the Datahyena API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the operations it needs on demand.
For Agents
Read funding events, acquisitions, executive moves, companies, and investors from Datahyena. Pull a chronological event timeline for one company or request timelines for several companies at once.
Use for: List recent funding events, Find acquisitions in a given sector, Track executive moves at a target company, Get the event timeline for a company
Not supported: Does not handle contact enrichment, CRM syncing, or outreach. Use for reading funding events, acquisitions, executive moves, and investor data only.
The Datahyena API serves read-only market intelligence on private-company activity, listing funding events, acquisitions, and executive moves alongside the companies and investors behind them. A per-company timeline endpoint assembles those events into a chronological history for one company, and a bulk variant returns timelines for many companies in a single request.
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>