Open-source project
ValueCell-ai/valuecell avatar
ValueCell-ai/valuecell

ValueCell: contract-only trading, three tested exchanges, and a 0.1.x beta

ValueCell is a community-driven, multi-agent platform for financial applications.

11,053 stars1,806 forksPythonApache-2.0

At a glance

What is it?
A community-driven, multi-agent platform for financial applications, shipped as a MacOS and Windows desktop app that wires language models to crypto exchanges. The exchange table grades its own support honestly; the contract-only trading model and the January release date are what to weigh first.
Who is it for?
Take ValueCell if you trade USDT-margined or USDC-margined contracts on Binance, Hyperliquid or OKX, and can accept a desktop install that keeps a LanceDB directory, a knowledge directory and valuecell.db beside your .env. Skip it if you need spot trading, if you need a library rather than an app, or if you need a release train: the newest tag is v0.1.20 from 2026-01-10 and the last push was on 2026-03-09.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 8 months ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • ValueCell-ai/valuecell11,053 ★ · +38
Star history
Repository2026-09-222026-11-15
ValueCell-ai/valuecell11k11.1k

38 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Contract trading only, with spot implemented as 1X contracts

Start with the constraint that decides whether ValueCell is usable for you at all. The README says only contract trading is currently supported, and that spot is implemented as 1X contracts. Perpetual trading is the only mode, so a Perps account holding sufficient balance is a prerequisite rather than an option.

That reaches past the trading screen. A spot-only account on any supported venue cannot be connected, and a futures account sitting at zero will not do: the Binance row tells you to ensure the perpetual contract account balance is not 0, and the notice at the bottom of the exchange table repeats that leverage trading is all there is.

Pair formats are fixed per exchange rather than inferred from a symbol you type. Binance uses `BTC/USDT`, OKX uses `BTC/USDT`, and Hyperliquid needs the pair adjusted by hand to `SYMBOL/USDC`, for example `WIF/USDC`, because it only supports USDC as margin currency. A strategy written against one venue's format will not transfer to another without editing.

Three exchanges are marked Tested, and one row is named Blockchain

The exchange table is the most useful page in this repository because it grades its own support. Seven rows, each carrying notes and a status. Binance, Hyperliquid and OKX hold the Tested mark, which the legend defines as fully tested and verified in production environment. Coinbase, Gate.io, MEXC and a seventh row labelled Blockchain hold Partially Tested, defined as code implementation complete but not fully tested, and may require debugging.

The recommendation follows directly: prioritize the fully tested exchanges, which the README names as Binance, Hyperliquid and OKX. If your venue is Coinbase, you are in the group the project itself flags as the one that may require debugging.

That seventh row deserves a note rather than a guess. It is labelled Blockchain, which is not an exchange name, and its requirement line reads API Key, Secret with a USDT-margined contract note. Whatever venue was intended, the row cannot be acted on as written, so read it as untested rather than reverse-engineering the exchange from its credential requirements.

Hyperliquid turns market orders into IoC limit orders

Each fully tested venue has a quirk worth knowing before a strategy touches it. On Hyperliquid, market orders are automatically converted to IoC limit orders, which means an order can fill partially or not at all instead of crossing the book at the quoted price. Logic that assumes full execution has to cope with partial fills.

Hyperliquid authentication also differs from the API key model used elsewhere: it needs your main wallet address plus an API wallet private key, applied for on the exchange's API tab, and it enforces a minimum of 10U per trade. Binance is the strictest at setup rather than at runtime: only the international site binance.com is supported and not the US site, it uses USDT-margined futures, and you are advised to add an IP whitelist to the API key. OKX is the only one of the three that also requires a passphrase, described as the OKX account password.

Market data is a separate list from execution. Coverage is given as the US market, crypto, Hong Kong and China, and exchange connectivity is described as live routing to OKX and Binance with built-in guardrails. The feature list mentions the guardrails without describing them, which is the gap to keep in mind.

An OpenRouter key alone will not unlock full functionality

The environment template makes the provider requirement explicit, and it is the first place to look when the research features feel inert. The primary setup uses OpenRouter plus another provider that supports embeddings, and the file states that to access full functionality you must include an embedding-capable provider. OpenRouter is called out as not currently supporting embedding or reranker models.

So the configuration splits in two. The agent needs a chat model from OpenRouter, SiliconFlow, Azure, Google, OpenAI, DeepSeek or any OpenAI-compatible endpoint, and something else has to serve embeddings. Fill in OPENROUTER_API_KEY alone and whatever depends on retrieval has no model behind it.

The same file fixes the local defaults:

bash
API_HOST=localhost
API_PORT=8000
OPENROUTER_API_KEY=
AZURE_OPENAI_API_KEY=

LANG is documented as mainly intended for frontend use, with setting LANG not required, and API_I18N_ENABLED switches on the four interface languages en, zh_CN, zh_TW and ja. SiliconFlow carries its own trap: a key obtained from siliconflow.com rather than siliconflow.cn needs siliconflow.yaml updated by hand.

LanceDB, .knowledge and valuecell.db sit beside your .env, per platform

Because secrets and data stay on the device, the storage layout is part of setup rather than an afterthought. Three stores live in the system application directory, on the same path as .env: a LanceDB directory, a knowledge directory, and the valuecell.db SQLite file.

