WaitSpin Terms

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, and install-all orchestration for detected supported targets. Native spinner patches, account-credit redemption, self-serve cash refunds, and ungated live payout promises are not public paid-launch capabilities. Guarded wallet, ledger, Connect, and payout commands remain policy-gated before any live payout execution.

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.

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.

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 publisher balances tied to affected delivery.

The current revenue model uses a 60 percent publisher 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, ledger, Stripe Connect onboarding, payout dry-run, guarded payout execution, minimum payout, and cadence controls are release-candidate surfaces. Public payout promises and live transfers remain gated until deployed E2E, legal approval, minimum/cadence policy approval, Stripe test-transfer proof, and explicit operator flags are complete.

Billable impressions require the server-side minimum visibility window and an active publisher install, but public paid traffic also requires fraud controls, scoped publisher 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.

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.

Current public API and agent docs are available at /docs. Product and billing questions should go through WaitSpin support once the product-specific support intake is published.