Oscorp

Telegram + web growth copilot for X — your agent pays specialist APIs via x402 (TestNet USDC), Groq drafts posts, you approve every publish.

What it does

• Web app: wallet → policy → fund agent → run cycles → drafts queue with x402 receipts
• Telegram (recommended daily flow): /link → /run → Post on X · Regenerate · Skip
• x402: USDC micropayments to trend / hook providers (tx links on each draft)
• Regenerate: new copy from Groq only — no extra provider spend
• Research: Groq pre-cycle topics/angles from policy + memory (OSCORP_GROQ_RESEARCH_ENABLED)

Run a growth cycle (dev)

The backend calls x402-payer (:8110), which pays provider-services (:8101–:8103). If you only run the API + frontend, Start agent will fail with a connection error.

Option A — full stack (real x402 micropayments):

cd Oscorp
./scripts/dev-up.sh              # background: payer, providers, backend, telegram (if token set)
cd frontend && npm run dev       # web UI
./scripts/dev-down.sh            # stop background services

Or ./scripts/dev-stack.sh for manual per-terminal control.

Minimum for one cycle: x402-payer, trend-analyzer, hook-generator, backend, frontend.

Option B — stub providers (Groq draft only, no x402):

# backend/.env
OSCORP_PROVIDER_STUB=true

Restart uvicorn after changing .env.

Architecture (current default)

flowchart TB
    U[User]
    W[Web App]
    TG[Telegram Bot]
    B[Oscorp Backend]
    XP[x402 Payer]
    P1[Trend API]
    P2[Hook API]
    F[Facilitator]

    U --> W & TG
    TG --> B
    W --> B
    B --> XP --> P1 & P2
    P1 & P2 --> F

Loading

Agents / services in the stack

Component	Role
Oscorp backend	Orchestrator, wallet, policy, cycles
Groq	Draft copy + Telegram conversation
x402-payer	Signs USDC payments from agent wallet
Provider APIs	Trend, hook, thread specialists (paid via x402)
Telegram bot	User chat, memory, cycle triggers
Frontend	Wallet UI, onboarding, drafts

Research uses Groq only (no live X API). See docs/growth-research.md.

Quick start

# 1) Env
cd backend && cp .env.example .env   # add GROQ_API_KEY, TELEGRAM_BOT_TOKEN
cd ../frontend && cp .env.example .env

# 2) See scripts/dev-stack.sh — start payer, providers, backend, telegram, frontend
./scripts/dev-stack.sh

Open http://127.0.0.1:5173

Docs

• Env setup
• Telegram
• x402 on Algorand
• Architecture
• Growth research (Groq)

DoraHacks pitch

Problem: X growth needs paid specialist tools and a controlled agent budget — not fake analytics.

Solution: Oscorp runs a funded agent wallet, pays providers via x402 on Algorand, drafts on Groq, and keeps humans in the loop before posting.