Sato Hub
Payment Rail

Skyfire

Identity and payment layer for agents: KYAPay tokens carry an agent's identity and a USDC-backed payment commitment, with a hosted MCP server.

  • Sato Score20
  • ChainsBase
UnknownUnverified

Skyfire is a closed-source payment rail by Skyfire on Base, with no code activity tracked. Sato Score 20/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 skyfire.xyz on 2026-10-08. Install: not attempted — no install path on record. Evidence →

Next step

Watch Skyfire

One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.

Check it from your agent

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

https://satohub.ai/api/mcp
Run Sato Hub Preflight on https://mcp.skyfire.xyz/mcp 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

Skyfire's docs describe KYAPay tokens (kya, pay and kya-pay): signed credentials a buyer agent presents to a seller, who charges the pay token after delivering. Each agent account has a wallet managed by Skyfire, funded by card, USDC on Base, or ACH or wire. A hosted MCP server at mcp.skyfire.xyz exposes find-sellers and token-creation tools and needs a Skyfire API key (it answered 401 without one on 2026-10-08). Closed source; no public repo for the platform was found. The balance sits in a Skyfire-managed wallet, so read its terms before funding one.

Sato Score

20/100· Low

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

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

Evidence — listed vs checked · what the words mean

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

ClaimValueEvidenceSourceChecked
Chains supportedBaseself-reporteddocs.skyfire.xyzas of 2026-11-22
Verification statusUnverified — not independently reviewedself-reportedskyfire.xyzas of 2026-11-22
MCP endpoint answersanswered, but declined an anonymous probeobservedmcp.skyfire.xyz2026-11-22
Daily check record0 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
Sato Score20/100 (Low)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

0%of 45 checks since 2026-10-09 succeeded
Currently unreachable from our probe for 45 days
Succeeded
0
Failed
45
Their error
0
Unattributed
45

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
fewer than 2 points—
7-day rolling; unattributable days are gaps · 0/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
20
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
Base
Agent types
Payments, Identity
Open source
No
Last checked
2026-11-22

Marketplace Signals

No marketplace signals recorded for this resource yet.

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

#kyapay#kya#agent-payments#usdc#agent-wallet#identity#mcp#hosted
See something inaccurate or outdated?Submit a correction →

Listing History

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

  1. Oct 9, 2026
    Sato Hub began tracking this listing

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Skyfire

Is Skyfire open source?
No. Skyfire is closed source as of 2026-11-22.
Which chains does Skyfire support?
Skyfire lists support for Base as of 2026-11-22.
Is Skyfire still maintained?
Sato Hub tracks no commit or release for Skyfire; it cannot say whether it is maintained.
How do I install or run Skyfire?
Sato Hub has no deploy spec for Skyfire; follow the project's own documentation at https://docs.skyfire.xyz.
Is Skyfire verified on Sato Hub?
No independent verification is on record for Skyfire; its verification status is "Unverified" and its Sato Score is 20 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. "Skyfire — Sato Hub." Sato Hub, updated 2026-11-22, accessed 2026-11-22. https://satohub.ai/resources/skyfire

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.