Trending hip-hop artist momentum scores across four cultural dimensions.
The server computes trending hip-hop artist momentum scores across four cultural dimensions. It exposes data and insights related to artist momentum, enabling analysis and visualization through its tool set.
π οΈ Key Features
toolCount: 3
Readme excerpt provided to guide integration and understanding
Centered banner imagery referenced for UI contexts
Quickstart and documentation links available in readme excerpt
π Use Cases
Track four cultural dimensions of artist momentum over time
Integrate momentum scores into dashboards for media or label analytics
Benchmark artists against peers using the supplied data
β‘ Developer Benefits
Clear quickstart guidance and docs references
GitHub and external links for collaboration
Lightweight data model suitable for fast rendering
β οΈ Limitations
Readme excerpt shows truncated links and content in the sample data
Tool count and exact schema may vary; rely on the provided readme for integration specifics
Captured live from the server via tools/list.
get_trending_artists
Returns the current list of trending hip-hop and rap artists ranked by LabelHead's composite momentum score. Each artist is scored across three dimensions: Acceleration (30-day streaming/social velocity), Cultural Gravity (press velocity, playlist adds, sync placements), and Longevity (catalog depth and retention). Use this to identify which artists are building genuine momentum right now.
Returns a detailed explanation of LabelHead's three-dimensional artist scoring methodology. Use this when you need to understand how composite scores are calculated, what each dimension measures, and how to interpret momentum labels.
Look up the current momentum score and signals for a specific artist by name. Returns the full three-dimensional score breakdown and notable signals driving their momentum.
Parameters1
artist_name
string
required
Artist name to look up (e.g. 'Doechii', 'Kendrick Lamar', 'GloRilla')
Paperclip is the app people use to manage AI agents for work.
Open-source orchestration for teams of AI agents.
If OpenClaw is an employee, Paperclip is the company.
Paperclip is a Node.js server and React UI that orchestrates a team of AI agents to run a business. Bring your own agents, assign goals, and track work and costs from one dashboard.
It looks like a task manager. Under the hood: org charts, budgets, governance, goal alignment, and agent coordination.
Manage business goals, not pull requests.
Step
Example
01
Define the goal
"Build the #1 AI note-taking app to $1M MRR."
02
Hire the team
CEO, CTO, engineers, designers, marketers β any bot, any provider.
03
Approve and run
Review strategy. Set budgets. Hit go. Monitor from the dashboard.
Works with
OpenClaw
Claude Code
Codex
Cursor
Bash
HTTP
If it can receive a heartbeat, it's hired.
Paperclip is right for you if
β You want to build autonomous AI companies
β You coordinate many different agents (OpenClaw, Codex, Claude, Cursor) toward a common goal
β You have 20 simultaneous Claude Code terminals open and lose track of what everyone is doing
β You want agents running autonomously 24/7, but still want to audit work and chime in when needed
β You want to monitor costs and enforce budgets
β You want a process for managing agents that feels like using a task manager
β You want to manage your autonomous businesses from your phone
The four pillars
Four things have to work for an organization of AI agents to actually produce: the tasks, the org, the training, and the infrastructure. Paperclip is built around exactly those four pillars.
Pillar
Built for
What it covers
Agentic Task Manager β Declare intent. Agents work. You verify the output.
Identity & Access β Two deployment modes (trusted local or authenticated), board users, agent API keys, short-lived run JWTs, company memberships, invite flows, and OpenClaw onboarding. Every mutating request is traced to an actor.
Org Chart & Agents β Agents have roles, titles, reporting lines, permissions, and budgets. Adapter examples match the diagram: Claude Code, Codex, CLI agents such as Cursor/Gemini/bash, HTTP/webhook bots such as OpenClaw, and external adapter plugins. If it can receive a heartbeat, it's hired.
Work & Task System β Issues carry company/project/goal/parent links, atomic checkout with execution locks, first-class blocker dependencies, comments, documents, attachments, work products, labels, and inbox state. No double-work, no lost context.
Heartbeat Execution β DB-backed wakeup queue with coalescing, budget checks, workspace resolution, secret injection, skill loading, and adapter invocation. Runs produce structured logs, cost events, session state, and audit trails. Recovery handles orphaned runs automatically.
Workspaces & Runtime β Project workspaces, isolated execution workspaces (git worktrees, operator branches), and runtime services (dev servers, preview URLs). Agents work in the right directory with the right context every time.
Governance & Approvals β Board approval workflows, execution policies with review/approval stages, decision tracking, budget hard-stops, agent pause/resume/terminate, and full audit logging. Nothing ships without your sign-off.
Budget & Cost Control β Token and cost tracking by company, agent, project, goal, issue, provider, and model. Scoped budget policies with warning thresholds and hard stops. Overspend pauses agents and cancels queued work automatically.
Routines & Schedules β Recurring tasks with cron, webhook, and API triggers. Concurrency and catch-up policies. Each routine execution creates a tracked issue and wakes the assigned agent β no manual kick-offs needed.
Plugins β Instance-wide plugin system with out-of-process workers, capability-gated host services, job scheduling, tool exposure, and UI contributions. Extend Paperclip without forking it.
Secrets & Storage β Instance and company secrets, encrypted local storage, provider-backed object storage, attachments, and work products. Sensitive values stay out of prompts unless a scoped run explicitly needs them.
Activity & Events β Mutating actions, heartbeat state changes, cost events, approvals, comments, and work products are recorded as durable activity so operators can audit what happened and why.
Company Portability β Export and import entire organizations β agents, skills, projects, routines, and issues β with secret scrubbing and collision handling. One deployment, many companies, complete data isolation.
What Paperclip is not
Not a chatbot.
Agents have jobs, not chat windows.
Not an agent framework.
We don't tell you how to build agents. We tell you how to run a company made of them.
Not a workflow builder.
No drag-and-drop pipelines. Paperclip models companies β with org charts, goals, budgets, and governance.
Not a prompt manager.
Agents bring their own prompts, models, and runtimes. Paperclip manages the organization they work in.
Not a single-agent tool.
This is for teams. If you have one agent, you probably don't need Paperclip. If you have twenty β you definitely do.
Not a code review tool.
Paperclip orchestrates work, not pull requests. Bring your own review process.
Quickstart
Open source. Self-hosted. No Paperclip account required.
The installer ensures Node.js 20 or newer is available, installs a managed
Paperclip CLI under ~/.paperclip/cli, and starts interactive onboarding. It
can also install Paperclip as a background service on supported Linux and
macOS systems. The checksum detects transfer or publishing mistakes, but it is
served from the same origin as the script; use a release-tag or commit-pinned
GitHub copy when you need an independently hosted source.
The piped form requires supported Node.js, npm, and npx to already be present.
If Node.js bootstrap is required, download and review install.sh before
running it so no privileged dependency-install command is accepted through a
pipe.
To try Paperclip without installing anything permanently:
If this fails with an E404 for paperclipai (or similar) and you use a private npm registry (for example GitHub Packages) via a global ~/.npmrc, npx may be resolving paperclipai against that private registry instead of the public npm registry.
Diagnostic:
bash
npm config get registry
Workaround (cross-platform; force the public npm registry for this command):
That quickstart path now defaults to trusted local loopback mode for the fastest first run. To start in authenticated/private mode instead, choose a bind preset explicitly:
If you already have Paperclip configured, rerunning onboard keeps the existing config in place. Use paperclipai configure to edit settings.
See doc/INSTALLING.md for pinned versions, canary and
git-ref installs, updates, rollback, service management, and uninstalling.
Or manually:
bash
git clone https://github.com/paperclipai/paperclip.git
cd paperclip
pnpm install
pnpm dev
This starts the API server at http://localhost:3100. An embedded PostgreSQL database is created automatically β no setup required.
Requirements: Node.js 20+, pnpm 9.15+
FAQ
What does a typical setup look like?
Locally, a single Node.js process manages an embedded Postgres and local file storage. For production, point it at your own Postgres and deploy however you like. Configure projects, agents, and goals β the agents take care of the rest.
If you're a solo entrepreneur you can use Tailscale to access Paperclip on the go. Then later you can deploy to e.g. Vercel when you need it.
Can I run multiple companies?
Yes. A single deployment can run an unlimited number of companies with complete data isolation.
How is Paperclip different from agents like OpenClaw or Claude Code?
Paperclip uses those agents. It orchestrates them into a company β with org charts, budgets, goals, governance, and accountability.
Why should I use Paperclip instead of just pointing my OpenClaw to Asana or Trello?
Agent orchestration has subtleties in how you coordinate who has work checked out, how to maintain sessions, monitoring costs, establishing governance - Paperclip does this for you.
(Bring-your-own-ticket-system is on the Roadmap)
Do agents run continuously?
By default, agents run on scheduled heartbeats and event-based triggers (task assignment, @-mentions). You can also hook in continuous agents like OpenClaw. You bring your agent and Paperclip coordinates.
Development
bash
pnpm dev # Full dev (API + UI, watch mode)
pnpm dev:once # Full dev without file watching
pnpm dev:server # Server only
pnpm dev:mobile # Serve prebuilt UI on :3101 for phones/tablets (proxies /api β :3100)
pnpm dev:both # Run `pnpm dev` and `pnpm dev:mobile` together
pnpm build # Build all
pnpm typecheck # Type checking
pnpm test# Cheap default test run (Vitest only)
pnpm test:watch # Vitest watch mode
pnpm test:e2e # Playwright browser suite
pnpm db:generate # Generate DB migration
pnpm db:migrate # Apply migrations
pnpm test does not run Playwright. Browser suites stay separate and are typically run only when working on those flows or in CI.
Paperclip ships with opt-in OpenTelemetry auto-instrumentation for the server (traces only). It activates when OTEL_EXPORTER_OTLP_ENDPOINT is set and supports grpc, http/protobuf, and http/json via the standard OTEL_EXPORTER_OTLP_PROTOCOL env var. The @opentelemetry/* packages are optional peer dependencies β install them only if you want tracing. See doc/observability.md for install commands and the full env-var reference.
Telemetry
Paperclip collects anonymous usage telemetry to help us understand how the product is used and improve it. No personal information, issue content, prompts, file paths, or secrets are ever collected. Private repository references are hashed with a per-install salt before being sent.
Contributors changing emitted telemetry events should follow the Telemetry Data Contract.
For proposed first-party events that are not in the generated contract yet, follow Telemetry Workflow.
Telemetry is enabled by default and can be disabled with any of the following:
Method
How
Environment variable
PAPERCLIP_TELEMETRY_DISABLED=1
Standard convention
DO_NOT_TRACK=1
CI environments
Automatically disabled when CI=true
Config file
Set telemetry.enabled: false in your Paperclip config