Structured Intelligence.
Directly Delivered.
The HEVEA Genius API gives advanced users and teams direct access to signal data, conviction scores, and verification metadata — in a structured, integration-ready format. Built for automation, analysis, and internal product workflows.
Beyond the Dashboard
For some users, visibility isn't enough. They need to move data.
The HEVEA Genius dashboard gives members structured signal access inside the platform. The API takes that a step further — delivering the same intelligence directly into your systems, tools, and workflows. It exists because advanced users build things with data, and the best data is only useful when it flows where you need it.
Direct delivery
No manual checks, no dashboard dependency. Signals arrive the moment they are published.
System integration
Plug structured intelligence into internal tools, analytics layers, or automation pipelines.
Workflow ownership
Build the workflow you need. The API provides the data — you control what happens next.
Built for Teams and Advanced Users
API access fits a specific type of user — one who builds with data rather than just consuming it.
Product & Platform Teams
Building internal signal dashboards, market intelligence layers, or research tooling that requires live data delivery.
Automation & Workflow Builders
Running automated execution support, alert pipelines, or signal-triggered workflow logic that operates without manual intervention.
Analytics & Research Teams
Feeding structured signal history into back-testing frameworks, quantitative models, or research analysis pipelines.
Reporting & Audit Layers
Constructing compliance-adjacent reporting, audit trails, or structured outcome records that benefit from verified, timestamped data.
Platform Integrators
Embedding HEVEA Genius intelligence into broader product stacks — portfolio tools, aggregators, or multi-source intelligence platforms.
Advanced Individual Users
Power users running personal automation, algorithmic alerting, or data-driven analysis frameworks outside the standard dashboard.
Six Core Capabilities
Each capability is designed to move structured intelligence directly into your environment.
Real-Time Signal Feed
Receive new signals the moment they are published. REST polling or webhook push — whichever fits your architecture.
Conviction Score Layer (HGX)
Every signal includes the HGX conviction breakdown — directional strength, confidence rating, and time horizon context — structured for programmatic use.
Structured Signal History
Access the full HEVEA Genius signal archive in structured format. Filter by asset, date range, status, or conviction level for back-testing and research.
Verification Metadata
Every payload includes the signal's verification hash and publication timestamp — immutable proof of when and what was published.
Webhook Delivery
Push delivery to your endpoint the moment a signal is published. Configurable retry logic, signed payloads, and delivery confirmation.
Integration Flexibility
Standard REST architecture with versioned endpoints, predictable schema, and documented field structures. Designed to integrate cleanly with existing systems.
What Serious Users Build
API access unlocks a different class of workflow — here are the most common.
Internal Signal Dashboards
Teams who want structured signal intelligence inside their own tooling — Notion, Airtable, internal apps, or custom dashboards.
Automated Alerting Systems
Webhook-triggered alerts to Slack, Telegram, email, or custom notification layers — without any manual monitoring.
Back-Testing & Research Pipelines
Feeding structured historical signal data into quantitative models, scenario analysis frameworks, or strategy evaluation tools.
Portfolio Monitoring Layers
Layering signal context over position tracking — combining BTC/Gold signals with portfolio data for cohesive reporting.
Compliance & Audit Records
Structured, verified signal records with immutable timestamps — useful for firms that need documented, auditable market intelligence inputs.
Multi-Source Intelligence Aggregators
Teams building broader intelligence platforms that draw from multiple data sources — with HEVEA Genius as a structured signal layer.
API Access vs. Platform Plans
API Access is a separate advanced tier, built on top of the platform — not a replacement for it.
| Feature | NEXUS | INSTITUTIONAL | API ACCESS |
|---|---|---|---|
| Member Dashboard | ● | ● | ● |
| Signal Alerts (Telegram + Email) | ● | ● | ● |
| Gold Signals | ● | ● | ● |
| Dashboard HGX Score | ● | ● | ● |
| REST API | ● | ● | ● |
| Webhook Delivery | ● | ● | ● |
| Structured JSON Payloads | ● | ● | ● |
| Conviction Score (API) | ● | ● | ● |
| Verified Payload Metadata | ● | ● | ● |
| Historical Archive (API) | ● | ● | ● |
| Rate Limits | N/A | N/A | Generous / documented |
| Support Channel | Community | Priority | Dedicated |
| Price | $49/mo | $99/mo | $990/mo |
The Technical Layer
Designed for clean integration from day one.
Delivery
Signals are available via REST API (polling) and webhook (push). REST endpoints are versioned and return structured JSON. Webhooks are delivered to your specified endpoint with signed headers for payload verification.
Authentication
API access uses bearer token authentication. Credentials are issued on approval, tied to your account, and rotatable from the API management panel. All requests must be made over HTTPS.
Rate Limits & Availability
Rate limits are generous and documented — designed for real-world integration, not developer sandboxes. Current limits, endpoint availability, and schema versioning are detailed in the API documentation provided on approval.
Schema & Versioning
All endpoints follow a stable, versioned schema. Field structures are documented, and breaking changes are versioned. You receive advance notice of any schema evolution before it goes live.
What a Signal Looks Like as Data
Every API response includes a consistent, structured payload with signal data, conviction context, and verification metadata.
Signal Core
assetTarget asset (e.g. BTC, XAU)directionSignal direction (LONG / SHORT / NEUTRAL)entry_zoneStructured entry contexttarget_zoneStructured target contextstop_contextRisk boundary referencestatusOPEN / CLOSED / EXPIREDvalidity_windowSignal validity periodHGX Conviction Layer
hgx_scoreNumerical conviction score (0–100)hgx_directionDirectional conviction labelconfidence_ratingConfidence tiertime_horizonShort / Medium / Longmacro_alignmentMacro context alignment flagonchain_alignmentOn-chain signal alignment flagVerification Metadata
signal_idUnique immutable signal identifierpublished_atISO 8601 publication timestampverification_hashSHA-256 hash of signal content at publicationrecord_immutableBoolean — true once publishedverification_urlDirect link to public verification record{
"signal_id": "hg_btc_20260421_001",
"asset": "BTC",
"direction": "LONG",
"entry_zone": { "low": 82400, "high": 84200 },
"target_zone": { "primary": 96000, "extended": 108000 },
"stop_context": "Below 79800",
"status": "OPEN",
"validity_window": "14d",
"hgx_score": 78,
"hgx_direction": "bullish",
"confidence_rating": "high",
"time_horizon": "medium",
"macro_alignment": true,
"onchain_alignment": true,
"published_at": "2026-04-21T09:00:00Z",
"verification_hash": "a3f9d2...c71e",
"record_immutable": true,
"verification_url": "https://heveagenius.io/verify/hg_btc_20260421_001"
}Schema is versioned. Full field documentation is provided on API approval.
The Record Is Immutable
Every signal published through HEVEA Genius is timestamped at the moment of publication. That record cannot be changed after the fact.
The verification metadata in every API payload isn't decorative — it's structural. The verification_hash is computed from the signal content at publication time. The published_at timestamp is set at the moment the signal enters the record. Once published, neither can be altered. This is what makes the HEVEA Genius signal record independently verifiable — not just claimed.
Timestamp at publication
The published_at field captures the exact moment a signal is published — not edited, not backdated.
Content hash
The verification_hash is a SHA-256 digest of the signal content at publication. Any change to the signal would produce a different hash.
Public verification
Every signal's verification record is accessible at its verification_url. External validation is possible without trusting the platform.
One Advanced Tier
API Access is a separate layer — not a feature inside the standard plans.
INSTITUTIONAL
- Full platform access
- All BTC & Gold signals
- Member dashboard
- Priority support
- HGX conviction scores
API ACCESS
- REST API access
- Webhook delivery
- Structured JSON payloads
- Verified signal payloads
- Historical archive access
- Conviction score API
- Dedicated integration support
- API credential management
API Access is billed monthly. Application required — access is reviewed individually. Annual pricing available on request.
Apply for Access
API access is not automated. Every application is reviewed individually.
We review every application to understand the use case, the integration environment, and whether the data layer is a good fit. This ensures we can offer meaningful support and the right level of access for your workflow.
Common Questions
Precise answers for technical audiences.
verification_hash (SHA-256 of signal content at publication) and a published_at timestamp. These are set at publication and cannot be altered. A verification_url in every payload links to the public record. This allows external validation of the signal record.Direct Access to Structured Intelligence
If you build with data, the HEVEA Genius API is the access layer you need.