Research subscription
Pays for research access. It does not include API usage or trading fees.
MARKET STRUCTURE → AGENT SYSTEMS
Different markets. One structured view.
Connect U.S. equity context with Hyperliquid native and HIP-3 perpetuals. Inspect model evidence, build with structured results, and keep execution separate.
Local developer preview · Public research remains available
- 01
Market inputs
Identify venue, instrument and observation clock.
- 02
Model evidence
Return versioned context with quality and validity.
- 03
Agent interface
Read through API, Python SDK or MCP.
- 04
Separate execution
Require independent permissions and risk checks.
Compare the context, not just the price.
Market identity, observation time and reference type travel with every result. A shared ticker does not make two instruments equivalent.
Research reference
U.S. equities
Session-aware price and event context. Public research and the delayed tape are available today.
- Session and quote time
- Corporate actions and currency
- A reference asset, not a perpetual contract
Local developer preview
Hyperliquid native
Read native perpetual market context with explicit network and asset identity. Keep mark, reference and order-book observations distinct.
- Network, coin and asset identifier
- Funding and order-book context
- Perpetual exposure; no equity ownership
Explicit market mapping
Hyperliquid HIP-3
Deployer-defined markets need their own identifiers and reference checks. An equity-linked contract is not the underlying share.
- DEX and coin namespace
- Reference source, hours and freshness
- Validate comparability before calculating a spread
Illustrative workflow · No market observation
Evidence your system can inspect.
Versioned results keep freshness, quality and validation status explicit. Missing inputs remain missing; a descriptive model result is not an order instruction.
This outline illustrates research and human review steps. It is not live data, an executable strategy or validated performance.
{
"example": "Illustrative workflow only",
"question": "Which evidence supports this assessment?",
"review": "Identify missing information and human review needs.",
"execution": "Simulation and testnet are separate steps; no production availability is implied."
}From a market question to a typed result.
A local developer preview for Agent and application builders. Inspect capabilities and market identifiers before requesting context. Credentials and service access are provisioned separately; no public commercial endpoint is offered here.
HTTP API
Integration requirements and access are confirmed for the agreed workflow. No public endpoint or production capability is implied.
Confirm permitted inputs → inspect context → review the saved receipt.Python SDK
Integration requirements and access are confirmed for the agreed workflow. No public endpoint or production capability is implied.
SDK setup is supplied through authorized workspace access.MCP tools
Integration requirements and access are confirmed for the agreed workflow. No public endpoint or production capability is implied.
Discover enabled tools → request research → inspect limitations.This non-executable outline describes a research workflow. Available access and integration scope must be confirmed before implementation.
A clear boundary at every layer.
| Layer | Availability | What it means |
|---|---|---|
| Research & public tape | Available | Free briefings and a public tape delayed by ten minutes. Personal workspace access is a separate subscription. |
| Models & Agent access | Local preview | Descriptive, unvalidated results. Not a public commercial API or an execution signal. |
| Service usage credits | Access and usage depend on configuration | Planned prepaid service units, non-transferable and non-withdrawable. Not an investment or a claim on assets. |
| Execution connector | Gated testnet development | Separate from research and the Agent API. Requires explicit permissions, signing and risk checks; no public execution service is enabled by this page. |
Research access, service usage and execution stay separate.
API service usage
Planned usage-based service billing. No credit purchase or prepaid balance is available on this page.
Execution costs
Venue costs and any future connector charges are separate and require their own disclosed terms. No fee or rebate is promised here.
Build around the result.
Tell us your market coverage, latency needs and integration format. Pilot discussions do not promise commercial access or execution approval.