Gameye website screenshot

Gameye

Gameye is a managed game server orchestration platform for multiplayer game studios, founded in 2017 in Rotterdam (Gameye B.V.). It runs dedicated, containerized game servers across bare metal, cloud, and edge providers behind a single REST API — the Session API. Studios call POST /session with a region and a Docker image; Gameye selects the best available location, starts a container in about half a second, and returns the host IP and mapped ports players connect to. Capacity-based pricing carries no egress fees, and the platform is matchmaker-agnostic (Pragma Engine, Nakama, PlayFab, FlexMatch). Gameye has orchestrated 120M+ sessions with a 99.99% uptime SLA and serves studios including Torn Banner Studios (Chivalry 2) and Remedy Entertainment.

Gameye publishes 5 APIs on the APIs.io network, including Artifacts API, Available Location API, Logs API, and 2 more. Tagged areas include Company, Game Server Hosting, Game Server Orchestration, Multiplayer, and Containers.

Gameye’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 28 more developer resources.

54.3/100 developing ▬ flat Agent 69/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
5 APIs 1 MCP Servers
CompanyGame Server HostingGame Server OrchestrationMultiplayerContainersInfrastructureGamingEdge ComputingDevOps

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 54.3/100 · developing
Contract Quality 13.8 / 25
Developer Ergonomics 16.1 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 5.5 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 69/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/gameye: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Gameye Artifacts API

The Artifacts API from Gameye — 1 operation(s) for artifacts.

Gameye Available Location API

The Available Location API from Gameye — 1 operation(s) for available location.

Gameye Logs API

The Logs API from Gameye — 1 operation(s) for logs.

Gameye Session API

The Session API from Gameye — 4 operation(s) for session.

Gameye Tag API

The Tag API from Gameye — 1 operation(s) for tag.

Arazzo Workflows 4

Multi-step API workflows described with the Arazzo specification.

_Index

ARAZZO

Allocate a Gameye session and get its connection address

Pick an available region for an image, start a session, and read its host/ports.

ARAZZO

Manage the player roster on a Gameye session

Start a session, register players joining, then remove players leaving.

ARAZZO

Stream logs, stop a Gameye session, and download an artifact

Pull a session's logs, terminate it, then download a diagnostic artifact.

ARAZZO

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

gameye-mcp.yml

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Gameye Authentication

http · 1 scheme

SECURITY

Gameye Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Gameye Agentic Access

10 operations · 4 acting · 1 human-in-the-loop

10 operations · 4 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Scroll for all 8

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: gameye
name: Gameye
description: Gameye is a managed game server orchestration platform for multiplayer game studios, founded in 2017 in Rotterdam
  (Gameye B.V.). It runs dedicated, containerized game servers across bare metal, cloud, and edge providers behind a single
  REST API — the Session API. Studios call POST /session with a region and a Docker image; Gameye selects the best available
  location, starts a container in about half a second, and returns the host IP and mapped ports players connect to. Capacity-based
  pricing carries no egress fees, and the platform is matchmaker-agnostic (Pragma Engine, Nakama, PlayFab, FlexMatch). Gameye
  has orchestrated 120M+ sessions with a 99.99% uptime SLA and serves studios including Torn Banner Studios (Chivalry 2) and
  Remedy Entertainment.
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://static.gameye.com/images/android-chrome-512x512.png
url: https://raw.githubusercontent.com/api-evangelist/gameye/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-tier: enriched
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Game Server Hosting
- Game Server Orchestration
- Multiplayer
- Containers
- Infrastructure
- Gaming
- Edge Computing
- DevOps
apis:
- aid: gameye:gameye-artifacts-api
  name: Gameye Artifacts API
  description: The Artifacts API from Gameye — 1 operation(s) for artifacts.
  humanURL: https://gameye.com/docs/api-v2/
  baseURL: https://api.production-gameye.gameye.net
  tags:
  - Artifacts
  properties:
  - type: OpenAPI
    url: openapi/gameye-artifacts-api-openapi.yml
