01
Send eligible players
Provide the game-mode constraints and minimum player context agreed for the workflow.
Developer preview
Integrate social matchmaking without replacing your core queue.
Gamers Framework is designed as a backend decision layer that works alongside the skill, latency, role, platform, and population constraints your game already owns.
The interface below is illustrative. The production schema will be defined with design partners.
Illustrative request workflow
02
Receive ranked groups
Request candidate squads with compatibility factors your backend can inspect and apply.
03
Report outcomes
Return repeat-play, leave, block, and other agreed signals so future recommendations can improve.
Example request
POST /v1/squads/recommend
{
"game_mode": "ranked_squad",
"region": "eu-west",
"players": [
{
"player_ref": "opaque-player-reference",
"role": "support",
"play_style": "coordinated",
"communication": "voice-preferred"
}
]
}Player references should be scoped and pseudonymous. Exact fields, retention, access, and deletion requirements must be agreed before any production integration.
Questions for the design-partner phase
- Which formation decisions should the compatibility layer influence?
- Which player-declared and game-owned signals are necessary?
- What latency and availability constraints must the recommendation meet?
- How should studio safety policy affect eligibility?
- Which outcomes demonstrate healthier, more durable groups?
Shape the first integration.
We are looking for multiplayer studios willing to define a concrete use case, integration boundary, and success measure.
Request developer access