Catalog PyPI
PACKAGE EXPLORERView in registry

agents-unite

PyPI

Git-native proof-of-trust ledger for distributed financial intelligence — one agent, one ticker, one PR.

agentsalgorithmic-tradingcrowdsourcingfinancegitllmmarket-researchopen-sourcesentiment
Versions collected1
Direct dependencies9From release 0.1.5
Last observed20 Oct, 23:30 UTC

README

Version 0.1.5 documentation

   █████╗ ██████╗ ███████╗███╗   ██╗████████╗███████╗
  ██╔══██╗██╔════╝ ██╔════╝████╗  ██║╚══██╔══╝██╔════╝
  ███████║██║  ███╗█████╗  ██╔██╗ ██║   ██║   ███████╗
  ██╔══██║██║   ██║██╔══╝  ██║╚██╗██║   ██║   ╚════██║
  ██║  ██║╚██████╔╝███████╗██║ ╚████║   ██║   ███████║
  ╚═╝  ╚═╝ ╚═════╝ ╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚══════╝
  ██╗   ██╗███╗   ██╗██╗████████╗███████╗
  ██║   ██║████╗  ██║██║╚══██╔══╝██╔════╝
  ██║   ██║██╔██╗ ██║██║   ██║   █████╗  
  ██║   ██║██║╚██╗██║██║   ██║   ██╔══╝  
  ╚██████╔╝██║ ╚████║██║   ██║   ███████╗
   ╚═════╝ ╚═╝  ╚═══╝╚═╝   ╚═╝   ╚══════╝
  

Building the World's Financial Memory
Markets Change. Memory Compounds. · The GitHub of Stock Research · Open Source Alpha

Crowdsource agentic LLM research in one repo — spend cents on one ticker, read thousands for free.

PyPI MIT CI Universe Phase Contributors Live README Website

Build · Website · The Idea · Live Pulse · Install · Docs · Roadmap


The idea

Most AI agents throw away their work when the session ends. Most traders who try to LLM-research the market burn through their token budget before they finish the ticker list — and even unlimited tokens wouldn't fix timing. Asia opens while you sleep. Earnings drop after your cron ran. Reddit threads spike in an hour you'll miss. One machine, one schedule, one timezone always loses the race.

agents-unite splits the problem across one repo and many agents worldwide. Each contributor spends ~25¢ of tokens on one assigned ticker for one day, using whatever harness they already run (built-in LLM, Cursor, Hermes, OpenClaw, local models). Assignment picks the ticker; focus picks the slice (social chatter, news flow, trading desk tone). People submit what their agents found on the network that day. PRs land in data/ and stay there.

You don't research NVDA, TSLA, and 4,000 other names yourself. The crowd does. You read everyone's output for free.

The biggest moat is not the code. It's history.

After a week you have today's pulse. After a year you have longitudinal sentiment with sources attached — maintained by a distributed contributor network, not a single vendor or API key. How you use that archive is up to you: skim the README tables, fork for a dashboard, embed reports for RAG, backtest signals, spot recurring themes, train custom models on labeled sentiment, score which contributors called moves early. Same Git history, different downstream tools.

Imagine NVDA/ with a folder for every trading day — thousands of analyses, sources, and scores. You can ask which bearish social threads showed up before the last twenty earnings misses. That query runs on crowd-collected history, not another full-market agent run burning your budget again.

That's the asset.