- aid: gameye:gameye-available-location-api
  name: Gameye Available Location API
  description: The Available Location API from Gameye — 1 operation(s) for available location.
  humanURL: https://gameye.com/docs/api-v2/
  baseURL: https://api.production-gameye.gameye.net
  tags:
  - Available Location
  properties:
  - type: OpenAPI
    url: openapi/gameye-available-location-api-openapi.yml
- aid: gameye:gameye-logs-api
  name: Gameye Logs API
  description: The Logs API from Gameye — 1 operation(s) for logs.
  humanURL: https://gameye.com/docs/api-v2/
  baseURL: https://api.production-gameye.gameye.net
  tags:
  - Logs
  properties:
  - type: OpenAPI
    url: openapi/gameye-logs-api-openapi.yml
- aid: gameye:gameye-session-api
  name: Gameye Session API
  description: The Session API from Gameye — 4 operation(s) for session.
  humanURL: https://gameye.com/docs/api-v2/
  baseURL: https://api.production-gameye.gameye.net
  tags:
  - Session
  properties:
  - type: OpenAPI
    url: openapi/gameye-session-api-openapi.yml
- aid: gameye:gameye-tag-api
  name: Gameye Tag API
  description: The Tag API from Gameye — 1 operation(s) for tag.
  humanURL: https://gameye.com/docs/api-v2/
  baseURL: https://api.production-gameye.gameye.net
  tags:
  - Tag
  properties:
  - type: OpenAPI
    url: openapi/gameye-tag-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://gameye.com
- type: DeveloperPortal
  url: https://gameye.com/docs/
- type: Documentation
  url: https://gameye.com/docs/api-v2/
- type: APIReference
  url: https://gameye.com/docs/api-v2/
- type: GettingStarted
  url: https://gameye.com/docs/getting-started/
- type: Support
  url: https://gameye.com/docs/support/getting-support/
- type: Blog
  url: https://gameye.com/blog/
- type: GitHubOrganization
  url: https://github.com/Gameye
- type: Roadmap
  url: https://gameye.com/roadmap/
- type: Pricing
  url: https://gameye.com/pricing/
- type: SignUp
  url: https://trial.gameye.com/
- type: TermsOfService
  url: https://gameye.com/terms/
- type: PrivacyPolicy
  url: https://gameye.com/privacy/
- type: StatusPage
  url: https://gameye.com/status/
- type: ChangeLog
  url: https://gameye.com/docs/changelogs/
- type: ChangeLog
  url: changelog/gameye-changelog.yml
- type: Authentication
  url: authentication/gameye-authentication.yml
- type: DomainSecurity
  url: security/gameye-domain-security.yml
- type: AgenticAccess
  url: agentic-access/gameye-agentic-access.yml
- type: Packages
  url: packages/gameye-packages.yml
- type: SDKs
  url: packages/gameye-packages.yml
- type: WellKnown
  url: well-known/gameye-well-known.yml
- type: APICatalog
  url: well-known/gameye-api-catalog.json
- type: MCPServer
  url: mcp/gameye-mcp.yml
- type: LLMsTxt
  url: llms/gameye-llms.txt
- type: Conformance
  url: conformance/gameye-conformance.yml
- type: ErrorCatalog
  url: errors/gameye-problem-types.yml
- type: Lifecycle
  url: lifecycle/gameye-lifecycle.yml
- type: Sandbox
  url: sandbox/gameye-sandbox.yml
- type: Conventions
  url: conventions/gameye-conventions.yml
- type: DataModel
  url: data-model/gameye-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Allocate a Gameye session and get its connection address
  url: arazzo/gameye-allocate-session.yml
- type: Arazzo
  name: Manage the player roster on a Gameye session
  url: arazzo/gameye-player-lifecycle.yml
- type: Arazzo
  name: Stream logs, stop a Gameye session, and download an artifact
  url: arazzo/gameye-session-teardown.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence