OpenByteInc / QuantDinger
“Open-source AI Trading OS, agent trading, and vibe trading, with Jev System One integration. Research, build Python strategies, backtest, and paper/live trade across crypto, stocks, and forex. Launch your own multi-tenan”
Jev Integrations rank #1In Harness #1
- 11.9kStars
- —Stars Δ / 1d
- —Stars Δ / 7d
- —Stars Δ / 30d
- 2.4kForks
- 78Watchers
GitHub ↗Official docs ↗Back to ranking
TL;DR
OpenByteInc/QuantDinger showed up as Jev / System One related work: Agent skill, MCP, or harness that routes work through Jev-style decisions.
The author describes it as: “Open-source AI Trading OS, agent trading, and vibe trading, with Jev System One integration. Research, build Python strategies, backtest, and paper/live trade across crypto, stocks, and forex. Launch your own multi-tenan” That is their claim, not a bench this site ran.
Who it’s for
- Agent / harness authors who need a typed gate, route, or prune step
- Quant or trading engineers who will keep ledger math in code
- Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe
What’s inside
Top-level entries on GitHub at generation time: .cursor, .dockerignore, .env.example, .gitattributes, .github, .gitignore, .gitleaksignore, .spectral.agent.yaml, .spectral.yaml, CODE_OF_CONDUCT.md, CONTRIBUTING.md, CONTRIBUTORS.md, DEVELOPMENT.md, LICENSE. Read those before you trust a one-line install.
How to use
- Clone and follow the author’s Python toolchain. Do not invent a package name.
git clone https://github.com/OpenByteInc/QuantDinger.git
cd QuantDinger
- If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
- Send a complete
stateand typed questions. Code owns control flow after the probabilities.
Hosted Jev still looks like a function call — wrapper or not:
{
model: "jev-1.13.0",
state: { source: "OpenByteInc/QuantDinger", brief: "..." },
questions: {
gate: { type: "noul", instructions: "Should we act on this state?" },
route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
},
}
Try this
Judgment, not the ledger
Using OpenByteInc/QuantDinger, have Jev Noul “is this fill evidence of a gap?” and Choice a regime label. Keep PnL and position limits in deterministic code.
Schema-safe ≠ correct
On a case OpenByteInc/QuantDinger gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.
FAQ
Does this replace the TypeSafe SDK?
Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.
Are the star chips live?
Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.
Sources
Public repository metadata and TypeSafe documentation. No private claims.