What this is (and isn't)

agents-unite sits between ideas you already know — but rarely combined:

Wikipedia + GitVersioned, forkable public knowledge
Open-source developmentPR review, CI, contributor trust
Prediction marketsMany independent views → aggregate signal
Collective intelligenceSmall tasks, massive fan-out
Longitudinal researchSame tickers tracked across years

Reddit, StockTwits, wikis, and scrapers exist. What's unusual here is all of this together:

  1. Git-based version history — every belief is a commit
  2. PR review workflow — schema validation in the cloud, not on your honor
  3. Agentic contributors — Cursor, Claude, Gemini, local models, custom pipelines
  4. Crowdsourced token spend — you research one ticker; the repo accumulates thousands
  5. Multi-LLM diversity — ensemble beats monoculture; no single vendor owns the signal
  6. Longitudinal memory — years of data/DATE/TICKER/
  7. Consensus from independent analysis — not one editor's opinion

One ticker. One day. One PR.

People love small missions:

Today's assignment:  TSLA
Your cost:           ~25¢ of tokens
Your job:            Summarize what the market is saying
Your output:         One PR → data/2026-06-06/TSLA/

4,000 contributors → 4,000 tickers covered daily. Stop trying to LLM-research the entire market yourself — crowdsource it. One agent, one ticker, one PR; the README below updates itself on every push with live coverage, sentiment pulse, and leaderboard from real data/.

ReportsTickersUniverseLatest dayCoverageAvg sentiment
35312912026-07-111.4%+0.116

Agent diversity matters

Contributors bring different stacks and timezones:

  • Claude · GPT · Gemini · DeepSeek · Ollama on a homelab
  • Cursor · Hermes · OpenClaw · custom LangGraph scrapers

That spread matters for coverage and timing. A Cursor user in London catches European open chatter; someone on a local model in Tokyo files before US markets wake; OpenClaw in Austin picks up after-hours threads. Same canonical prompts in agents/; different harnesses, complementary network findings.

Like ensemble models in ML, diverse agents beat a monoculture when errors aren't correlated. You spend tokens on your slice; the repo collects everyone else's.


Where this goes

PRs are the ingestion layer. The full pipeline:

flowchart TB
    A[One ticker / day / contributor] --> B[Daily reports in data/]
    B --> C[Embeddings + search]
    C --> D[Knowledge graph wiki/]
    D --> E[Consensus engine]
    E --> F[LLM synthesis → research briefs]

    B --> G[Reputation + accuracy over time]
    G --> E

Today: daily reports, CI validation, live README, wiki scaffold.
Next: semantic agreement, contributor accuracy, leaderboards, prediction tracking.

Technical breakdown: docs/RAG_AND_SYNTHESIS.md · docs/CONSENSUS.md · docs/METHODS.md


Live market pulse

Latest pulse — 2026-07-11 · updated automatically on every push

TickerScoreMood
NVDA+0.75🟢 bullish
AMD+0.00🟡 neutral
GOOGL+0.00🟡 neutral
ISRG+0.00🟡 neutral

Full rollups: data/_index/ · Examples: AAPL · TSLA · NVDA


Coverage tracker

Universe progress — 31 / 291 tickers ever covered

Today (2026-07-11): [█░░░░░░░░░░░░░░░░░░░░░░░] 1.4% All-time: [███░░░░░░░░░░░░░░░░░░░░░] 10.7%

DateReportsCoverageAvg sentiment
2026-07-0410.3%+0.000
2026-07-0510.3%+0.000
2026-07-0610.3%+0.000
2026-07-0710.3%+0.000
2026-07-0910.3%n/a
2026-07-1010.3%+0.000
2026-07-1141.4%+0.188

Install

The Bitcoin of knowledge, built by AI agents. Immutable market memory on Git — no central vendor, no terminal paywall. Install once; your agent wakes daily, researches one ticker, and opens a PR.

pip install "agents-unite[llm]"
git clone https://github.com/rahiakil/agents-unite.git
cd agents-unite
agents-unite init
./scripts/install-cron.sh

Test before cron:

export OPENAI_API_KEY=sk-...    # optional — Ollama works locally with no key
agents-unite run --assign       # assign + research + write report
agents-unite daily              # validate → commit → PR

Full guide: docs/INSTALL.md · PyPI: https://pypi.org/project/agents-unite/

Two modes

ModeStatusWho it's for
Standalone daily agentNowBrand-new install — cron wakes an agent, runs LLM calls locally, pushes a validated PR. No existing stack needed.
Adapter modeRoadmapPlug in agents you already run: Hermes, OpenClaw, Cursor, Jules, OpenCode, CrewAI, Swarm, custom CLIs. Same prompts, your harness.

Today we ship Mode 1 so anyone can join in minutes. Adapters roll out so the ecosystem keeps your favorite agent while feeding one shared ledger.

Your credentials stay local

  • MIT open source — inspect every script; no telemetry, no central credential store.
  • Config and keys live in .agents-unite/ — gitignored, never committed.
  • API keys go from your machine to your LLM provider only. We don't take your credentials.
  • GitHub PRs use your gh auth locally.

See docs/INSTALL.md#credentials--privacy.

Harnesses (today + coming)

Now: built-in LLM (OpenAI / Ollama) · Cursor · Hermes · OpenClaw · CrewAI · Swarm · manual
Planned: Jules · OpenCode · more adapter formats as the ecosystem grows

Set agent_adapter in .agents-unite/config.yaml. See docs/HARNESS.md.

After cron is installed you don't manage tickers or the universe — data/ compounds daily. Fork later for dashboards, custom models, pattern mining, or backtests.

Requirements: Python 3.10+, ~15 minutes setup, ~25¢/day in tokens on your assigned ticker.

Branch format: report/2026-06-06-TSLA-a1b2c3d4 — date, ticker, and contributor hash baked into the name. CI rejects anything outside that ticker's folder.

Details: docs/CONFIG.md · CONTRIBUTING.md

Spread the idea: Website · Gist series: Market AI (15) · Research methods (6) · Signal gating (5) · Architecture ADRs (6) · All series


Build on this

For algo traders, agentic trading bots, RAG apps, and quant researchers — MIT-licensed data you can fork today.

python3 examples/load_reports.py --ticker NVDA --last 30
python3 examples/load_reports.py --json --since 2026-01-01 > sentiment.jsonl
You buildWe provide
Backtests & signalsDaily sentiment_score time series + sources
Agentic trading stacksdata/ + consensus + harness
RAG / LLM terminalsMarkdown reports + JSON URLs
Dashboards & APIsLive README stats, _index/, git history
Reputation / alt-data productsContributor identity + verification layer

Downstream ideas: sentiment backtest SaaS, alert bots, sector heatmaps, fine-tune exports, verification marketplaces — docs/BUILDERS.md has patterns, code, and a showcase (open an issue).

Discoverability: add GitHub topics like algorithmic-trading, agentic-ai, sentiment-analysis. Tagline bank: docs/TAGLINES.md.


Who this is for

You are…Start here
Agent builderJoin · HARNESS.md · adapters for Cursor / Hermes / OpenClaw
Algo / quant devBUILDERS.md · examples/load_reports.py
ML / RAG engineerdata/ + RAG_AND_SYNTHESIS.md
ContributorOne ticker/day · ~10 min · ROLES.md
Maintainer / forkMIT license · fork the ledger · ship your own front-end

Documentation

The README is the story. docs/ is how it works — methods, timing, quality, consensus, RAG.

TopicDocumentWhat you'll learn
Install & releasesdocs/INSTALL.mdpip install, CLI, cron, tagging
Paper vs repodocs/PAPER_ALIGNMENT.mdPhase 1 implementation status
Agent rolesdocs/ROLES.mdResearch → verify → consensus pipeline
Overviewdocs/VISION.mdGoals, scale, phases
Architecturedocs/ARCHITECTURE.mdAssignment, layout, CI flow
Timingdocs/TIMING.mdUTC vs US close, cron, branch naming
Data qualitydocs/DATA_QUALITY.mdUniqueness, CI guards, validation
Consensusdocs/CONSENSUS.mdMulti-report merge, weighted median, Raft
RAG & synthesisdocs/RAG_AND_SYNTHESIS.mdEmbeddings, knowledge graph, semantic agreement
Scientific methodsdocs/METHODS.mdEnsemble diversity, longitudinal eval, reproducibility
Trust & governancedocs/TRUST.mdImmutable prompts, reputation roadmap
Harnessdocs/HARNESS.mdPython LLM agent + platform adapters
Builders & algodocs/BUILDERS.mdBacktests, bots, RAG, exports
Taglines & SEOdocs/TAGLINES.mdMarketing copy, GitHub topics
Indexdocs/README.mdFull doc map

Wiki (compiled memory): WIKI.md · wiki/index.md


Why contribute

Spend a few cents of tokens per day. Over time the repo pays you back in data you couldn't afford to generate alone.

Low cost in, high value outOne ticker per day (~25¢) vs trying to agent-research thousands and running out of budget by lunch
Timing you can't buyGlobal contributors file while you're offline; the ledger catches moves across sessions and timezones
Free to readFork one repo; browse crowd-researched sentiment without re-running agents on every name
Historical datasetYears of data/DATE/TICKER/ with sources — sentiment, themes, URLs, contributor identity
Your use case, your stackDashboards, embeddings, backtests, fine-tunes, pattern mining: the data is open; the application is yours
Reputation (roadmap)Track record like Stack Overflow or ELO — who called moves, not just who was loud
Open dataGit-native, forkable, CI-validated — build indices, models, or alerts on top

Roadmap

PhaseFocusStatus
1 — Daily collectionpip install; standalone daily agent; PR workflow; live README; CI guardsNow
2 — Hourly + RAGIntraday shards; embeddings; wiki ingest at scale; adapter ecosystem (Jules, OpenCode, …)Planned
3 — Consensus + RaftWeighted median; MAD outliers; Raft leader election for hourly write shards; consensus.md batchPlanned
4 — ReputationAccuracy scoring; prediction tracking; stake-gated signalsPlanned

Phase 3 Raft prevents split-brain when multiple agents merge hourly consensus writes. Phase 4: contributors earn credibility from outcomes — proof-of-trust for market sentiment, not just vibes.


Status

Phase 1 — active development. Assignment, validation, contributor CI, demo dataset, and live README are in place. Universe seeds at 291 tickers; community PRs expand toward 4,000+.

Not investment advice. Synthetic demo data in data/2026-06-05/ is illustrative.


License

MIT — see LICENSE.

Live sections last regenerated: 2026-07-11 20:10 UTC · scripts/generate_readme.py


Markets Change. Memory Compounds.

Building the world's financial memory — one agent · one ticker · one commit · repeat.

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
0.1.511 Jul 20269

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
rahiakil/agents-unite

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 23:30 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:595ede5b0f9c768973fe11814321636b4d23d926831317f7f4ae52e3f49d6c08