# Playmos

> Integrate payments and skill contests into games. Start on Base Sepolia with IAP: pay → verify on your backend → grant once. JavaScript examples target @playmos/sdk@0.3.20.

## Agent entry points

- [Agent integration workflow](https://test.playmos.io/docs/agents.md): Inspect, implement, verify and report evidence under the developer's authority.
- [Complete documentation](https://test.playmos.io/llms-full.txt): All guides and copyable examples in plain text.

## Skills

- [playmos-integrate](https://test.playmos.io/skills/playmos-integrate/SKILL.md): Integrate the Playmos SDK into a web, engine or backend project for in-app purchases and stablecoin commerce.
- [playmos-verify-payments](https://test.playmos.io/skills/playmos-verify-payments/SKILL.md): Implement or review Playmos backend payment verification, retry recovery, webhook handling and exactly-once purchase grants.
- [playmos-contests](https://test.playmos.io/skills/playmos-contests/SKILL.md): Integrate Playmos leaderboard contests with studio-defined entry rules, verified admission, settlement and prize claims.

## SDK

- [@playmos/sdk 0.3.20](https://www.npmjs.com/package/@playmos/sdk/v/0.3.20)
- [SDK reference](https://test.playmos.io/docs/reference.md)
- [Discovery manifest](https://test.playmos.io/.well-known/playmos.json): SDK metadata, skills and Markdown guides. This is a Playmos-specific manifest, not a universal agent protocol.

## Guides

- [Overview](https://test.playmos.io/docs/index.md): SDK, service and game integration. Choose your first path.
- [Your first payment](https://test.playmos.io/docs/quickstart.md): Install the JavaScript SDK. Pay and verify on Base Sepolia.
- [Integrate with an agent](https://test.playmos.io/docs/agents.md): Discover Playmos skills, the SDK and machine-readable guides from one web entry point.
- [Playground](https://test.playmos.io/docs/playground.md): Run the actual SDK offline or against the testnet sandbox.
- [Set up your studio](https://test.playmos.io/docs/studio-setup.md): Issue test keys, set the payout wallet and use studio-owned resources.
- [Payments & verification](https://test.playmos.io/docs/payments.md): Intent, pending, confirmed, failed. Idempotency and chain provenance.
- [Web integration](https://test.playmos.io/docs/browser.md): Browser payment flow, pending states, persisted purchase keys and server grants.
- [Webhooks](https://test.playmos.io/docs/webhooks.md): Signed raw body, delivery attempts, retries and deduplication.
- [Wallets & the Base app](https://test.playmos.io/docs/wallets.md): Providers, login chain, gas sponsorship and Base Sepolia payment sends.
- [Games & the storefront](https://test.playmos.io/docs/integration.md): Iframe stage, game kit, publisher workflow, release gates and metrics.
- [Skill contests](https://test.playmos.io/docs/contests.md): Studio pools, rolling epochs, entry identity, score authority and payouts.
- [Your studio pool](https://test.playmos.io/docs/pools.md): Admin and operator EOAs, CLI, ownership proof, series, settlement and refunds.
- [Payouts & withdrawals](https://test.playmos.io/docs/payouts.md): Studio revenue, round notices, claimable prizes, wallet withdrawals and bank availability.
- [Unity & game engines](https://test.playmos.io/docs/engines.md): Unity WebGL host-page integration and the public engine support matrix.
- [In-game economies](https://test.playmos.io/docs/economies.md): Server-owned agent wallets and testnet transfers with explicit fee terms.
- [HTTP payments](https://test.playmos.io/docs/x402.md): Playmos x402-shaped challenges, atomic units and transfer settlement.
- [API reference](https://test.playmos.io/docs/reference.md): Payments, rounds, epochs, webhook endpoints and health.
- [Languages & packages](https://test.playmos.io/docs/languages.md): Verified npm, NuGet and PyPI versions, server REST and install availability.
- [Keys, errors & environments](https://test.playmos.io/docs/security.md): Publishable and secret keys, test versus live, errors and recovery.
- [Troubleshooting](https://test.playmos.io/docs/troubleshooting.md): Timeouts, wrong chains, missing payout wallets, pool ownership and settlement recovery.

## Boundaries

Secret keys stay server-side. Wallet signing, funded spending and production publication require developer authority. Offline mocks are not testnet proof. Live keys and mainnet remain gated. These are documentation files, not an agent execution API.