What did Hlido score Agoragentic Integrations?

Agoragentic Integrations scored 68/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.

Agoragentic Integrations

Name: Agoragentic Integrations review
Item: Agoragentic Integrations
Rating: 68
Author: Hlido Editor

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

In short: A 97-surface integration catalogue for a governed agent router, notable mostly for refusing to let its own status labels be misread as live availability.

4 PASS · 1 FAIL of 5 public-surface claims

Visit Agoragentic Integrations → scorecard.json

Quick answer

Agoragentic Integrations scores 68/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-05). FADING (68) — the surface is careful and well-organised, and the explicit warning that statuses describe artifacts rather than live paid-route availability is unusually honest. Pricing was not findable on the public surface when tested.

Hlido Editor · 2026-08-05

Agoragentic positions itself as a governed routing, commerce and receipt layer: keep your model loop and local tools in whatever framework you already use, send external work through `execute()`, and carry invocation, policy, cost and settlement evidence back as a receipt. This catalogue is the integration surface — 97 manifest-backed entries, 34 first-class site guides, 63 repo adapters and references, with a stated catalog source date of 2026-07-23 and newly indexed entries for Claude Code, Gemini CLI, Cursor and Cline. The distribution shape is sensible (npm, PyPI, an MCP relay, and a local harness for no-spend policy and readiness runs), and the three-step buyer flow — match, execute, prove — is coherent. The standout is a disclaimer most catalogues would omit: "Statuses describe the public integration artifact, not live paid-route availability", and experimental entries stay guides or references unless their repository evidence says otherwise. That is precise, self-limiting language, and it is the main reason to take the counts seriously. Against that: the counts are self-reported and we verified none of them; a catalogue of adapters is not evidence that routing, commerce or settlement work in production; there are no named customers or transaction volumes; and the governance and policy claims — the actual product — sit behind this surface where we could not see them. Dating the catalogue is good practice and also a liability, since a stale date is now visible to everyone.

Why FADING

FADING (68) — the surface is careful and well-organised, and the explicit warning that statuses describe artifacts rather than live paid-route availability is unusually honest. But this is a catalogue of integration artifacts, not evidence of a working routing, commerce and settlement layer: all counts are self-reported and unverified, there are no named customers or volumes, and the governed-router product itself sits behind the page we captured.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — 'Agent integrations for one governed Router'
PASS Cta present (required) — 'Browse catalog' / 'SDK quickstart'
FAIL Pricing or access — No pricing on the captured surface despite commerce being central
PASS Evidence or demo — Self-reported counts with a dated catalogue; no independent validation

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-4c4379b6389e9cef-agoragentic-com). Our own captures — not vendor marketing material.

Agoragentic Integrations — run screenshot 1 (home.png) — home.png

Agoragentic Integrations — run screenshot 2 (page_main-content.png) — page_main-content.png

Agoragentic Integrations — run screenshot 3 (page_catalog.png) — page_catalog.png

Agoragentic Integrations — run screenshot 4 (pageagno_.png) — pageagno_.png

What it does well

Explicitly warns that statuses describe the public integration artifact, not live paid-route availability
Experimental entries stay guides or references unless repository evidence supports more
Catalogue carries a visible source date (2026-07-23) so readers can judge freshness
Coherent three-step buyer flow — match (preview), execute (route), prove (receipt)
Sensible distribution: npm and PyPI SDKs, an MCP relay, and a local harness for no-spend policy and readiness runs
Does not require moving your model loop, memory runtime or local tools into a hosted control plane

What it fails at

All headline counts (97 surfaces, 34 guides, 63 adapters) are self-reported and unverified by Hlido
An integration catalogue is not evidence that routing, commerce or settlement work in production
No named customers, transaction volumes, or third-party validation
The governed router — the actual product — is not visible on this surface, so it could not be assessed
A dated catalogue becomes visibly stale if it is not maintained; nothing states the refresh cadence
No pricing on the captured surface despite commerce being central to the pitch

Best for

Teams already running an agent framework who want external work routed through one governed rail
Buyers who need invocation, policy, cost and settlement evidence carried back as receipts
Developers checking whether their specific runtime already has an adapter

Not recommended for

Anyone treating the catalogue's status labels as proof a paid route is live — the vendor says it is not
Procurement needing verified transaction volumes or reference customers
Teams wanting a complete agent platform rather than a routing and settlement layer

Pricing & access

Pricing findable on the public surfaceFAIL No pricing on the captured surface despite commerce being central (tested 2026-08-04)

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

Related agents

Agent relevance

API CLI MCP SDK

Agentic-Commerce Readiness 70/100 · INTEGRABLE

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

Node and Python SDKs plus an MCP relay (`npx agoragentic-mcp`) and a POST /api/execute rail; the whole design assumes an agent framework calls it rather than a human using a dashboard.

Agent-friendly score: 8/10

Evidence

97 manifest-backed surfaces, 34 first-class site guides, 63 repo adapters and references — source (2026-08-05)
Statuses describe the public integration artifact, not live paid-route availability — source (2026-08-05) verified
Catalog source date of 2026-07-23 published on the page — source (2026-08-05) verified
Distribution via npm (agoragentic), PyPI (agoragentic), MCP relay, and a local harness — source (2026-08-05) verified
Named customers, transaction volumes, or pricing — source (2026-08-05)

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

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/rhein1-agoragentic-integrations.svg)](https://hlido.eu/check/?agent=rhein1-agoragentic-integrations)

HTML

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