# RemoteDraw > Your phone is the pen; a second screen is the paper. Guide discovery, verify live monetary costs, obtain scope and cost approval, then implement. If you were told to look at RemoteDraw and add it to a project: read the [agent skill](https://docs.remotedraw.com/docs/agent.md) first, inspect the project, then read only the two references that match the stack you find: the frontend kit's and the backend's session endpoint (`https://docs.remotedraw.com/docs/agent/references/sdks/.md`; the skill's routing table names them). Any other backend language uses the plain HTTP API. ## Read first - [Agent skill](https://docs.remotedraw.com/docs/agent.md): adaptive discovery, architecture trade-offs, live pricing checks, approval, rules and verification, with a table of which reference to read for each stack. Each SDK page is one skill reference at `https://docs.remotedraw.com/docs/agent/references/sdks/.md` (for example [React](https://docs.remotedraw.com/docs/agent/references/sdks/react.md)); [overview](https://docs.remotedraw.com/docs/agent/references/sdks/overview.md) has the support matrix and session endpoints. Read only the reference for the stack in use. - [API contract](https://docs.remotedraw.com/docs/api-reference.md): exact HTTP/realtime fields, errors, limits and lifecycle. - [Live pricing](https://docs.remotedraw.com/docs/pricing): public USD rates; check account availability before promising a feature. - [Wallet](https://dashboard.remotedraw.com/api/billing) and [usage](https://dashboard.remotedraw.com/api/usage): authenticated account availability, balance, reservations and spend. - [Free Standard](https://docs.remotedraw.com/docs/free-standard.md) and [AI wallet](https://docs.remotedraw.com/docs/ai-wallet.md): included native limits and separate AI quote/settlement contract. - [SDKs as Markdown](https://docs.remotedraw.com/docs/sdks.md): every kit's status, tier and install line; one file per kit with its facts, install, quickstart, configuration, errors, platform notes, testing, troubleshooting and evidence: [React](https://docs.remotedraw.com/docs/sdks/react.md), [Custom elements](https://docs.remotedraw.com/docs/sdks/elements.md), [JavaScript client](https://docs.remotedraw.com/docs/sdks/js-client.md), [Svelte](https://docs.remotedraw.com/docs/sdks/svelte.md), [Swift](https://docs.remotedraw.com/docs/sdks/swift.md), [React Native (iOS)](https://docs.remotedraw.com/docs/sdks/react-native.md), [Compose and Swing](https://docs.remotedraw.com/docs/sdks/kotlin.md), [Flutter](https://docs.remotedraw.com/docs/sdks/flutter.md), [.NET and WPF](https://docs.remotedraw.com/docs/sdks/dotnet.md), [WinUI 3](https://docs.remotedraw.com/docs/sdks/winui.md), [WKWebView](https://docs.remotedraw.com/docs/sdks/wkwebview.md), [WebView2](https://docs.remotedraw.com/docs/sdks/webview2.md), [WebKitGTK and Qt](https://docs.remotedraw.com/docs/sdks/linux-adapters.md), [Host recipes](https://docs.remotedraw.com/docs/sdks/recipes.md), [Node, Bun, Deno, Workers](https://docs.remotedraw.com/docs/sdks/server-js.md), [Python, Go, .NET, JVM](https://docs.remotedraw.com/docs/sdks/backends.md), [CLI](https://docs.remotedraw.com/docs/sdks/cli.md). - [Get started](https://docs.remotedraw.com/docs), [API guide](https://docs.remotedraw.com/docs/api), [SDKs](https://docs.remotedraw.com/docs/sdks), [App help](https://docs.remotedraw.com/docs/app), [Legal](https://docs.remotedraw.com/docs/legal). The Markdown URLs need no account or CLI installation. Install the skill with `npx @remotedraw/cli@latest agent --path .agents/skills/remotedraw` (Codex/Cursor) or `--path .claude/skills/remotedraw` (Claude Code) when package execution is authorized. Check installed SDK versions/exports against the current contract. ## Discover the right solution Use decisions already supplied. For experts, confirm only missing consequential details and prepare a priced proposal. For newcomers, explain the two-device model, offer relevant examples, then ask a few questions at a time: 1. Which existing screen should receive ink, who holds the phone, and what should Submit save or trigger? 2. Must the phone see a native ground, an occasional image, or exact changing receiver pixels? 3. Which frontend/backend, authentication, devices, data-retention policy and design system already exist? 4. Which tools, materials/textures, attachments, AI actions and pairing customization are wanted? 5. What session volume/duration, image byte sizes/replacements/downloads, AI job counts, test budget, per-session ceiling and monthly budget should the estimate cover? Resolve architecture first. Present viable options with behavior, effort, compatibility, privacy and cost trade-offs, recommend a direction, and ask the owner to choose before committing. For example: existing backend versus serverless backend; hosted sender versus custom iOS/web; native map versus static export versus streaming. A mode named native does not require a native app. ## Compare rendering modes - **Native:** phone renders its own board/field/basemap. It does not automatically reproduce the receiver's content. Simplest infrastructure; eligible ordinary drawing can use Free Standard. - **Static:** phone displays one published PNG/JPEG/WebP. The host creates the raster; no automatic component/PDF rasterizer ships. Current web and iOS source render static images and replacements; verify deployed sender/installed SDK support. Same paid time rate as native, with hosted uploads, retention and each delivery contributing to usage. At most 8 MiB and 4096 px per edge; two seconds between publishes. - **Streaming:** receiver publishes a canvas/image/video source and stays open; hosted web sender or a custom web pad consumes it. Higher time rate and relay/network work. SenderKit has no native streaming consumer. Hosted wallet streaming is gated; customer ICE requires a separately approved provider arrangement and connectivity proof. Agree whether failed video permits native/blank fallback or blocks the workflow. Static and enabled live view are mutually exclusive. Source support, hosted deployment, released package and installed app are separate evidence. Glass Overlay is parked; preview receiver SDKs and Aurora are not stable default alternatives. ## Price and approve before implementation Read live pricing and account availability each time, with date/source and taxes. Do not treat local source or cached examples as a live offer. If rates/account status cannot be checked, show a provisional estimate and obtain the missing information before paid implementation. Use **money per session, not credits**. Billing is in USD: the wallet is prepaid in USD ($5, $10, $25, $50 or $100 top-ups), prices exclude tax, and the card issuer may convert the charge. Do not quote prices in another currency. Baseline to verify (session tariff `hourly-usd-2026-09-19-combined-v1`): native/static $0.25/hour; streaming $0.50/hour, with hosted relay unavailable until enabled. Each paid session has a $0.10 minimum credited toward time, then prepaid started minutes. Idle time is not free. Set the approved `maxCostMinor` explicitly (whole USD cents, 10–100000; default 500 = $5). Drawing, edits and reads share one Combined Allowance per session hour; work over it is refused with no charge (no automatic overage) and it resets each session hour. Hosted media is not part of the allowance: it is charged separately per upload ticket ($0.0001), completed upload ($0.0002 + $0.05/GB) and each delivery ($0.0001 + $0.20/GB), each × 120/85, within the cap. The cap includes session/media usage, including retained downloads after End, but excludes separate AI reservations. It is not a monthly account cap. Explain each selected feature: standard tools and QR/UI components have no separate surcharge found, but generate normal session usage; custom designs add implementation effort. 2.5D physical materials (`experimental-3d`) add $0.05/hour from first material draft/commit onward; returning to standard ink does not disable the premium. “2.5T” is not an API field—clarify whether 2.5D is meant. Do not invent separate texture prices. Hosted image size, upload/replacement count, storage/retention and every download affect resource usage; hosted media is charged per operation on top of time (not covered by it), so quote it separately from time and drawing/reads. Customer-hosted images, map services and custom capture infrastructure have separate provider costs. Retention is at most 30 days. Free Standard must be selected explicitly with `billingMode: "free"`: 10 native sessions per tenant per UTC month, one active session/phone, up to 30 minutes/500 strokes plus shared capacity limits. No automatic wallet upgrade, hosted media, AI, streaming or physical materials. App Pro remains separate. AI requires backend `POST /v1/ai-actions/quote`, then approval of its currency/version/limits/maximum before creating the action with `maxCostMinor`. AI holds the full quote, settles within it and releases unused money; failures after dispatch can still cost money. A session needed to obtain a quote must first have its own approved test budget. There is no public general pricing/session-quote endpoint—do not invent one. Present receiver/sender/mode, content and components, behavior/fallbacks, implementation effort, dated per-session and monthly cost estimates, assumptions/external fees, explicit session/AI/test caps, availability and verification plan. **Obtain explicit approval of scope and costs before implementation**, including a $0 proposal. Respect approval already covering those exact decisions; silence or a funded wallet does not approve spending. ## Implement, communicate and verify 1. Use the approved SDK/backend; keep `rd_sk_` server-side and `rd_cli_` in account configuration. Authorize tenant/session access. Public clients receive scoped session tokens only. 2. Create sessions from explicit intent with duplicate-request protection. Session creation consumes funds or free allowance and is retry-safe only with a `requestId` persisted once per logical create (same id + identical body replays the original session for 24 hours while it is active; `externalId` is not an idempotency key). CLI defaults must be checked against approved mode/caps before execution. 3. Explain meaningful component choices: “I’m using the standard QR with connection status as agreed; we can customize its branding/layout.” Obtain approval before new scope, behavior, customization or cost choices. Ordinary details already covered by approval need no repeat confirmation. 4. Hosted sender, full-screen SenderKit and custom SDK-based sender are distinct choices. The standard RemoteDraw QR does not become a customer's app Universal Link just by restyling it. Hosted material/attach controls are not a feature-consent gate; resolve restrictions with the owner before shipping a workflow that excludes them. 5. Implement image publishing/rendering or approved streaming, ink, editing, error/expiry/presence/reconnect, Submit and explicit End. Current SDKs use counted reads and conditional revision checks for wallet/free sessions; do not bypass metering with direct payload subscriptions. 6. Verify phone-to-receiver landmark alignment, static replacement, streaming fallback, rotation, undo, reconnect, submit, end, expiry and billing limits within the approved test budget. Free sessions allow the original sender-token reconnect, not replacement by another sender token. 7. Report implemented scope, actual usage and outstanding AI holds versus estimates, device-tested and untested paths. Never raise limits, top up, change mode or retry a paid AI job without existing approval covering it. No native Android sender SDK, desktop sender, arbitrary component-capture service, `Idempotency-Key` header (session-create idempotency is the `requestId` body field) or AI completion webhook. RemoteDraw is not an electronic-signature compliance product.