Install Jentic One Beta

Connect the HEY Research Lab public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HEY Research Lab 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%2Fheyresearch.xyz%2Fheyresearch" | sh

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%2Fheyresearch.xyz%2Fheyresearch" | 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 HEY Research Lab public API.

Search and browse published Robinhood Chain projects by name, symbol, kind, status, or narrative

Read one project's dossier, snapshot, coverage, and timeline with every claim tagged FACT, DERIVED, or UNKNOWN

Compare what changed for a project between two dates with the diff and change-ledger reads

Resolve a token contract address on chain 4663 to its published project, or up to 30 contracts in one keyed call

GET STARTED

Start building with HEY Research Lab public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HEY Research Lab public API for, with concrete tasks.

★ Agent research on a Robinhood Chain token

An AI agent asked about a token on Robinhood Chain needs sourced facts, not a guess. Through Jentic the agent searches for 'resolve a token contract to a project', loads the HEY lookup operation, and passes chain id 4663 and the contract address. It then reads the project snapshot and coverage, so its answer separates what HEY records as fact from what HEY marks unknown, each with a source.

Call GET /api/token/{chainId}/{address} with chainId 4663 and a 0x contract address, then call GET /api/projects/{slug}/snapshot for the returned project slug and summarise its FACT and UNKNOWN lines

Builder activity monitoring

A research desk tracking who is actually shipping on Robinhood Chain polls the HEY change ledger with a cursor and reads the ships feed by project and date window. Each ship and change carries its source, so a digest can cite the release or contract change rather than restating market moves. The Builder Radar and accelerating-builders reads add a ranked view of shipping momentum.

Page GET /api/changes with the after cursor from the previous run, then call GET /api/ships with project and since filters and list new releases with their evidence ids

Point-in-time project comparison

An analyst writing a project review compares two to four projects side by side and checks what changed for one of them across a date range. HEY returns the diff between two days at most 400 days apart and labels it as a difference, not an explanation, so the review states changes without inventing causes.

Call GET /api/compare with slugs for two projects, then call GET /api/projects/{slug}/diff with from 2026-08-01 and to 2026-11-01 for the first project

Claim verification with evidence receipts

A writer citing HEY data verifies each figure before publishing. Every published claim carries a typed evidence id, and the evidence read resolves it to a receipt with the original source, while the explain read states why HEY publishes a given fact for a project.

Call GET /api/evidence/{id} for an evidence id taken from a project timeline and report the source and observedAt date in the receipt

Key Endpoints

59 endpoints — the hey research lab api publishes evidence-backed research records for projects building on robinhood chain (chain id 4663): project dossiers, ships and releases, contracts, on-chain usage, market context, and a dated change ledger.

METHOD

PATH

DESCRIPTION

GET

/api/projects

Search and browse published projects

GET

/api/projects/{slug}

Get one project's dossier

GET

/api/projects/{slug}/timeline

Get a project's evidence timeline

GET

/api/projects/{slug}/diff

Compare a project between two dates

GET

/api/changes

Read the change ledger

GET

/api/token/{chainId}/{address}

Resolve a token contract to a project

GET

/api/ships

List what projects shipped

GET

/api/evidence/{id}

Resolve an evidence id to a receipt

GET

/api/projects

Search and browse published projects

GET

/api/projects/{slug}

Get one project's dossier

GET

/api/projects/{slug}/timeline

Get a project's evidence timeline

GET

/api/projects/{slug}/diff

Compare a project between two dates

GET

/api/changes

Read the change ledger

GET

/api/token/{chainId}/{address}

Resolve a token contract to a project

GET

/api/ships

List what projects shipped

GET

/api/evidence/{id}

Resolve an evidence id to a receipt

Why Jentic?

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

Setup

Wiring HEY by hand means deciding between anonymous reads and a key, choosing the bearer or x-api-key form, and handling 308 redirects for renamed slugs and 429 quota answers. Through Jentic you install once, import HEY Research Lab from the API Directory, store the key once, and your agent calls it.

