SIWA (Sign In With Agent)
Agent-identity authentication protocol modeled on Sign-In-With-Ethereum, letting services verify an agent before granting access.
- Sato Score59
- ChainsEthereum
SIWA (Sign In With Agent) is an open-source security tool by Builders Garden on Ethereum, with last code activity on 2026-04-29 (Quiet). Latest release on 2026-03-05. Sato Score 59/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See how to install SIWA (Sign In With Agent) →Last commit Apr 29, 2026 · Last release Mar 5, 2026 · ★ 43
Listed from siwa.id on 2026-07-19. Install: not attempted. Evidence →
Next step
Watch SIWA (Sign In With Agent)
One email if what we observe changes — its repo goes quiet or disappears, 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/mcpRun Sato Hub Preflight on builders-garden/siwa before I use it.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
SIWA adapts the Sign-In-With-Ethereum pattern to AI agents, giving services a way to challenge and verify an agent's onchain identity/signature before granting API or application access, instead of relying on shared API keys. Built by Builders Garden; 43 GitHub stars, last push April 2026.
Sato Score
59/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 18/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 3/10
Sato Check
v0.0.24 · as of 2026-09-29- Does it take your key?
- Asks for a key
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from siwa.id on 2026-07-19. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum | self-reported | siwa.id | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | siwa.id | as of 2026-10-21 |
| Recent activity | last release 2026-03-05 · last commit 2026-04-29 | observed | github.com/builders-garden/siwa | 2026-10-21 |
| Install works | documented by the project, not run by Sato Hubnot attempted: the run did not complete and the log named no cause we could attribute | self-reported | github.com/builders-garden/siwa | as of 2026-10-19 |
| Website answers | answered (HTTP 200) | observed | siwa.id | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Takes your key | asks for a private key or seed phrase | declared | satohub.ai | as of 2026-09-29 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-29 |
| Built by | Builders Gardenconfidence 0.80 | self-reported | siwa.id | as of 2026-08-07 |
| Works with | Next.js, Express, Hono, Fastify, Circle, Openfort, Privy, WalletClientconfidence 0.85 | self-reported | github.com/builders-garden/siwa | as of 2026-08-07 |
| Docs | https://siwa.id/docsconfidence 0.90 | self-reported | github.com/builders-garden/siwa | as of 2026-08-07 |
| Sato Score | 59/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
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.
Install — not run by us — the run did not complete and the log named no cause we could attribute
Runtime: Node.js (npm package)
npm install @buildersgarden/siwa
import { signSIWAMessage } from "@buildersgarden/siwa"; server middleware exports at @buildersgarden/siwa/next, /express, /hono, /fastifyYou supply: A wallet signer via one of the documented factories (Circle, Openfort, Privy, local account, keyring proxy, wallet client); local-account signing handles a private key — custody risk, .env.proxy.example lists proxy-mode variables (not enumerated in README)
Read from the project’s own docs as of 2026-10-19. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
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. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-21, one point per UTC day
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
- Ethereum
- Agent types
- Authentication protocol
- Open source
- Yes
- Works with
- Next.js, Express, Hono, Fastify, Circle, Openfort, Privy, WalletClient
- Last checked
- 2026-10-21
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.
Where SIWA (Sign In With Agent) fits
Related concepts: What Are Onchain Agents?, Onchain Agents vs Offchain Agents
Listing History
Recorded changes to SIWA (Sign In With Agent)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 19, 2026Verified: deploy spec
- Sep 26, 2026Edited: entity class, resource type
- Aug 7, 2026Auto-enriched: supported integrations, creator name, docs url
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
ERC-8004: Trustless Agents
ActiveEthereum standard providing on-chain identity, reputation, and validation registries for AI agents.
COTI
ActivePrivacy infrastructure that gives MCP-compatible agents private wallets, encrypted messaging, and confidential smart contracts using Garbled Circuits.
Turnkey
ActiveSecure key management infrastructure with policy controls, commonly used for agent wallets.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about SIWA (Sign In With Agent)
- Is SIWA (Sign In With Agent) open source?
- Yes. SIWA (Sign In With Agent) is open source under the MIT license; the repository is https://github.com/builders-garden/siwa. Checked as of 2026-10-21.
- Which chains does SIWA (Sign In With Agent) support?
- SIWA (Sign In With Agent) lists support for Ethereum as of 2026-10-21.
- Is SIWA (Sign In With Agent) still maintained?
- The most recent code activity Sato Hub observed was on 2026-04-29 (last commit 2026-04-29, last release 2026-03-05), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run SIWA (Sign In With Agent)?
- Node.js (npm package). Install: npm install @buildersgarden/siwa. Entry: import { signSIWAMessage } from "@buildersgarden/siwa"; server middleware exports at @buildersgarden/siwa/next, /express, /hono, /fastify. This is taken from the project's own documentation and has not been reproduced by Sato Hub.
- Is SIWA (Sign In With Agent) verified on Sato Hub?
- No independent verification is on record for SIWA (Sign In With Agent); its verification status is "Unverified" and its Sato Score is 59 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "SIWA (Sign In With Agent) — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/siwa-sign-in-with-agentData last refreshed 2026-10-21; 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.