bash
~/Library/Application Support/ValueCell/lancedb
~/.config/valuecell/lancedb
~/Library/Application Support/ValueCell/.knowledge
~/.config/valuecell/.knowledge
~/Library/Application Support/ValueCell/valuecell.db
~/.config/valuecell/valuecell.db

On Linux everything lands under `~/.config/valuecell/`, which is the line to remember when running this headless or in a container with a mounted home directory. Windows uses %APPDATA% as the root instead. The remedy the README offers for a stale install is blunt: if it has been a long time since the last update, delete the local data stores and start fresh, which takes your local knowledge base and history with them.

One inconsistency to ignore rather than trust: the example environment file declares APP_VERSION=0.1.0 while the newest release tag is v0.1.20, so the template is not a version marker.

Secrets stay local, and the README still tells you to rotate your keys

The security story rests on two claims and one instruction. The app stores secrets locally on your device and will not send them to any third party over the internet, and the description repeats that all sensitive information is stored locally to keep core data secure. Both claims cover where credentials sit at rest, not what the venue sees: the same credentials go to the exchange, which is why the README insists you keep API secrets secure to avoid losing funds and reset your API keys regularly.

The feature list mentions built-in guardrails on the live OKX and Binance routes without describing what they do. A guardrail you cannot inspect is a guardrail you have to test for yourself.

The project is also explicit about its own edges: team members will never proactively contact community participants, the project is for technical exchange only, and investing involves risk. That sits awkwardly beside a Strategy Agent whose description includes automatically executing your strategies, and it is worth reading before you wire an exchange key to it.

The repository is a Python service with a Makefile, not the app you download

The desktop app that new users download from the Releases page and the code in this repository are different shapes of thing. The tree holds a python/ backend, a frontend/, a docker/ directory, docs/, start.sh, start.ps1 and an .env.example. The Makefile has three targets, and they are the entire developer entry point:

bash
ruff check --config ./python/pyproject.toml ./python/
uv run pytest ./python
ruff format --config ./python/pyproject.toml ./python/ && uv run --directory ./python isort .

That is lint, test and format, driven by ruff, pytest and uv, with the Python configuration living in python/pyproject.toml. The Developers section of the README opens with an invitation to the Discord discussion group.

If you would rather keep your own agent framework, the integration note says the platform is compatible with Langchain and Agno by A2A Protocol for research and development integration.

No release tag since 2026-01-10 and no push since 2026-03-09

The version history is the thing to weigh before building on this. The newest release is v0.1.20, tagged ValueCell-0.1.20-beta on 2026-01-10, preceded by v0.1.19 on 2025-12-15 and v0.1.18 on 2025-12-09. Every tag in that series carries a beta marker, and the newest of them is still numbered 0.1.20.

The last push to the repository was on 2026-03-09, two months after that release. There has been no tag since 2026-01-10. The repository is not archived, so none of that says the project was abandoned, but the shape is a long beta rather than a steady release train, and an exchange API that changes shape underneath you is exactly the kind of thing that turns into your outage.

Licensing is Apache-2.0, the permissive licence with an express patent grant and a notice-preservation requirement, so there is no copyleft obligation riding on a fork. The cost sits elsewhere: a 0.1.x surface where the API can move between releases, paired with an exchange table that already marks four of its seven venues as possibly needing debugging.

Editorial conclusion

Take ValueCell if you trade USDT-margined or USDC-margined contracts on Binance, Hyperliquid or OKX, and can accept a desktop install that keeps a LanceDB directory, a knowledge directory and valuecell.db beside your .env. Skip it if you need spot trading, if you need a library rather than an app, or if you need a release train: the newest tag is v0.1.20 from 2026-01-10 and the last push was on 2026-03-09. Before you connect real credentials, check which row your venue occupies in the exchange table, and note that the README mentions built-in guardrails on the OKX and Binance routes without describing them, so test how they behave yourself.

Frequently asked questions

What is ValueCell?

ValueCell is a community-driven, multi-agent platform for financial applications, with a team of investment agents covering stock selection, research, tracking and trading. The README says sensitive information is stored locally on your device, and it also points to a hosted version at valuecell.ai that requires no deployment.

How do I use ValueCell?

New users download the latest ValueCell application for MacOS or Windows from the Releases page on GitHub, then configure a model provider before first use. For live trading you add your model API key through the web interface, set up Binance, HyperLiquid, OKX or Coinbase credentials, create a strategy, and start and stop the trader from the interface.

Which exchanges does ValueCell support for live trading?

The README marks Binance, Hyperliquid and OKX as Tested and recommends those three. Coinbase, Gate.io, MEXC and one row labelled Blockchain are marked Partially Tested, which the legend defines as code implementation complete but not fully tested and may require debugging.

Does ValueCell support spot trading?

Not directly. The README says only contract trading is currently supported and that spot is implemented as 1X contracts, so you need a Perps or futures account with sufficient balance rather than a spot balance.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. ValueCell-ai/valuecell on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/valuecell-ai-valuecell.svg)](https://hysenlabs.com/projects/valuecell-ai-valuecell)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/valuecell-ai-valuecell.svg)](https://hysenlabs.com/projects/valuecell-ai-valuecell)

Was this useful?