# Peritus Games

> Peritus Games licenses asynchronous 1v1 skill games to platform operators. Your players play each other, on your platform. You keep your players and their funds. We deal the cards and score the match.

Asynchronous 1v1 skill games, licensed to platforms. Every page below is the same text the
site publishes — so this is the documentation, not a summary
of it.

## Documentation

- [Documentation](https://peritusgames.com/docs/index.md): What a Peritus game is, what crosses the boundary between your product and ours, and where to start integrating.
- [Quickstart](https://peritusgames.com/docs/quickstart.md): Six steps from an API key to a played match: mint a session, embed the frame, answer the handshake, read the authoritative result.
- [Keys and environments](https://peritusgames.com/docs/authentication.md): One API key authenticates your backend, and the key — not the URL — decides whether a call is test or live. What the two environments keep apart, and how rotation works.
- [Testing your integration](https://peritusgames.com/docs/testing.md): A test key plays the whole flow with no money in it. Decide a seated match on demand, the request shape, the three uncoded refusals, and what a green suite does and does not cover.
- [Identifying your player](https://peritusgames.com/docs/players.md): One server-to-server call before you show a game: who is playing, what they are called, and a short-lived token scoped to that player and that game.
- [Embedding a game](https://peritusgames.com/docs/embedding.md): The iframe, the registered origins that decide who may embed it, and every message the frame and your page exchange.
- [Paid matches](https://peritusgames.com/docs/paid-play.md): Seat one of your players in a match with a real prize: the tier ladder, the stake floor, the per-seat fee, and why a paid match seats two players of the same operator.
- [Match results](https://peritusgames.com/docs/results.md): The confirmed, server-computed outcome of every match your players play — the only signal you may move value on, and the four rules that decide whether your ledger is right.
- [Result webhooks](https://peritusgames.com/docs/webhooks.md): A signed nudge that says there is something new — go poll. It carries no result data and no cursor, so a delivery you miss costs you nothing. How to verify it, and when we stop sending.
- [Errors and limits](https://peritusgames.com/docs/errors.md): Every coded refusal, what causes it, what to do about it, and the rate limits your integration is budgeted against.
- [Versioning and change](https://peritusgames.com/docs/versioning.md): Every partner-facing response names the version that answered it. What may change without notice, the two things that keeps your client safe, and what needs a version bump and ninety days.
- [Managing your account](https://peritusgames.com/docs/portal.md): Keys, origins, colleagues, game licensing, usage and a six-month audit trail — all of it self-service in the partner portal.
- [Security model](https://peritusgames.com/docs/security.md): The design assumes the client is hostile — a player will read the network, edit the code and replay requests — and stays correct anyway. Here is how.
- [Who owns what](https://peritusgames.com/docs/responsibilities.md): Peritus supplies game software. Your users, and any money, stay with you. Where the line falls, stated plainly.

## The contract

- [partner-api-contract.md](https://peritusgames.com/partner-api-contract.md): The contract — the version policy and every reason code
- [partner-api-changelog.md](https://peritusgames.com/partner-api-changelog.md): The changelog — every breaking change and its notice period
- [partner-api-supported-versions.json](https://peritusgames.com/partner-api-supported-versions.json): The versions this build's resolver accepts today, generated from ApiVersion::SUPPORTED