Sato Hub
Agent Framework

Arbitrum Vibekit

Arbitrum-native, MCP-first agent framework with A2A and x402 support, backed by an Arbitrum Foundation grant program.

  • Sato Score72
  • ChainsArbitrum
ActiveUnverifiedRecent · 2mo ago

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/mcp
Run Sato Hub Preflight on emberagi/arbitrum-vibekit 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

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· High

How 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
Full profile, evidence and limits →

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.

ClaimValueEvidenceSourceChecked
Chains supportedArbitrumself-reporteddocs.emberai.xyzas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reporteddocs.emberai.xyzas of 2026-10-21
Recent activitylast release 2026-08-05 · last commit 2026-08-08observedgithub.com/EmberAGI/arbitrum-vibekit2026-10-21
Install worksdocumented by the project, not run by Sato Hubnot attempted: the run did not complete and the log named no cause we could attributeself-reportedraw.githubusercontent.comas of 2026-10-19
Website answersanswered (HTTP 200)observeddocs.emberai.xyz2026-10-21
Daily check record90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-09-29
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-29
X accounthttps://x.com/EmberAGIconfidence 0.80self-reportedgithub.com/EmberAGI/arbitrum-vibekitas of 2026-09-17
Sato Score72/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-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

100%of 91 checks since 2026-07-23 succeeded
Currently responding for 91 days
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

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
72
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
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.

#agent-framework#mcp#a2a#x402#arbitrum

Where Arbitrum Vibekit fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from Arbitrum Vibekit, pulled from its GitHub and X.

ReleaseEmberAGI/arbitrum-vibekitAug 5, 2026

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
GitHub ↗
ReleaseEmberAGI/arbitrum-vibekitAug 5, 2026

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
GitHub ↗
ReleaseEmberAGI/arbitrum-vibekitJul 31, 2026

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
GitHub ↗
ReleaseEmberAGI/arbitrum-vibekitJul 31, 2026

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

Arbitrum
GitHub ↗

Listing History

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

  1. Oct 19, 2026
    Verified: deploy spec
  2. Sep 26, 2026
    Edited: standards, provenance
  3. Sep 26, 2026
    Edited: standards
  4. Sep 17, 2026
    Auto-enriched: x url
  5. Sep 4, 2026
    Sato Score tier: High → Medium
    Score 79 → 69.
  6. Aug 5, 2026
    New release published
  7. Jul 31, 2026
    New release published
  8. Jul 24, 2026
    Sato Hub began tracking this listing
  9. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

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 pageShowHide

Cite this page

Sato Hub. "Arbitrum Vibekit — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/arbitrum-vibekit

Data 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.