Install Jentic One Beta

Connect the 0xArchive API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 0xArchive 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%2F0xarchive.io%2F0xarchive" | 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%2F0xarchive.io%2F0xarchive" | 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 0xArchive API.

Pull current and historical trades for a Hyperliquid or Lighter perpetual by symbol

Retrieve OHLCV candles and funding rate history for a market and interval

Read native and full-depth L2 and L4 order book snapshots and diffs for a symbol

Track open interest, liquidation events, and liquidation levels across Hyperliquid, HIP-3, and HIP-4 markets

GET STARTED

Start building with 0xArchive API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use 0xArchive API for, with concrete tasks.

★ AI market-research agent for perpetuals

An AI agent researching a token's microstructure needs grounded market data without wiring a bespoke client. Through Jentic the agent searches for 'get recent trades for a perpetual', loads the matching 0xArchive operation with its input schema, and reads trades and candles for the symbol with the API key injected at call time. The agent returns a summary of recent flow for a Hyperliquid or Lighter market without browsing the reference docs.

Fetch the latest trades via GET /v1/hyperliquid/trades/{symbol} and hourly candles via GET /v1/hyperliquid/candles/{symbol} for a symbol, then summarise recent price action

Backtesting data pipeline

Quantitative researchers backfilling a strategy pull historical candles, funding, and open interest for a basket of symbols. 0xArchive exposes cursor-paginated history for each series, so a pipeline can page from a start timestamp to an end timestamp per market. Funding rate history pairs with candle data to reconstruct carry-adjusted returns for Hyperliquid and Lighter perpetuals.

Page GET /v1/hyperliquid/funding/{symbol} and GET /v1/hyperliquid/candles/{symbol} from a start to an end timestamp and store the merged series

Liquidation monitoring

A risk dashboard tracks forced liquidations and clustering of stop levels for the symbols it watches. 0xArchive returns individual liquidation events, aggregated liquidation volume, and bucketed liquidation levels for a symbol. Combined with trigger-level history, this lets a monitor flag when a market is approaching a dense band of resting stops.

Poll GET /v1/hyperliquid/liquidations/{symbol} for a symbol and alert when liquidation volume over the last hour exceeds a threshold

Order book depth analysis

A microstructure study needs reconstructed depth rather than top-of-book quotes. 0xArchive serves native 20-level and full-depth L2 order book snapshots, L2 diffs, and L4 order book data for a symbol, plus point-in-time history by timestamp. An agent can rebuild the book at a chosen moment to measure spread, imbalance, and depth at price.

Fetch GET /v1/hyperliquid/orderbook/{symbol}/l2 at a given timestamp and compute bid-ask depth imbalance for the top levels

Key Endpoints

231 endpoints — the 0xarchive api serves current and historical market data for the hyperliquid and lighter decentralised perpetuals venues, including spot pairs, hip-3 builder perpetuals, and hip-4 outcome markets.

METHOD

PATH

DESCRIPTION

GET

/v1/hyperliquid/trades/{symbol}

Get Hyperliquid trades for a symbol

GET

/v1/hyperliquid/candles/{symbol}

Get Hyperliquid OHLCV candles

GET

/v1/hyperliquid/orderbook/{symbol}/l2

Get full-depth L2 order book

GET

/v1/hyperliquid/funding/{symbol}

Get funding rate history

GET

/v1/lighter/trades/{symbol}

Get Lighter trades for a symbol

GET

/v1/hyperliquid/hip4/outcomes

List HIP-4 outcome markets

POST

/v1/webhooks/subscriptions

Create a webhook subscription

GET

/v1/data-quality/coverage

Get coverage summary

GET

/v1/hyperliquid/trades/{symbol}

Get Hyperliquid trades for a symbol

GET

/v1/hyperliquid/candles/{symbol}

Get Hyperliquid OHLCV candles

GET

/v1/hyperliquid/orderbook/{symbol}/l2

Get full-depth L2 order book

GET

/v1/hyperliquid/funding/{symbol}

Get funding rate history

GET

/v1/lighter/trades/{symbol}

Get Lighter trades for a symbol

GET

/v1/hyperliquid/hip4/outcomes

