VeilNet
Privacy-preserving x402 payments for agents on Base, with stealth addresses and TEE-encrypted inference, no accounts or API keys.
- Sato Score47
- ChainsBase, Ethereum
VeilNet is a partly open-source API or SDK by Veilnet on Base and Ethereum, with no code activity tracked. Sato Score 47/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-25. How the score works →
See how to install VeilNet →No code activity tracked
Listed from veilnet.to on 2026-06-12. Install: not attempted. Evidence →
Next step
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpAsk Sato Hub what is on record about VeilNet 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
VeilNet is a privacy-focused protocol that lets autonomous agents pay for services through machine-to-machine x402 (HTTP 402) transactions on Base without accounts or API keys. It pairs encrypted AI inference running in attested TEEs with private settlement: stealth addresses (EIP-5564 / ERC-6538) generate one-time payment recipients and gasless USDC transfers (EIP-3009) avoid the agent holding gas. Payments settle through the PayAI x402 facilitator, and VeilNet ships an open-source TypeScript SDK (@veilnet/stealth-x402). Live on Base mainnet; privacy and settlement claims are the project's own.
Sato Score
47/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 4/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 14/15
- Independent verification
- 3/10
Sato Check
v0.5.2 · as of 2026-09-26- 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 veilnet.to on 2026-06-12. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Base, Ethereum | self-reported | docs.veilnet.to | as of 2026-06-25 |
| Verification status | Unverified — not independently reviewed | self-reported | veilnet.to | as of 2026-10-25 |
| Install works | documented by the project, not run by Sato Hubnot attempted by Sato Hub | self-reported | docs.veilnet.to | as of 2026-07-20 |
| Website answers | answered (HTTP 200) | observed | veilnet.to | 2026-10-25 |
| Daily check record | 90 of 90 daily checks since 2026-07-27 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-24 |
| Takes your key | asks for a private key or seed phrase | declared | satohub.ai | as of 2026-09-26 |
| 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-26 |
| Built by | Veilnetconfidence 0.85 | self-reported | docs.veilnet.to | as of 2026-06-25 |
| Deploys as | MCP server, APIconfidence 0.75 | self-reported | docs.veilnet.to | as of 2026-06-25 |
| Works with | Model Context Protocol (MCP), Claude Code, Cursorconfidence 0.80 | self-reported | veilnet.to | as of 2026-06-25 |
| Tags | privacy, x402, stealth-addresses, tee, payments, base, agent-payments, usdc, co…confidence 0.80 | self-reported | veilnet.to | as of 2026-06-25 |
| Sato Score | 47/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-25 |
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 — as documented by the project, not run by us
Runtime: Node.js >=22 (native WebCrypto required); MCP server via npx
claude mcp add veilnet --scope user -- npx -y @veilnet/mcp-server
{"mcpServers": {"veilnet": {"command": "npx", "args": ["-y", "@veilnet/mcp-server"]}}}You supply: session.json + master.key files at ~/.veilnet/ downloaded from app.veilnet.to Agent tab (private key material — local custody risk), funded shielded-USDC balance on VeilNet
claude mcp add satohub-veilnet -- npx -y @veilnet/mcp-server
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-07-20. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-27
- 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. 36 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-25, 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
- Base, Ethereum
- Agent types
- Payments Protocol, Privacy Protocol
- Open source
- Partial
- Pricing
- Free tier up to ~10k settlements/month, then metered via PayAI (per VeilNet)
- Deploys as
- MCP server, API
- Works with
- Model Context Protocol (MCP), Claude Code, Cursor
- Last checked
- 2026-10-25
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.
Listing History
Recorded changes to VeilNet's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 28, 2026Sato Hub began tracking this listing
- Jul 20, 2026Edited: deploy spec
- Jun 25, 2026Enriched: deployment options, marketplace notes
- Jun 25, 2026Auto-enriched: creator name, chains supported, supported integrations, tags
Compared with
Appears in
- x402 payment tools on Base, scored →
- Base MCP servers, scored →
- Ethereum MCP servers, scored →
- x402-ready tools, scored →
- What crypto MCP servers do with your keys: dated Sato Check readings →
- x402 endpoints checked for a payment-required answer →
- x402 facilitators on Base →
- x402: agent payments over HTTP →
- MCP: the tool interface for agents →
- Onchain agents on Base →
- Onchain agents on Ethereum →
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about VeilNet
- Is VeilNet open source?
- Partly. Some of VeilNet is published as source and some is not. Checked as of 2026-10-25.
- Which chains does VeilNet support?
- VeilNet lists support for Base, Ethereum as of 2026-10-25.
- Is VeilNet still maintained?
- Sato Hub tracks no commit or release for VeilNet; it cannot say whether it is maintained.
- How do I install or run VeilNet?
- Node.js >=22 (native WebCrypto required); MCP server via npx. Install: claude mcp add veilnet --scope user -- npx -y @veilnet/mcp-server. Entry: {"mcpServers": {"veilnet": {"command": "npx", "args": ["-y", "@veilnet/mcp-server"]}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (npx -y @veilnet/mcp-server (stdio)).
- Is VeilNet verified on Sato Hub?
- No independent verification is on record for VeilNet; its verification status is "Unverified" and its Sato Score is 47 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. "VeilNet — Sato Hub." Sato Hub, updated 2026-10-25, accessed 2026-10-25. https://satohub.ai/resources/veilnetData last refreshed 2026-10-25; 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.