What did Hlido score NeuroLink?

NeuroLink scored 60/100 (FADING) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

NeuroLink

Name: NeuroLink review
Item: NeuroLink
Rating: 60
Author: Hlido Editor

Infrastructure · tested 2026-08-07 · re-test due 2026-11-07 · by the Hlido desk, not the vendor

In short: A broad multi-provider AI streaming layer from an established payments company — undercut by a homepage whose own headline metrics all read zero.

3 PASS · 2 FAIL of 5 public-surface claims

Visit NeuroLink → scorecard.json

Quick answer

NeuroLink scores 60/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-07). FADING (60) despite genuine breadth and real institutional backing (Juspay, published on npm), because the public surface actively works against it: all four headline metrics render as '0+', which is either placeholder m Pricing was not findable on the public surface when tested.

Hlido Editor · 2026-08-07

NeuroLink positions itself as the signal layer for AI applications, connecting streams of tokens, data, tools and context through pluggable connectors, and the breadth is real on paper: 16+ token providers (Anthropic, OpenAI, Gemini, Bedrock, Mistral, Vertex, Azure, Ollama, LiteLLM, HuggingFace, SageMaker, OpenRouter, DeepSeek, NVIDIA NIM, LM Studio, llama.cpp), tool integrations spanning 58+ MCP servers, memory primitives (conversation, semantic recall, working memory, Redis, vector index, compaction), 50+ knowledge formats, voice in and out across nine engines, and reasoning constructs including workflows, multi-agent, HITL, checkpointing and evals. It is published on npm as `@juspay/neurolink`, and Juspay is a substantial established payments company — meaningful institutional backing that most projects in this cohort lack. But the homepage undermines its own case: the four headline statistics render as **"0+ STREAM SOURCES, 0+ ACTIVE NEURONS, 0+ SYNAPSE TOOLS, 0+ KNOWLEDGE FORMATS"**. Either these are unwired placeholders shipped to production, or a live counter that is genuinely reporting zero usage. Both readings are bad, and neither is something a serious infrastructure page should show a prospective adopter. Combined with heavy metaphor (neurons, synapses, receptors, organs) standing in for concrete architectural explanation, and no named production deployments, case studies or benchmarks, the surface asks for a lot of trust while showing little. The corporate backing is the main reason this is not lower. Reviewed from the public surface.

Why FADING

FADING (60) despite genuine breadth and real institutional backing (Juspay, published on npm), because the public surface actively works against it: all four headline metrics render as '0+', which is either placeholder markup shipped to production or a live counter reporting no usage. Heavy biological metaphor substitutes for architectural explanation, and there are no named deployments, case studies or benchmarks anywhere.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — 'The Nervous System for AI Streams.'
PASS Cta present (required) — 'Get Started' / npm install @juspay/neurolink
FAIL Pricing or access — No pricing on the captured surface
FAIL Evidence or demo — Headline metrics render as 0+; no case studies or benchmarks

What we saw

1 screenshot captured by the Hlido engine during the reviewed run (run-2f7c5e196c919d99-neurolink-ink). Our own captures — not vendor marketing material.

NeuroLink — run screenshot 1 (home.png) — home.png

What it does well

Genuine provider breadth — 16+ model providers including local runtimes (Ollama, LM Studio, llama.cpp)
Spans tokens, tools, memory, knowledge, voice and reasoning in one layer rather than one slice
Backed by Juspay, an established payments company — real institutional weight for this cohort
Published and installable on npm as @juspay/neurolink
Explicit support for HITL, checkpointing and evals — production concerns, not just demo features
58+ MCP servers and 50+ knowledge formats claimed

What it fails at

All four homepage headline metrics render as '0+' — placeholder markup in production, or genuinely zero usage
Dense biological metaphor (neurons, synapses, receptors, organs) replaces concrete architectural explanation
No named production deployments, case studies, or customer references
No benchmarks for latency, throughput or overhead in a layer whose value is streaming performance
Breadth across six domains invites shallow depth in each; nothing on the surface disambiguates
Not exercised by us — connector quality and stream reliability are untested

Red flags

[object Object]

Best for

Teams wanting one abstraction across many model providers including local runtimes
Applications needing token, tool, memory and voice streams in a single layer
Existing Juspay customers who can rely on the commercial relationship

Not recommended for

Buyers who need evidence of production use before adopting a core streaming dependency
Latency-sensitive systems, with no published performance figures
Teams needing depth in one domain rather than breadth across six

Pricing & access

Pricing findable on the public surfaceFAIL No pricing on the captured surface (tested 2026-08-05)

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

Related agents

Agent relevance

API CLI MCP SDK

Agentic-Commerce Readiness 64/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

An SDK and CLI plus MCP tool integration across 58+ servers; the layer is designed to be embedded in an agent application rather than used directly by a person.

Agent-friendly score: 7/10

Evidence

Signal layer connecting token, data, tool and context streams via pluggable connectors — source (2026-08-07) verified
16+ model providers including Anthropic, OpenAI, Gemini, Bedrock and local runtimes — source (2026-08-07) verified
Published on npm as @juspay/neurolink — source (2026-08-07) verified
Homepage headline metrics all display as '0+' — source (2026-08-07) verified
Named production deployments, case studies or benchmarks — source (2026-08-07)

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-07

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/juspay-neurolink.svg)](https://hlido.eu/check/?agent=juspay-neurolink)

HTML

<a href="https://hlido.eu/check/?agent=juspay-neurolink"><img src="https://hlido.eu/badge/juspay-neurolink.svg" alt="Hlido trust score"></a>