List HIP-4 outcome markets

POST

/v1/webhooks/subscriptions

Create a webhook subscription

GET

/v1/data-quality/coverage

Get coverage summary

Why Jentic?

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

Setup

Wiring 0xArchive by hand means registering an API key, sending it in the X-API-Key header, and handling cursor pagination across hundreds of symbol routes split over Hyperliquid, HIP-3, HIP-4, and Lighter. Through Jentic you install once, import 0xArchive from the API Directory, store the key once, and your agent calls it.

Permission scoping

0xArchive is a read-only data API whose markets sit under symbol paths such as /v1/hyperliquid/trades/{symbol}, so a rule can pin your agent to the market-data operations it needs. You choose which operations it may call, so webhook-management routes like deleting an endpoint or rotating a secret are not included unless you add them.

Credential isolation

Your 0xArchive API key is stored once, encrypted, by your own Jentic One instance and attached to each request at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get recent trades for a perpetual' or 'read the funding rate', and Jentic returns the matching 0xArchive operation with its input schema, including the symbol and pagination parameters, so the agent calls the right endpoint directly.

FAQs

Specific to using 0xArchive API through Jentic.

What authentication does the 0xArchive API use?

0xArchive authenticates with an API key sent in the X-API-Key request header, as declared in its OpenAPI spec. A handful of endpoints such as GET /health and GET /v1/symbols are public and need no key, while the market-data routes expect the key. Through Jentic the key is held by your own instance and attached to each call, so the agent never sees it.

Can I pull historical candles and funding rates with the 0xArchive API?

Yes. GET /v1/hyperliquid/candles/{symbol} returns OHLCV candles for a symbol and interval, and GET /v1/hyperliquid/funding/{symbol} returns funding rate history. Both are cursor-paginated between a start and end timestamp, so an agent can page back across the available history for Hyperliquid, HIP-3, HIP-4, and Lighter markets.

What are the rate limits for the 0xArchive API?

The OpenAPI spec does not declare numeric rate limits, and limits vary by access tier and route. Check the 0xArchive documentation at https://docs.0xarchive.io/ for the current per-plan limits before scripting bulk history extraction.

Is there a 0xArchive MCP server?

You do not need an MCP server to give your agent 0xArchive. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the market-data operations it needs on demand without loading another server's tool definitions into its context.

How do I read a symbol's order book through Jentic?

Search Jentic for 'get the full-depth order book for a symbol', load the GET /v1/hyperliquid/orderbook/{symbol}/l2 operation, and execute it with the symbol and an optional timestamp. The response carries the depth levels so the agent can measure spread and imbalance. 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 0xArchive API?

Yes. Write a rule that allows only the read operations your task needs, such as fetching trades and candles for a symbol, and the agent can read that market data and nothing else. Every operation sits behind a path your rule can pin, and each call the agent makes is logged for review.

0xArchive API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingapiKey231 EndpointsREST

For Agents

Read Hyperliquid and Lighter perpetuals and spot market data for AI agents: trades, OHLCV candles, funding rates, open interest, liquidations, and full-depth order books by symbol.

Use for: Get the most recent trades for a Hyperliquid perpetual, Retrieve OHLCV candles for a symbol on Lighter, Check the current funding rate for a Hyperliquid market, List HIP-4 outcome markets that are still open

Not supported: Does not place orders, hold funds, or execute trades on any venue. Use for reading Hyperliquid and Lighter market data only.

The 0xArchive API serves current and historical market data for the Hyperliquid and Lighter decentralised perpetuals venues, including spot pairs, HIP-3 builder perpetuals, and HIP-4 outcome markets. It returns trades, OHLCV candles, funding rates, open interest, and both native and full-depth L2 and L4 order book snapshots and diffs for a symbol. Liquidation events, liquidation levels, cumulative volume delta, and wallet classification are available across each venue. Webhook subscriptions and watched-address alerts let a client follow new deliveries without polling.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

93%

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).

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: A-Signals: 4

35%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

78%

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.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

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: A-Signals: 1

80%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the 0xArchive API to your agent

Capabilities

Start building with 0xArchive API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

0xArchive API

Jentic AI Readiness Score

0xArchive 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