Permission scoping

HEY puts the project slug in the URL path (/api/projects/{slug}/...), so a rule can pin your agent to one project's reads. You choose the operations it may call, so bulk reads like CSV exports or the A2A JSON-RPC interface are not included unless you add them.

Credential isolation

Your HEY 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 'research a Robinhood Chain project' or 'what changed for a project', and Jentic returns the matching HEY operation with its input schema, including slug and date parameters, so the agent calls the right endpoint.

FAQs

Specific to using HEY Research Lab public API through Jentic.

What authentication does the HEY Research Lab API use?

Per its OpenAPI spec, a key is optional on most reads: the spec declares a bearer token (Authorization: Bearer) and the same key in the x-api-key header. Two bulk reads, GET /api/snapshots and GET /api/token/{chainId}, require the key. Through Jentic the key is stored by your own instance and attached at call time, so the agent never sees it.

What are the rate limits for the HEY Research Lab API?

The spec states that calls without a key get 120 requests a minute per client address, with anonymous answers cached for 60 seconds. A free key keeps 120 a minute in its own bucket, and every key carries a monthly allowance that answers 429 quota once spent. See https://heyresearch.xyz/developers for current tiers.

Can I find out what changed for a project with the HEY Research Lab API?

Yes. GET /api/projects/{slug}/diff compares a project between two dates at most 400 days apart, and GET /api/changes returns the change ledger, filterable by project, contract, type, and date and paged with the after cursor. HEY states a difference, never a cause.

Is there a HEY Research Lab MCP server?

You don't need an MCP server to give your agent the HEY Research Lab API. Jentic connects it directly from the API Directory: import it, store your key once if you use one, and your agent calls the project and change-ledger operations it needs without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the HEY Research Lab API?

Yes. For example, write a rule that allows only the GET operations under /api/projects/{slug} for one project slug, plus the evidence read, so the agent can research that project and resolve its receipts but cannot run bulk exports or the A2A interface. Every call it makes is logged.

How do I look up a token contract through Jentic?

Search Jentic for 'resolve a token contract to a project', load the GET /api/token/{chainId}/{address} operation, and execute it with chainId 4663 and the 0x contract address. The response names the published project, which you can then read with GET /api/projects/{slug}. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Heyresearch Xyz HEY Research Lab public API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer, apiKey (optional)59 EndpointsREST

For Agents

Research Robinhood Chain projects with sourced evidence: read a project's dossier, ships, contracts, timeline, and change history, resolve a token contract to its project, and fetch evidence receipts for every claim.

Use for: Find all Robinhood Chain projects tagged with a given narrative, Get the dossier and contracts for one Robinhood Chain project, Check whether a token contract belongs to a published project, List all ships a project recorded since last month

Not supported: Does not provide wallet analytics, price predictions, investment advice, or trade execution. Use for evidence-backed research on Robinhood Chain projects only.

The HEY Research Lab API publishes evidence-backed research records for projects building on Robinhood Chain (chain id 4663): project dossiers, ships and releases, contracts, on-chain usage, market context, and a dated change ledger. Every claim it returns is tagged FACT, DERIVED, or UNKNOWN and carries a typed evidence id that resolves to a receipt with its source. Builder views such as the Builder Radar, accelerating builders, comebacks, and weekly and monthly reports sit beside per-project timelines, diffs between two dates, and relationship maps. Token contracts resolve to published projects by chain id and address rather than by symbol.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

21%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

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

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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.

AI-Readiness & Agent Experience

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

Grade: CSignals: 4

76%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

49%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

54%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HEY Research Lab public API to your agent

Capabilities

Start building with HEY Research Lab public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Heyresearch Xyz HEY Research Lab public API

Jentic AI Readiness Score

HEY Research Lab public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness