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, Antigravity CLI statusline command, GitHub Copilot CLI statusline command, MiMo Code shell hook, OpenCode TUI plugin slot, Grok Code CLI integration, Qoder CLI UserPromptSubmit/Stop hooks, and install-all orchestration for detected supported targets. Advertiser block purchases can be paid through Stripe Checkout or the crypto MPP API rail backed by Stripe/Tempo stablecoin payment. 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. MPP is an advertiser pay-in rail only: WaitSpin does not custody crypto, store private keys, collect raw wallet destinations, or offer direct cryptocurrency publisher withdrawals in the current EU product. Live transfers execute only when payout policy eligibility checks pass; WaitSpin does not guarantee that any balance is immediately withdrawable. Advertiser block purchases support Stripe Checkout and the production Stripe/Tempo stablecoin MPP pay-in rail. Native spinner patches, account-credit redemption, and self-serve cash refunds are not available yet.

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. Blocks activate only after the relevant Stripe payment is confirmed: Checkout through the existing Checkout/webhook path, or crypto MPP after the MPP credential verifies and Stripe reports the crypto PaymentIntent as succeeded. Destinations are validated to reduce SSRF and unsafe URL risk, but advertisers remain responsible for all advertising text, promoted names, brands, destination links, destination content, claims, tracking, and legal compliance. Illegal, abusive, deceptive, infringing, or prohibited promotion may result in permanent account blocking without restoration or refund, and WaitSpin may disclose available account, campaign, payment, network, and audit data to law enforcement when required or appropriate. WaitSpin does not guarantee impressions, conversions, ranking, traffic quality, or continuous availability.

Advertiser block purchases can be paid through Stripe Checkout or through the production Stripe/Tempo stablecoin MPP endpoint at /v1/blocks/mpp-crypto. The stablecoin MPP rail is an inbound pay-in rail only: WaitSpin verifies the MPP credential, verifies the bound Stripe PaymentIntent reached succeeded, and then activates blocks through the canonical block purchase path. WaitSpin does not provide crypto payouts, hold customer crypto, store raw wallet addresses or private keys, or operate a treasury crypto balance.

Publisher payouts remain standard fiat payouts through Stripe-managed methods, including bank payouts, SEPA, or Instant Payouts where available and allowed by payout policy. WaitSpin does not offer direct EU crypto publisher payouts.

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. Crypto MPP pay-ins are processed by Stripe/Tempo; any supported refund, dispute, or reversal path is handled through the Stripe-managed payment rail rather than a WaitSpin wallet or direct crypto custody flow.

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 fiat payout execution are the documented publisher money surfaces. Publisher payouts do not use the crypto MPP block purchase rail.

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.

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.

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.

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