What Godot MultiplayerAPI is
Godot's MultiplayerAPI is the engine's high-level multiplayer interface: RPCs, authority, and scene replication (MultiplayerSpawner, MultiplayerSynchronizer) over a multiplayer peer such as ENet, WebSocket or WebRTC. It is free and built in. It does not include accounts, matchmaking, a lobby service or a place to run the server.
The hosted Multiplayer API at multiplayerapi.com provides those missing pieces over HTTP and WebRTC. It is engine-agnostic: the same rooms serve a Godot build, a web build and a Unity build.
Side by side
| Multiplayer API | Godot MultiplayerAPI | |
|---|---|---|
| Hosting | fully hosted, nothing to run | none: engine-level; you or a host player run the server |
| Price model | flat $19.99/month, unlimited games | free, open source (you pay for your own servers) |
| Transport | WebRTC peer-to-peer + automatic relay | ENet, WebSocket or WebRTC peers you configure |
| Validated state | declarative JSON rules | RPC authority and synchronizers; validation is your code |
| Accounts & leaderboards | built in | not included: you build or integrate them |
| AI-agent setup | unauthenticated game creation + llms-full.txt | an agent writes scene, RPC and hosting code |
Checked September 2026 against public documentation. Tell us if something changed: contact@lannetech.ae.
Choose Godot MultiplayerAPI if…
- You want deep scene replication with Godot's own tools,
@rpcannotations and spawners. - You already have a dedicated server or host-player model and just need transport.
- You only target Godot and want zero outside services.
Choose Multiplayer API if…
- You need accounts, matchmaking, rooms and leaderboards without building a lobby server.
- You export Godot to the web and want WebRTC with automatic relay fallback.
- You want the same rooms to serve other clients (browser, Unity).
They combine. You can use the hosted API only for login, matchmaking and room codes, then connect Godot peers however you like. The Godot integration guide shows the HTTP calls from GDScript.
Moving from Godot MultiplayerAPI: what maps to what
@rpccalls for gameplay → keep them if you run your own peers, or useroom.send()/room.emitEvent()through the hosted API.- Lobby and room-code UI you built →
mp.quickmatch(),mp.create()andmp.join(code). - Synchronized properties → shared state paths such as
players.<id>.hp, guarded by declarative rules. - Host-authority checks →
write: "host"rules, automatic host migration and match attestation. - Dedicated server hosting → not needed for the hosted peer-to-peer model.
The concepts are covered in full in the documentation and in llms-full.txt, which a coding agent can use to do the port for you.
Try it in one call
curl -X POST https://multiplayerapi.com/v1/games \
-H 'Content-Type: application/json' \
-d '{"name":"My Game","preset":"realtime_arena"}'Returns a public key, a secret key and a sandbox with 2 live rooms for 24 hours. No account, no card.
Is Multiplayer API made by Godot?
No. Multiplayer API at multiplayerapi.com is an independent hosted service. The similar name is a coincidence: Godot's class is called MultiplayerAPI and ships inside the engine.
Can I use Godot's MultiplayerAPI and the hosted Multiplayer API together?
Yes. A common split is to use the hosted API for accounts, matchmaking and leaderboards, and Godot's own networking for gameplay.
Does the hosted API work with Godot web exports?
Yes. Web exports can call the JavaScript SDK through JavaScriptBridge and get WebRTC peer-to-peer with relay fallback.
Make your game online today
Free sandbox keys in one call, no account and no card. $19.99/month when you ship, for every game you make.
Free sandbox · $19.99/mo to go live · cancel anytime