Privy
Embedded and server wallet infrastructure used to give agents secure key management.
- Sato Score84
- ChainsEthereum, Base +2
Privy is a partly open-source wallet infrastructure by Privy on Ethereum, Base and Solana, with last code activity on 2026-10-23 (Active). Latest release on 2026-10-16. Sato Score 84/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-24. How the score works →
See how to install Privy →Last commit Oct 23, 2026 · Last release Oct 16, 2026 (v0.36.0) · ★ 3
Last news post Oct 20, 2026 on X
Listed from privy.io on 2026-06-06. Install: reproduced by Sato Hub on 2026-10-15. Evidence →
Next step
Watch Privy
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 privy-io/node-sdk 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
Privy provides embedded wallets and server-side wallet APIs that let applications (and increasingly AI agents) hold keys and sign transactions with policy controls. Its server wallets and policy engine are used by agent builders who need programmatic signing with guardrails.
Sato Score
84/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 13/20
- Interface verifiability
- 8/10
- Docs & demo
- 10/10
- Listing transparency & provenance
- 15/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v0.36.0 · as of 2026-10-17- Does it take your key?
- No key read found
- 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 privy.io on 2026-06-06. Install: reproduced by Sato Hub on 2026-10-15.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Base, Solana, Multichain | self-reported | docs.privy.io | as of 2026-10-24 |
| Verification status | Unverified — not independently reviewed | self-reported | privy.io | as of 2026-10-24 |
| Recent activity | last release 2026-10-16 · last commit 2026-10-23 | observed | github.com/privy-io/node-sdk | 2026-10-24 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/privy-io | 2026-10-15 |
| Website answers | answered (HTTP 308) | observed | privy.io | 2026-10-24 |
| Daily check record | 90 of 90 daily checks since 2026-07-26 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-23 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-10-17 |
| 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-10-17 |
| Built by | Privyconfidence 0.70 | self-reported | github.com/privy-io | as of 2026-06-25 |
| Creator profile | https://github.com/privy-ioconfidence 0.80 | self-reported | github.com/privy-io | as of 2026-06-25 |
| Deploys as | API, SDK, Hostedconfidence 0.80 | self-reported | docs.privy.io | as of 2026-06-25 |
| Works with | REST API, Node.js SDK, React SDK, Swift SDK, Android SDK, Unity SDK, Go SDK, Ru…confidence 0.85 | self-reported | docs.privy.io | as of 2026-06-25 |
| Agent types | Wallet, Agent Walletconfidence 0.80 | self-reported | privy.io | as of 2026-06-25 |
| Tags | wallets, key-management, infrastructure, embedded-wallets, agent-wallets, polic…confidence 0.80 | self-reported | privy.io | as of 2026-06-25 |
| Demo available | yesconfidence 0.70 | self-reported | privy.io | as of 2026-06-25 |
| Sato Score | 84/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-24 |
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 — reproduced in a container Oct 15, 2026
Runtime: Node.js
npm install @privy-io/node
import { PrivyClient } from '@privy-io/node';
const privy = new PrivyClient({ appId: process.env.PRIVY_APP_ID, appSecret: process.env.PRIVY_APP_SECRET });
const wallet = await privy.wallets().create({ chain_type: 'ethereum' });You supply: PRIVY_APP_ID + PRIVY_APP_SECRET (server-to-server), authorization keys for signing/transactions
Read from the project’s own docs as of 2026-10-15. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-26
- 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. 37 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-24, 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.
Skills that target this — 3, with disclosures
integration-privyskills.sh · solana-mobile
9,068 installsAdd Privy authentication to a Solana Expo Android app on top of Mobile Wallet Adapter, using Sign-In-With-Solana. Use when installing @privy-io/expo, mounting PrivyProvider, logging a user in with useLoginWithSiws, linking a wallet to an existing Privy account, reading the Privy access token from a backend, or debugging a Privy plus MWA setup.
USDC Krump EVVM x402 PaymentClawHub · arunnadarasa
825 installsPay with USDC Krump (USDC.k) via x402 on Story Aeneid EVVM. Supports EVVM Native adapter (no EIP-3009 on token) and legacy Bridge adapter. Requires PRIVY_APP...
Usdc Dance Evvm PaymentClawHub · arunnadarasa
592 installsPay with USDC.d via x402 protocol on Story Aeneid EVVM using Privy server wallets. Uses BridgeUSDC (custom bridge) until LayerZero supports Story Aeneid.
Disclosures describe what a skill declares and does; they are not safety verdicts. All skills →
Details
- Chains
- Ethereum, Base, Solana, Multichain
- Agent types
- Wallet, Agent Wallet
- Open source
- Partial
- Pricing
- Free tier + paid plans
- Deploys as
- API, SDK, Hosted
- Works with
- REST API, Node.js SDK, React SDK, Swift SDK, Android SDK, Unity SDK, Go SDK, Ruby SDK
- Last checked
- 2026-10-24
Marketplace Signals
- ▸ Demo available
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Recent Activity
All news →Releases and posts from Privy, pulled from its GitHub and X.
Artisan (@UseArtisan) went live in weeks with stablecoin-backed cards* using Privy’s prebuilt components and @stripe Issuing. Launching a card program* has traditionally meant managing onboarding, KYC
Artisan (@UseArtisan) went live in weeks with stablecoin-backed cards* using Privy’s prebuilt components and @stripe Issuing. Launching a card program* has traditionally meant managing onboarding, KYC, fraud tooling, support, and bank approval across multiple vendors. Privy’s prebuilt components bring that experience together, with pre-approved UI for onboarding, card creation, transaction history
RT @Didotxyz_: We’re partnering with @privy_io to power a smoother, more seamless onboarding experience across the DI ecosystem. Less fric…
1/ Privy lets developers give AI agents stablecoin wallets to hold funds and pay as they work. But not all agent wallets work the same way. With @link Agent Wallet and @stripe Issuing, agents can also
1/ Privy lets developers give AI agents stablecoin wallets to hold funds and pay as they work. But not all agent wallets work the same way. With @link Agent Wallet and @stripe Issuing, agents can also spend using saved cards or stablecoin-backed cards. https://t.co/hAIkUqP5Sl
node-sdk v0.36.0
0.36.0 (2026-10-16) Features api: api update ( 10257d3 ) api: api update ( df933c1 ) api: api update ( 1477e02 ) api: api update ( a1a3ace ) api: api update ( b758250 ) api: api update ( d81fbd8 ) api: api update ( f9fd9da ) api: api update ( 037b15e ) api: api update ( de6de42 ) api: api update ( f5ce62c ) api: api update ( 5d77d19 ) api: api update ( 736d6c6 ) api: api update ( e4bc3bf ) api: ap
2/ With 8M+ funded accounts, and $1T+ in value moved, XRPL is moving digital assets at scale. Privy enables developers to integrate XRPL wallets into their apps, combining programmable transactions wi
2/ With 8M+ funded accounts, and $1T+ in value moved, XRPL is moving digital assets at scale. Privy enables developers to integrate XRPL wallets into their apps, combining programmable transactions with seamless onboarding + user ownership. Read more: https://t.co/UsrCk3ZA07
1/ We're partnering with @Ripple to bring Privy wallets to the XRP Ledger (XRPL). This makes it easier for developers to build stablecoin payments, fintech applications, and agentic commerce on XRPL.
1/ We're partnering with @Ripple to bring Privy wallets to the XRP Ledger (XRPL). This makes it easier for developers to build stablecoin payments, fintech applications, and agentic commerce on XRPL. https://t.co/vUhKJdfxBT
Listing History
Recorded changes to Privy's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 16, 2026New release published
- Oct 15, 2026Verified: deploy spec
- Jul 27, 2026Sato Hub began tracking this listing
- Jun 25, 2026Enriched: creator name, has demo, marketplace notes
- Jun 25, 2026Auto-enriched: tags, agent type, deployment options, supported integrations +2 more
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Agent Payments Protocol (AP2)
ActiveOpen protocol from Google for secure agent-led payments across traditional and crypto rails, with a crypto-native x402 extension built with Coinbase, Ethereum Foundation, and MetaMask.
x402
EarlyOpen HTTP 402 payment protocol, now at the x402 Foundation: agents pay per request in stablecoins, and by a newly merged spec, in bitcoin over Lightning.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Privy
- Is Privy open source?
- Partly. Some of Privy is published as source (https://github.com/privy-io/node-sdk) and some is not. Checked as of 2026-10-24.
- Which chains does Privy support?
- Privy lists support for Ethereum, Base, Solana, Multichain as of 2026-10-24.
- Is Privy still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-23 (last commit 2026-10-23, last release 2026-10-16), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Privy?
- Node.js. Install: npm install @privy-io/node. Entry: import { PrivyClient } from '@privy-io/node'; const privy = new PrivyClient({ appId: process.env.PRIVY_APP_ID, appSecret: process.env.PRIVY_APP_SECRET }); const wallet = await privy.wallets().create({ chain_type: 'ethereum' });. Sato Hub reproduced this install in a container on 2026-10-15.
- Is Privy verified on Sato Hub?
- Sato Hub holds one earned check for Privy: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 84 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Privy — Sato Hub." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/resources/privyData last refreshed 2026-10-24; 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.