This guide documents the full crypto-vision repository structure and how the major projects relate to each other.
crypto-vision is a multi-project TypeScript monorepo-style workspace containing:
- A root API service (Hono + TypeScript) for crypto intelligence and AI endpoints
- Multiple app surfaces under
apps/(dashboard,news,video) - Reusable and standalone packages under
packages/ - Infrastructure-as-code and deployment resources under
infra/ - Prompt and agent assets under
prompts/andagents/ - Multi-layer test suites under
tests/
crypto-vision/
├── src/ # Root API service implementation
├── tests/ # Root service tests (e2e, integration, fuzz, load)
├── apps/
│ ├── dashboard/ # Next.js dashboard product
│ ├── news/ # Next.js news-focused product
│ └── video/ # Remotion video project
├── packages/
│ ├── agent-runtime/ # Agent runtime package
│ ├── binance-mcp/ # Binance MCP server package
│ ├── bnbchain-mcp/ # BNB Chain MCP package
│ ├── market-data/ # Market data package
│ ├── mcp-server/ # Main MCP server package
│ ├── pump-agent-swarm/ # Pump.fun swarm orchestration package
│ ├── sweep/ # Sweep protocol/contracts + frontend
│ └── ucai/ # Universal Contract AI Interface package
├── infra/ # Deployment and cloud infra resources
├── agents/ # Agent catalog, templates, docs, locales, prompts
├── prompts/ # System prompts + swarm prompt packs
├── docs/ # Root operational and architecture docs
└── scripts/ # Data export/import and helper scripts
The root service is the primary backend API and includes:
- Market endpoints
- DeFi endpoints
- News endpoints
- On-chain endpoints
- AI endpoints with multi-provider fallback
- Worker/sources pipelines for upstream ingestion
Primary entrypoint:
src/index.ts
Primary API contract:
openapi.yaml
Related documentation:
- Root README:
README.md - Performance guide:
docs/PERFORMANCE.md - Self-hosting guide:
docs/SELF_HOSTING.md
A Next.js dashboard application with extensive UI, SDK, integrations, and tooling assets.
Start here:
apps/dashboard/README.mdapps/dashboard/docs/README.md
A Next.js news-first application/API distribution with localization and extensive docs/examples.
Start here:
apps/news/README.mdapps/news/docs/README.md
Remotion project for rendering crypto/agent-themed videos.
Start here:
apps/video/package.jsonscripts (studio,render,render:gif)
Top-level package index:
packages/agent-runtime/README.mdpackages/binance-mcp/README.mdpackages/bnbchain-mcp/README.mdpackages/market-data/README.mdpackages/mcp-server/README.md(and module READMEs)packages/pump-agent-swarm/README.mdpackages/sweep/README.mdpackages/ucai/README.md
These packages are intentionally heterogeneous: some are libraries, some are servers, and some are full product/workspace modules.
Infrastructure resources include:
- Terraform resources (
infra/terraform/) - Kubernetes manifests (
infra/k8s/) - BigQuery, Pub/Sub, Scheduler assets
- Lifecycle scripts (
infra/setup.sh,infra/teardown.sh)
Start here:
infra/README.md
Contains:
- Agent templates and manifest
- Agent documentation (
agents/docs/) - Localization assets (
agents/locales/) - Prompt bundles (
agents/prompts/) - Schema and scripts for generation and splitting
Contains:
- End-to-end implementation prompts (
01...12) - Swarm-focused prompt series (
prompts/swarm/)
Root test coverage is organized by testing mode:
tests/routes/for route-level teststests/integration/for integration flow coveragetests/e2e/for end-to-end behaviortests/fuzz/andtests/load/for robustness/performance validationtests/benchmarks/for benchmark scenarios
Root project scripts are defined in package.json:
npm run devnpm run buildnpm startnpm run lintnpm run typechecknpm testnpm run test:e2e
Additional domain scripts include training and data export/import flows.
See also: docs/DEVELOPER_WORKFLOW.md.
Do not commit generated build caches or local runtime artifacts.
At minimum, keep these ignored:
.next/.turbo/- build output folders (
dist/, localout/where applicable) - local env files (
.env*)
If a secret is accidentally committed:
- Revoke/rotate credential immediately.
- Rewrite history to remove the secret-bearing commit(s).
- Force-push cleaned history only after validating no secret blobs remain.
- Re-run push and confirm repository rule checks pass.
For new contributors:
- Read
README.mdfor root API setup. - Read this document to understand project boundaries.
- Read the specific app/package README for your target area.
- Run local checks (
lint,typecheck,test) before opening a PR.