Skip to main content
Healthy Uptime healthy Near real-time snapshot Top gainer: KARRAT Top loser: KEYCAT Refreshed at: 2026-05-11 20:14:30 UTC Open status

How it works

Review live status, snapshot deltas, and latest release highlights before switching into authenticated operations views.

Risk notice

Execution remains market-sensitive. Public pages never imply performance guarantees and always defer to risk disclosure policy.

Live market overview

Crypto market context in one place.

OHLC Bot keeps the public homepage focused on a live market snapshot, monitored movers, and a clear invite-only path for approved users without exposing internal operations tooling.

OHLC Bot interface symbol
Log In Dashboard access remains invite-only.
Tracked assets 262
Access model Invite-only access
Visible price cards 4 / 4
Top gainer (24h) KARRAT
Top loser (24h) KEYCAT
24h sentiment 34.7%
Volatility pulse 3.07%
Live market data is currently available.
Refreshed at: 2026-05-11 20:14:30 UTC

Top Gainers

Top 24h movers
KARRAT
KARRAT
+42.00%
IOTX
IoTeX
+23.18%
VVV
Venice Token
+20.55%

Top Losers

Top 24h movers
KEYCAT
Keyboard Cat
-13.58%
SPK
Spark
-12.66%
LCX
LCX
-9.72%

How OHLC Bot works

Signal -> execution -> reporting
Workflow section visual marker
1

Signal context

Market context and signal state are ingested with explicit versioned payload contracts.

2

Execution controls

Runtime guards evaluate readiness, limits, and lifecycle state before any order action is accepted.

3

Reporting trace

Dispatch outcomes, rejects, and release-note changes stay traceable for operational review.

Security and transparency

Public non-sensitive operational posture
Ingress controls

Webhook ingress is protected by source controls, signature policy modes, and replay-guard checks before payload processing.

Operational audit trail

Accepted and rejected ingestion paths are persisted with explicit reasons so rollout incidents remain reviewable.

Diagnostics discipline

Runtime diagnostics and smoke checks are versioned and verified as part of deployment workflow checkpoints.

Release Notes

08. 05. 2026: Release 2.0.17 (build 3350)

Public visitors should eventually see what changed recently without being dropped into internal or admin-only areas.

Release Notes

Feature

  • Webhook v2 now propagates one explicit dispatch correlation ID end-to-end (dispatch payload, runtime notes, persisted order-correlation, and cancellation audit context), so each live dispatch attempt is traceable as one lifecycle chain.

UX

  • A follow-up dashboard filter cleanup retires the redundant lower-card selector shell so market dropdown interaction now stays fully in the sticky summary panel.
  • Authenticated app shell now shows `OHLC Bot v2` in the top navbar brand link, and authenticated page titles use the same `OHLC Bot v2` prefix.

Public status snapshot

Operational status preview from non-sensitive telemetry.
Current status

Healthy

Release changelog digest

Subscribe via email or webhook with explicit opt-in lifecycle.
API endpoint

https://ohlcbot.com/homepage/changelog-subscription

Lifecycle

Capture -> pending -> confirm -> unsubscribe (signed links).

Pricing

Single-plan scaffold with legal anchor

OHLC Bot Access

  • Invite-only access and controlled onboarding
  • Market snapshot, workflow transparency, and release visibility
  • Operational controls remain role-guarded after login

Legal and fees

  • Final fee and plan terms are linked from legal anchors below.
  • No implied profit guarantees or performance promises.
  • Open legal anchors

Trust and social proof

Config-driven counters, references, and testimonials

Usage counters

  • 300+ - Tracked assets
  • Continuous - Webhook contract checks
  • Daily - Release cadence
Coinbase TradingView CCXT

Testimonials

  • "Operators can review signal-to-dispatch context in one workflow without jumping across multiple tools." Internal operations feedback
  • "Release notes and diagnostics make incident handoff cleaner and faster during rollout windows." Rollout review notes

FAQ

Category-grouped answers with deep-link anchors
Access
  • Who can use OHLC Bot today?
    Current access is invite-only while onboarding and legal surfaces are being finalized.
  • Is registration open to the public?
    Public self-registration remains disabled until the pre-login rollout gates are approved.
Security
  • How is webhook ingestion protected?
    Ingress protections include source controls, signature policy modes, replay guard checks, and reject-audit logging.
  • Where can I see product changes?
    Recent public-facing updates are published in Release Notes with semantic stream labeling.

Manual trading vs OHLC Bot workflow

Concise operational comparison for pre-login visitors
Dimension Manual trading OHLC Bot workflow
Signal context Operator must manually collect context from multiple sources. Signal, runtime intent, and release context are centralized in one workspace.
Execution discipline Order checks and retries depend on manual consistency during incidents. Guarded execution paths apply lifecycle and policy checks before dispatch.
Auditability Post-incident evidence often requires manual reconstruction. Reject reasons, diagnostics, and release updates remain traceable for handoff.
Operational overhead Higher repetitive overhead for monitoring and consistency checks. Structured workflows reduce repeated manual steps for approved operators.

Guest dashboard preview

Sanitized teaser cards for authenticated surfaces
Signal overview
Order lifecycle panel
Diagnostics snapshot

Ready to continue?

Pick the next step based on your access path.
Start now See live diagnostics preview