Arbitrum Vibekit
Arbitrum-native, MCP-first agent framework with A2A and x402 support, backed by an Arbitrum Foundation grant program.
- Sato Score72
- ChainsArbitrum
Arbitrum Vibekit is an open-source agent framework on Arbitrum, with last code activity on 2026-08-08 (Recent). Latest release on 2026-08-05. Sato Score 72/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 Arbitrum Vibekit →Last commit Aug 8, 2026 · Last release Aug 5, 2026 (@emberai/onchain-actions-registry@4.8.0) · ★ 53
Listed from docs.emberai.xyz on 2026-07-19. Install: not attempted. Evidence →
Next step
Watch Arbitrum Vibekit
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 emberagi/arbitrum-vibekit 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
Arbitrum Vibekit, built by Ember AI, is an agent framework designed around MCP tool-calling and the A2A agent-to-agent protocol, with native x402 payment support for Arbitrum-based agents. It's backed by the Arbitrum Foundation's Trailblazer 2.0 grant program, which funds agents built on it, and is under active development.
Sato Score
72/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 25/35
- Code transparency
- 18/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 10/15
- Independent verification
- 5/10
Sato Check
v1.2.2 · as of 2026-09-29- 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 docs.emberai.xyz on 2026-07-19. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Arbitrum | self-reported | docs.emberai.xyz | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | docs.emberai.xyz | as of 2026-10-21 |
| Recent activity | last release 2026-08-05 · last commit 2026-08-08 | observed | github.com/EmberAGI/arbitrum-vibekit | 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 | raw.githubusercontent.com | as of 2026-10-19 |
| Website answers | answered (HTTP 200) | observed | docs.emberai.xyz | 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 | no private-key read found in what we read | traced | satohub.ai | 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 |
| X account | https://x.com/EmberAGIconfidence 0.80 | self-reported | github.com/EmberAGI/arbitrum-vibekit | as of 2026-09-17 |
| Sato Score | 72/100 (High)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 >=18 (npx package @emberai/agent-node)
npx -y @emberai/agent-node@latest init npx -y @emberai/agent-node@latest npx -y @emberai/agent-node@latest
You supply: AI provider API key (OpenRouter, OpenAI, xAI, or Hyperbolic) — on-chain env vars (wallet keys, RPC URLs) not enumerated in the 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
- Arbitrum
- Agent types
- Agent framework
- Open source
- Yes
- 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 Arbitrum Vibekit fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from Arbitrum Vibekit, pulled from its GitHub and X.
arbitrum-vibekit @emberai/onchain-actions-registry@4.8.0
@emberai/onchain-actions-registry 4.8.0 (2026-08-05) Dependencies @emberai/onchain-actions-contracts: upgraded to 1.1.0
arbitrum-vibekit @emberai/onchain-actions-contracts@1.1.0
@emberai/onchain-actions-contracts 1.1.0 (2026-08-05) Features onchain-actions-contracts: make canonical token identity chain-aware ( fbcba4b ) Bug Fixes onchain-actions-contracts: brand CanonicalTokenIdentifierV1 to close the TokenPriceReader type-forgeability gap ( 5fdd89a ) onchain-actions-contracts: canonicalize evm token identity to EIP-55 ( 83f4c7e ) onchain-actions-contracts: close CAIP-2,
arbitrum-vibekit @emberai/onchain-actions-registry@4.7.0
@emberai/onchain-actions-registry 4.7.0 (2026-07-31) Features contracts: publish neutral onchain action contracts ( b7932d4 ) Bug Fixes packaging: support current npm pack output ( f2f8577 ) registry: build contracts before lint ( b1131dc ) Dependencies @emberai/onchain-actions-contracts: upgraded to 1.0.0
arbitrum-vibekit @emberai/onchain-actions-contracts@1.0.0
@emberai/onchain-actions-contracts 1.0.0 (2026-07-31) Features contracts: publish neutral onchain action contracts ( b7932d4 ) Bug Fixes contracts: close canonical identity and release gaps ( fc35157 ) contracts: close request and release gaps ( 74aa1c1 ) contracts: enforce fresh-only result currentness ( ca43256 ) contracts: enforce generic result currentness ( d0ecbfe ) contracts: enforce receip
Listing History
Recorded changes to Arbitrum Vibekit'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: standards, provenance
- Sep 26, 2026Edited: standards
- Sep 17, 2026Auto-enriched: x url
- Sep 4, 2026Sato Score tier: High → MediumScore 79 → 69.
- Aug 5, 2026New release published
- Jul 31, 2026New release published
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
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.
ElizaOS
ActiveOpen-source TypeScript framework for building crypto-native multi-agent systems.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Arbitrum Vibekit
- Is Arbitrum Vibekit open source?
- Yes. Arbitrum Vibekit is open source under the MIT license; the repository is https://github.com/EmberAGI/arbitrum-vibekit. Checked as of 2026-10-21.
- Which chains does Arbitrum Vibekit support?
- Arbitrum Vibekit lists support for Arbitrum as of 2026-10-21.
- Is Arbitrum Vibekit still maintained?
- The most recent code activity Sato Hub observed was on 2026-08-08 (last commit 2026-08-08, last release 2026-08-05), which Sato Hub labels "Recent". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Arbitrum Vibekit?
- Node.js >=18 (npx package @emberai/agent-node). Install: npx -y @emberai/agent-node@latest init && npx -y @emberai/agent-node@latest. Entry: npx -y @emberai/agent-node@latest. This is taken from the project's own documentation and has not been reproduced by Sato Hub.
- Is Arbitrum Vibekit verified on Sato Hub?
- No independent verification is on record for Arbitrum Vibekit; its verification status is "Unverified" and its Sato Score is 72 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. "Arbitrum Vibekit — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/arbitrum-vibekitData 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.