Social matchmaking API
Combine player preferences, availability, play style, role, region, and game context to recommend compatible squads.
Recruiting multiplayer studio design partners
Social matchmaking APIs for multiplayer games.
Add compatibility-based squad formation, repeat-play learning, and community-health signals to the matchmaking systems your game already uses.
Developer preview in formation. Product workflow and API examples are illustrative.
Developer preview
POST
/v1/squads/recommend
role
rank
schedule
play_style
region
safety
Recommendation
Compatible squad
ready
Learning signal
Repeat session
observe
Company mission
Turn compatible players into safe, lasting communities.
We believe belonging should be part of game infrastructure: measurable, controllable, and designed into the player experience from day one.
The developer platform
Add the social layer your queue was never built to provide.
Squad lifecycle engine
Carry good matches beyond one lobby with repeat-play prompts, lightweight coordination, and persistent squad context.
Community health signals
Bring reporting, blocking, and behavior-aware eligibility into the decision layer that forms player groups.
Integration workflow
Connect once. Improve every squad decision.
Instrument your player ecosystem
Connect declared preferences and the game context you already own through an SDK or backend API.
Recommend compatible squads
Request explainable group recommendations tuned to your game mode, population, and community standards.
Learn from repeat play
Measure which groups choose to play again and use that feedback to improve future recommendations.
YOUR GAME
GAMERS FRAMEWORK API
BETTER GROUP EXPERIENCES
Use cases
Turn social fit into a product capability.
Strengthen social retention
Help players find people worth returning for instead of relying on a fresh random lobby every session.
Give new players a better first team
Form newcomer-friendly groups around shared intent, communication preferences, and availability.
Build balanced, compatible squads
Layer social fit and reliability onto the role, rank, region, and latency constraints your game already uses.
Build, bolt on, or integrate
Keep your core matchmaking. Add compatibility without rebuilding the stack.
Build internally
Strength: Maximum control over game-specific logic and data.
Tradeoff: Requires dedicated matchmaking, community, safety, analytics, and live-ops investment.
Community tools
Strength: Excellent for chat, voice, content, and broad community reach.
Tradeoff: Discovery happens outside the game and relationship signals remain fragmented.
Gamers Framework
Strength: A focused compatibility and squad layer designed to integrate with existing game systems.
Status: Currently recruiting a small group of studios to shape the developer preview.
Trust by design
Community health belongs in the matching decision.
Explicit data boundaries
Define the minimum player and game context used by each recommendation workflow.
Developer-controlled policy
Keep eligibility, blocking, reporting, and enforcement rules aligned with your game.
Auditable recommendations
Expose the factors behind a squad recommendation so teams can tune and govern the system.
Developer questions
Planning the first integrations.
What is the design partner program?
A small group of multiplayer studios will help shape the first integration, recommendation controls, and success metrics. Partners get direct product access and influence over the roadmap.
Does this replace our existing matchmaking?
No. Gamers Framework is designed to complement skill, latency, queue, and platform constraints with compatibility, repeat-play, and community-health signals.
What data does an integration require?
The initial model uses game context and player-provided preferences such as role, schedule, communication style, and goals. The exact schema is defined with each design partner.
How do you handle safety and player privacy?
We are designing for explicit data boundaries, minimum-necessary inputs, auditable recommendation controls, and behavior-aware eligibility. Production requirements will be agreed with each studio.
What will the platform cost?
Commercial pricing has not been finalized. The intended model is a platform subscription with usage-based API pricing and enterprise support after the developer preview.