WaitSpin public contract

WaitSpin Terms

These terms describe the current WaitSpin product contract and the disclosures for the public paid marketplace surface.

Last updated: June 17, 2026. The public launch surface is CLI, REST API, verified user earning surfaces for VS Code, Claude Code, MiMo Code, OpenCode, and Grok Code CLI, public market, and guarded wallet/ledger/Connect/payout routes.

Service Scope

WaitSpin is an independent ad marketplace for sponsored messages in verified developer wait-state surfaces. The current public contract is API-first and documents the verified VS Code Activity Bar/status-bar extension, Claude Code statusline command, MiMo Code shell hook, OpenCode TUI plugin slot, Grok Code CLI integration, and install-all orchestration for detected supported targets. Wallet visibility, ledger history, Stripe Connect onboarding, payout dry-run, and guarded payout execution are documented public publisher money surfaces in these terms and in /docs. Live transfers execute only when payout policy eligibility checks pass; WaitSpin does not guarantee that any balance is immediately withdrawable. Native spinner patches, account-credit redemption, and self-serve cash refunds are not available yet.

Accounts And API Keys

Accounts are created through email verification. API keys are bearer credentials and must be kept secret, rotated when exposed, and used only with scopes granted to the account. We may reject temporary email providers, rate-limit requests, revoke keys, suspend accounts, or disable serving when abuse, security risk, quota evasion, or legal compliance requires it.

Advertiser Blocks

Advertisers create campaign drafts with a short ad line, an HTTPS destination URL, block count, and price per block. Destinations are validated to reduce SSRF and unsafe URL risk, but advertisers remain responsible for destination content, claims, tracking, and legal compliance. WaitSpin does not guarantee impressions, conversions, ranking, traffic quality, or continuous availability.

Refunds, Credits, And Disputes

Unused prepaid block outcomes are handled only through support review until a visible credit ledger and redemption flow are shipped. The automated account-credit balance, redemption flow, and cash refund request flow are public-launch blockers and are not available as self-serve features yet. Stripe refunds or disputes may pause future delivery and may reverse or hold unpaid user balances tied to affected delivery.

Users And Revenue Split

The current revenue model uses a 60 percent user share and a 40 percent platform share on billed impression delivery. Stripe processing fees are absorbed from the platform share unless the payment policy changes. Wallet balance, ledger entries, Stripe Connect onboarding, payout dry-run, and guarded payout execution are the documented publisher money surfaces.

Wallet readout

Read the wallet before you wait for payout.

The extension and CLI show the same money states. Choose a surface, then select a row to see what it means, whether it blocks payout, and what to do next.

SPONSOR / WALLETVS Code Activity Bar

No eligible sponsor right now. The plugin keeps polling without showing house ads.

wallet status balance.availableMicroUnits

Available

Matured balance that is not held and not already reserved.

Means
This is the part of your 60 percent publisher share that has finished the 72-hour maturity window.
Payout impact
Available money can be paid only when it reaches EUR 10.00, the payout account is ready, cadence allows a run, and there are no active holds.
Next action
If this is zero, check Pending maturity and Recent ledger first; it usually means earnings are still aging or no billable impressions landed yet.
  1. 01Impression credited
  2. 02Pending maturity
  3. 03Available
  4. 04Payout

New eligible publisher accounts start at trust level 1/10 and can receive paid sponsored inventory immediately when campaigns are available. Each clean 24-hour period of billable activity can raise the level by 1, up to level 10/10. While the account is warming up, daily exposure limits scale with level: at level 1, one account can receive up to 3% of a campaign's effective daily inventory and one install up to 0.5%; at level 10, those caps rise to 30% and 5%. Risk signals such as refund/dispute pressure, invalid receipts, velocity limits, or cap pressure can reduce the effective level or pause paid supply for review.

Earnings first enter a maturing balance and become withdrawable only after the 72-hour maturity window completes. Trust warmup controls how much paid inventory you can receive; it does not shorten payout maturity. Minimum payout and cadence rules apply before transfers, and live payouts execute only when all payout policy eligibility checks pass, including Connect setup, maturity, minimum balance, cadence, and any active payout hold, fraud review, or compliance block. Full level tables and limits are documented at User levels and limits.

Fraud And Invalid Traffic

Billable impressions require the server-side minimum visibility window and an active user install, but public paid traffic also requires fraud controls, scoped extension credentials, alerting, and drill evidence. We may void, reverse, hold, or refuse payment for scripted traffic, self-dealing, false visibility, unauthorized extensions, rate-limit evasion, bot traffic, or other invalid activity.

Security And Non-Affiliation

WaitSpin uses host isolation, trusted-edge checks, rate limits, hashed API keys, and audit logging. You must not bypass security controls, probe unauthorized routes, or publish credentials. WaitSpin is not affiliated with Anthropic, OpenAI, Microsoft, Visual Studio Code, Stripe, or any IDE vendor unless a separate written agreement says so.

Support And Current Docs

Public API and agent docs: /docs. For payouts, billing, installs, abuse, and account questions, use Support.