SDK docs
Install & integrate on any platform. One Rust core, native everywhere.
Latest published SDK … — read it at runtime with version() (Kotlin/Swift), cr_version() (C ABI), or import { VERSION } (TV JS). Per-platform release details are on each tab.
Portal build 3.2.0 (2026-08-08·39ace81) — this site, not the SDK.
That's the only download you need for Electron / Node — one .zip with the SDK, the native core, a README.md, and an AGENTS.md for your AI coding assistant, all inside.
// npm i @cashraven/electron (or download the .zip — native core included)
const { CashRaven, showConsent } = require("@cashraven/electron");
const cr = new CashRaven({ developerKey: "<devKey>", uid: "user-123" });
if (await showConsent(cr, { parent: mainWindow })) cr.start(); // only after accept
// Renderer UI: attachIpc(cr) in main + the /preload bridge (window.cashRaven).
// REQUIRED: an opt-out control that calls cr.optOut();- • The consent screen is built into the SDK — render the SDK's copy; sharing starts only after the user agrees.
- • Add an opt-out control. Required for compliance approval.
- • Device is protected automatically: per-device bandwidth, data and CPU/RAM limits + local-network/sensitive-port blocking.
Every tab above is the same Cash Raven SDK — one Rust core, exposed for each language. Pick the tab for the language you build in and download that one .zip; you never combine two.
Each .zip also contains an AGENTS.md — drop it into your repo and your AI coding agent (Claude, Cursor…) integrates the SDK correctly on the first try. No separate download; it's already inside.
Do it in the Consent screen panel above — per app, no rebuild, and it applies on every platform you ship. Devices pick up a change on their next launch. You never hard-code colors or copy into your build.
- • Six colors — background, card, text, secondary text, accent, button label (#rrggbb).
- • Your own paragraphs, anywhere between ours, plus your app name and custom button labels.
- • The agreement's own wording and its links are Cash Raven's and are shown read-only. Need to change them for your app? Ask compliance — it is granted per app.
- • Your SDK reads the result automatically: consentScreen() (Android/Electron/C++/C#/Rust) or cr_client_consent_ui_text() (C ABI). Drive the paragraph and link lists off the count() call — we change how many there are without an SDK release.
You're paid per user per month, at a per-country rate — your rate card is on your dashboard, and it is quoted per month because that is the unit you compare networks on. The money is earned daily: every day one of your users qualifies, that day is worth the monthly rate divided by the days in that month, and the month is the sum of its days. A fleet that grows mid-month therefore earns the two halves added together, not the peak held for the whole month.
- • A user counts for a day once their device has been sharing for 60 minutes in that day (UTC). Time offline doesn't count toward it, and a device that comes and goes adds up across the day.
- • Below the bar a day is worth nothing; above it every qualifying day is worth the same, whether the device shared for an hour or for twenty-four.
- • Qualifying days are counted once per network connection — several devices on one home or office connection are one user, because that is what the network delivers.
- • All of it is visible as it accrues: your dashboard shows today's qualifying users alongside the month's total so far.
What developers ask before they integrate
How does Cash Raven monetize an app without ads?
Cash Raven's SDK relays a small, capped share of a consenting user's unused bandwidth for public web data collection, and pays the app's publisher for it. Users are never shown an ad and never see a slowdown — the SDK yields the moment the device needs its resources.
How much can a developer earn with Cash Raven?
Up to $0.40 per user per month. Earned daily — a user counts for a day once their device has been sharing for 60 minutes, and each qualifying day is worth one day's share of the monthly rate. A publisher whose users qualify 45,000 times across a 30-day month earns up to $600 that month. The full per-country rate card is in the dashboard after sign-up.
How is a month's earnings calculated?
Day by day. A user counts for a day once their device has been sharing for 60 minutes in that UTC day, and that day is worth the monthly rate divided by the number of days in the month; the month is the sum of its days. Users are counted once per network connection — so several devices on one home or office connection count as a single user. If 2,000 users qualify on days 1–15 and 1,000 on days 16–30 of a 30-day month, that is 45,000 user-days, and at the top rate 45,000 × ($0.40 ÷ 30) pays $600.
Do I need to talk to sales to start?
No. Sign up, add your app, and your first 100 devices go live immediately. Past 100 devices, new devices are refused until partnerships@cashraven.io sets custom pricing and compliance approves the build — usually within a business day.
Which platforms does the Cash Raven SDK support?
Electron and Node.js, Windows (cr_sdk.dll), macOS (universal dylib), Linux (libcr_sdk.so), Android including Android TV and Fire TV (an AAR via Gradle or Maven), and Samsung Tizen (JavaScript, beta). Go, Python, Swift, C, C++, C# and Rust bind through the stable C ABI. If your platform or language is missing, we ship a binding in about a week.
What do users consent to, and can they opt out?
Opt-in is the only code path that enables sharing. Every app must ship a visible opt-out control, and compliance verifies it in the submitted build before the device cap lifts. The SDK also opts a device out on its own when a protection limit — a data cap, or sustained load on the device — is reached.
What is the bandwidth actually used for?
Public web data collection: price and availability monitoring, flight and hotel search, SEO and ad verification, market research, and AI training data. A permanent, growing blacklist blocks .gov, .edu, banks and financial institutions, card processors, login endpoints, sensitive APIs, any reported-abuse domain, and users' own local networks.
How does Cash Raven protect a user's device?
Named guarantees enforced inside the compiled Rust core, with no API to disable them: a bandwidth ceiling, daily and monthly data caps (tighter on mobile data than WiFi), a CPU and RAM budget, a port and network denylist, and no access to anything personal — only the IP address and the bandwidth. The relay is a background task and yields to the app it lives in.