Partly. Some of Enso is published as source (https://github.com/EnsoBuild/sdk-ts) and some is not. Checked as of 2026-10-24.

Which chains does Enso support?

Enso lists support for Ethereum, Base, Arbitrum, Optimism, Polygon, Multichain as of 2026-10-24.

Is Enso still maintained?

The most recent code activity Sato Hub observed was on 2026-10-16 (last commit 2026-10-16, last release 2026-09-25), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.

Is Enso verified on Sato Hub?

Sato Hub holds one earned check for Enso: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 80 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.

API / SDK

Enso

Name: Enso
Author: Enso

An intent-based onchain execution engine and API that lets developers and agents bundle multi-step DeFi actions into a single transaction.

Sato Score80
ChainsEthereum, Base +4

ActiveSelf-ReportedActive · 8d ago

Enso is a partly open-source API or SDK by Enso on Ethereum, Base, Arbitrum and other chains, with last code activity on 2026-10-16 (Active). Latest release on 2026-09-25. Sato Score 80/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 Enso →

Last commit Oct 16, 2026 · Last release Sep 25, 2026 (v2.6.0) · ★ 2

Listed from enso.build on 2026-06-08. Install: reproduced by Sato Hub on 2026-10-15. Evidence →

Website ↗Docs ↗GitHub ↗X / Twitter ↗

Next step

Watch Enso

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 ensobuild/sdk-ts 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

Enso provides 'Shortcuts' (composable bundles of standardized DeFi Actions (swap, lend, borrow, LP) across many EVM chains) exposed via a REST API and TypeScript SDK. AI agents use Enso to autonomously execute complex DeFi strategies in one atomic transaction. Enso has a live ENSO token; usage figures (apps, protocols, developers) are self-reported. It is execution infrastructure, not an autonomous agent itself.

Sato Score

80/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness: 35/35
Code transparency: 13/20
Interface verifiability: 8/10
Docs & demo: 6/10
Listing transparency & provenance: 15/15
Independent verification: 3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

View verification & embed badge →History →How the Sato Score works

Sato Check

v2.6.0 · as of 2026-09-26

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 enso.build on 2026-06-08. Install: reproduced by Sato Hub on 2026-10-15.

Claim	Value	Evidence	Source	Checked
Chains supported	Ethereum, Base, Arbitrum, Optimism, Polygon, Multichain	self-reported	docs.enso.build	as of 2026-10-24
Verification status	Self-Reported — not independently reviewed	self-reported	enso.build	as of 2026-10-24
Recent activity	last release 2026-09-25 · last commit 2026-10-16	observed	github.com/EnsoBuild/sdk-ts	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/EnsoBuild/sdk-ts	2026-10-15
Website answers	answered (HTTP 200)	observed	enso.build	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-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	Ensoconfidence 0.80	self-reported	github.com/EnsoBuild/sdk-ts	as of 2026-06-25
Deploys as	npm, APIconfidence 0.90	self-reported	github.com/EnsoBuild/sdk-ts	as of 2026-06-25
Works with	Aave V3, Uniswap, Morpho, LayerZero, Stargate, CCTP, CCIPconfidence 0.85	self-reported	github.com/EnsoBuild/sdk-ts	as of 2026-06-25
Tags	intents, shortcuts, defi, api, sdk, execution-layer, agent-tooling, routing, bu…confidence 0.80	self-reported	github.com/EnsoBuild/sdk-ts	as of 2026-06-25
X account	https://x.com/EnsoBuildconfidence 0.90	self-reported	github.com/EnsoBuild/sdk-ts	as of 2026-06-25
Sato Score	80/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 / TypeScript

npm install @ensofinance/sdk
import { EnsoClient } from "@ensofinance/sdk";
const ensoClient = new EnsoClient({ apiKey: "YOUR_API_KEY" });
// discover chains at runtime: await ensoClient.getNetworks()

You supply: an Enso API key

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

100%of 91 checks since 2026-07-26 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. 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

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

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: Ethereum, Base, Arbitrum, Optimism, Polygon, Multichain
Agent types: DeFi Agent
Open source: Partial
Deploys as: npm, API
Works with: Aave V3, Uniswap, Morpho, LayerZero, Stargate, CCTP, CCIP
Last checked: 2026-10-24

Marketplace Signals

▸ Can be licensed

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#intents#shortcuts#defi#api#sdk#execution-layer#agent-tooling#routing#bundling#bridging#typescript

Where Enso fits

Trading

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from Enso, pulled from its GitHub and X.

ReleaseEnsoBuild/sdk-ts29d ago

sdk-ts v2.6.0

2.6.0

EthereumBaseArbitrum

GitHub ↗

ReleaseEnsoBuild/sdk-tsJul 14, 2026

sdk-ts v2.5.0

2.5.0

EthereumBaseArbitrum

GitHub ↗

ReleaseEnsoBuild/sdk-tsMay 19, 2026

sdk-ts v2.4.2

2.4.2

EthereumBaseArbitrum

GitHub ↗

ReleaseEnsoBuild/sdk-tsMay 18, 2026

sdk-ts v2.4.1

2.4.1

EthereumBaseArbitrum

GitHub ↗

Listing History

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

Oct 15, 2026
Verified: deploy spec
Sep 25, 2026
New release published
Sep 1, 2026
Sato Score tier: Medium → High
Score 67 → 70.
Aug 14, 2026
Sato Score tier: High → Medium
Score 77 → 67.
Jul 27, 2026
Sato Hub began tracking this listing
Jun 25, 2026
Auto-enriched: creator name, x url, supported integrations, deployment options +1 more

Compared with

Alternatives to Enso →

Appears in

Related Resources

Coinbase AgentKit

Active

Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain

Active★ 1.3k

ElizaOS

Active

Framework

Open-source TypeScript framework for building crypto-native multi-agent systems.

SolanaEthereumBaseMultichain

Active★ 20k

Jupiter

Active

VenueVerified

Solana swap aggregator that routes trades across DEXs via a widely used API and SDKs.

Solana

Recent★ 183▸ Oct 2021

Reference

QuestionsWhat people ask about this pageShowHide

Cite this pagePlain text, APA or BibTeXShowHide

Cite this page

Sato Hub. "Enso — Sato Hub." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/resources/enso-shortcuts

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

Enso

Next step

Watch Enso

Check it from your agent

Your project?

Overview

Sato Score

Sato Check

Evidence — listed vs checked · what the words mean

Install — reproduced in a container Oct 15, 2026

Observed record — 91 daily checks since 2026-07-26

Last 30 days — to 2026-10-24, one point per UTC day

Details

Marketplace Signals

Where Enso fits

Recent Activity

sdk-ts v2.6.0

sdk-ts v2.5.0

sdk-ts v2.4.2

sdk-ts v2.4.1

Listing History

Compared with

Appears in

Related Resources

Coinbase AgentKit

ElizaOS

Jupiter

Questions people ask about Enso

Cite this page

Join the Sato Hub Briefing