ForceDream
Infrastructure · tested 2026-08-07 · re-test due 2026-11-07 · by the Hlido desk, not the vendor
In short: Extraordinary claims — 99.97% uptime SLA, 4.2M+ sealed events, 78% margin "enforced in code", 90 settlement corridors — with a verification link as the only offered proof and no operating history behind any of it.
3 PASS · 2 FAIL of 5 public-surface claims
Quick answer
ForceDream scores 50/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-07). FADING (50) because the surface pairs extraordinary, highly specific claims (99.97% uptime SLA, 4.2M+ sealed events, −43.2% inference cost, 90 settlement corridors across 166 currencies) with no team, no company details, Pricing was not findable on the public surface when tested.
ForceDream presents itself as a "sovereign intelligence operating system for the global agentic economy": multi-provider inference arbitrage, an immutable SHA-256 WORM audit chain sealed from genesis, 78% of margin to developers enforced cryptographically before the response returns, autonomous agent payments, and 90 settlement corridors across 166 currencies with African mobile-money rails in development. The density and specificity of the numbers is the problem rather than the reassurance: **330+ live routes, 100% rule-enforced, 78% developer earnings, 99.97% uptime SLA, 4.2M+ WORM events, −43.2% inference cost, 117ms latency**, plus a live-updating genesis hash. Any one of these would be a significant claim; together, from an entity with no named team, no company details, no customers, no case studies and no operating history on the surface we captured, they form a pattern that warrants caution rather than confidence. A 99.97% uptime SLA is a contractual commitment, and no terms are shown. "78% of margin enforced in code" is checkable in principle — the page offers a genesis endpoint and a "verify live" link — and we credit that the mechanism is at least pointed at; but a self-published hash verifies internal consistency, not that the accounting behind it is honest or that the money moves as described. Cross-border settlement across 166 currencies is a regulated activity in most jurisdictions, and no licensing or regulatory posture is stated anywhere. We are not asserting anything here is false — we could not verify any of it, which is precisely the finding. The score records unverifiable extraordinary claims, and would move substantially on audited figures or named customers.
Why FADING
FADING (50) because the surface pairs extraordinary, highly specific claims (99.97% uptime SLA, 4.2M+ sealed events, −43.2% inference cost, 90 settlement corridors across 166 currencies) with no team, no company details, no customers, no operating history, and no regulatory posture for what is described as cross-border settlement. Self-published cryptographic verification demonstrates internal consistency, not honest accounting. This scores absence of verifiable substantiation behind unusually strong claims — not a finding that any specific claim is false.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — 'Sovereign AI Infrastructure for the Global Agentic Economy'
- PASS Cta present (required) — 'Start Earning 78%' / 'API Docs'
- FAIL Pricing or access — Revenue-share stated; no pricing terms or contract shown
- FAIL Evidence or demo — Live counters and a genesis hash; no audit, customers or team
What we saw
4 screenshots captured by the Hlido engine during the reviewed run (run-b34b66971a0553a3-www-forcedream-com). Our own captures — not vendor marketing material.
What it does well
- Points at a verification mechanism (public genesis endpoint, live hash) rather than asking for pure trust
- Immutable WORM audit chain sealed before the billable response returns is a sound architectural idea
- Developer revenue share stated as a specific, checkable number rather than a vague promise
- Multi-provider inference arbitrage is a real and useful optimisation
- Explicit that mobile-money rails are 'in development' rather than claiming them as live
What it fails at
- No named team, company details, jurisdiction, or operating history anywhere on the surface
- A 99.97% uptime SLA is asserted with no terms, no status page history, and no contract shown
- Headline figures (4.2M+ WORM events, −43.2% inference cost, 117ms latency, 330+ routes) are unaudited and unverifiable
- Cross-border settlement across 166 currencies is regulated activity; no licensing or regulatory posture stated
- No customers, case studies, or third-party validation of any kind
- Cryptographic sealing proves internal consistency, not that the underlying accounting is honest
- Very high claim density relative to available evidence
Red flags
- [object Object]
- [object Object]
- [object Object]
Best for
- Nobody we can identify from the public surface without substantially more disclosure
Not recommended for
- Anyone routing production inference or money through it on the strength of this page
- Buyers with vendor due-diligence requirements — the basic disclosures are absent
- Developers relying on the 78% margin commitment without contractual terms
- Any regulated context requiring a known, licensed counterparty
Pricing & access
- Pricing findable on the public surfaceFAIL Revenue-share stated; no pricing terms or contract shown (tested 2026-08-06)
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-06.
Related agents
Agent relevance
API MCP
Agentic-Commerce Readiness 48/100 · SURFACE-ONLY
Independent readiness for agent delegation & transaction. How it’s scored · check live
Advertises nine MCP tools plus an API with 330+ routes and autonomous agent payments, so the intended consumer is an agent. None of it was verifiable from the public surface.
Agent-friendly score: 5/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Full-stack intelligence OS: inference arbitrage, WORM audit, agent payments — source (2026-08-07) verified
- 78% of margin to developers, stated as enforced in code before the response returns — source (2026-08-07)
- 99.97% uptime SLA — source (2026-08-07)
- 4.2M+ WORM events, 330+ live routes, −43.2% inference cost, 117ms latency — source (2026-08-07)
- 90 settlement corridors, 166 currencies, settling in GBP — source (2026-08-07)
- Named team, company details, customers or case studies — source (2026-08-07)



