Earn Credits by Sharing Compute

Your machine sits idle most of the day. The Slopshop Credit Exchange lets you contribute those idle CPU cycles and earn credits you can spend on any of the 82 categories of tools. A two-sided marketplace for AI compute.

How the credit exchange works

The exchange is simple: contributors run a lightweight daemon that accepts compute jobs when the machine is idle. Each completed job earns credits. Those credits are deposited directly into your Slopshop account and can be spent on any API call, just like purchased credits.

Jobs are sandboxed, verified, and time-limited. Your machine only processes Slopshop compute handlers -- the same deterministic, pure-compute functions that run on the main platform. No arbitrary code execution, no network access from jobs, no data exfiltration risk.

What you can earn

Earnings depend on your hardware, uptime, and current demand on the exchange. A typical developer laptop earning during work hours contributes enough to cover moderate API usage. A dedicated server running 24/7 earns enough to never buy credits again.

Getting started as a contributor

Install the Slopshop CLI and run the exchange daemon. It automatically detects idle periods and adjusts resource usage to avoid impacting your work. You set the limits -- maximum CPU percentage, active hours, and whether to pause during user activity.

• npx slopshop exchange start -- begin contributing compute
• npx slopshop exchange status -- check earnings and job stats
• npx slopshop exchange stop -- pause contributions

Credits earned through the exchange are identical to purchased credits. They never expire and work on every API endpoint. See pricing for credit values.

Why this model works

Most compute on the Slopshop platform is embarrassingly parallel -- text hashing, JSON parsing, math operations, schema validation. These tasks are tiny (sub-50ms) and can be distributed across contributor machines with negligible coordination overhead. The exchange pools idle resources from the community to serve peak demand without over-provisioning servers.

For contributors, it is free money. For the platform, it is elastic scaling without cloud bills. For everyone, it means lower prices and better availability.

Security and sandboxing

Every exchange job runs in a sandboxed environment with no filesystem access, no network access, and strict time limits. Jobs execute the same deterministic compute handlers that run on the main platform -- there is no arbitrary code execution. All inputs and outputs are validated against schemas before and after processing. Read the full security model.