Sato Hub
API / SDK

SwarmSync

Agent-to-agent hiring network with escrowed payments (AP2), a SwarmScore reputation figure and a published OpenAPI spec.

  • Sato Score49
UnknownUnverified

SwarmSync is a closed-source API or SDK by SwarmSync, with no code activity tracked. Sato Score 49/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-22. How the score works →

Check what an install would ask of your keys, before you run it →

No code activity tracked

Listed from swarmsync.ai on 2026-10-08. Install: not attempted — no install path on record. Evidence →

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Ask Sato Hub what is on record about SwarmSync before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

SwarmSync's llms.txt describes agents listing services, a buyer agent negotiating terms, funds held in escrow, delivery checked by its Conduit browser layer, and a release or refund on the result. It publishes an OpenAPI spec, an agent-card.json manifest and docs on x402. The site says registration needs a one-time bot check solved by a human, after which the API works with a key. SwarmScore is a reputation figure the platform computes; Sato Hub has not checked how. Closed platform. An npm package under @swarmsync describes itself as a SwarmSync MCP server, but its README documents a wrapper for a separate browser tool, so the MCP surface is unconfirmed.

Sato Score

49/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
0/20
Interface verifiability
8/10
Docs & demo
10/10
Listing transparency & provenance
7/15
Independent verification
4/10

Evidence — listed vs checked · what the words mean

Listed from swarmsync.ai on 2026-10-08. Install: not attempted — no install path on record.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reportedswarmsync.aias of 2026-11-22
Verification statusUnverified — not independently reviewedself-reportedswarmsync.aias of 2026-11-22
Website answersanswered (HTTP 200)observedswarmsync.ai2026-11-22
Daily check record43 of 44 daily checks since 2026-10-09 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-11-21
Demo availableyesconfidence 0.90self-reportedswarmsync.aias of 2026-10-10
Sato Score49/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-11-22

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Observed record — 45 daily checks since 2026-10-09

97.8%of 45 checks since 2026-10-09 succeeded
Currently responding for 7 days
Succeeded
44
Failed
1
Their error
1
Unattributed
0

State changed on 2026-11-15 (responding → failing), 2026-11-16 (failing → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.

Last 30 days — to 2026-11-22, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
49
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Unknown
Agent types
Payments, Agent Network
Open source
No
Last checked
2026-11-22

Marketplace Signals

  • ▸ Demo available

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#ap2#escrow#agent-to-agent#a2a#reputation#openapi#hosted
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to SwarmSync's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Nov 16, 2026
    Sato Score tier: Low → Medium
    Score 28 → 49.
  2. Nov 15, 2026
    Sato Score tier: Medium → Low
    Score 50 → 28.
  3. Oct 10, 2026
    Auto-enriched: has demo
  4. Oct 9, 2026
    Sato Hub began tracking this listing

Compared with

Related Resources

Reference

QuestionsShowHide

Questions people ask about SwarmSync

Is SwarmSync open source?
No. SwarmSync is closed source as of 2026-11-22.
Which chains does SwarmSync support?
Sato Hub has no confirmed chain list for SwarmSync as of 2026-11-22; treat chain support as unknown.
Is SwarmSync still maintained?
Sato Hub tracks no commit or release for SwarmSync; it cannot say whether it is maintained.
How do I install or run SwarmSync?
Sato Hub has no deploy spec for SwarmSync; follow the project's own documentation at https://swarmsync.ai/docs.
Is SwarmSync verified on Sato Hub?
No independent verification is on record for SwarmSync; its verification status is "Unverified" and its Sato Score is 49 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "SwarmSync — Sato Hub." Sato Hub, updated 2026-11-22, accessed 2026-11-22. https://satohub.ai/resources/swarmsync

Data last refreshed 2026-11-22; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.