Install Jentic One Beta

Connect the Amazon GameLift to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon GameLift, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Famazon-gamelift" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Famazon-gamelift" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon GameLift API.

Upload custom game server builds and scripts and deploy them to GameLift fleets

Create and scale fleets across AWS regions with on-demand or Spot capacity

Place game sessions into queues and prioritise destinations by latency

Run FlexMatch matchmaking with custom rule sets to assemble balanced matches

Create and reserve player sessions inside running game sessions

GET STARTED

Start building with Amazon GameLift API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Amazon GameLift API for, with concrete tasks.

★ Multi-Region Fleet Deployment

Game studios use Amazon GameLift to deploy custom server builds to fleets in multiple AWS regions, giving players low-latency match capacity worldwide. The API drives build upload, fleet creation, and scaling so studios can spin up regional capacity for launch windows or events without operating their own datacenters. Fleets support on-demand and Spot instances to balance reliability with cost.

Create a fleet named eu-prod from build build-abc with EC2 instance type c5.large and target 10 instances in region eu-west-1.

FlexMatch Matchmaking

Multiplayer titles use GameLift FlexMatch to assemble matches from queued players based on skill, latency, and party composition rules. The API creates matchmaking tickets, monitors their status, and accepts or rejects matches once players are assembled. FlexMatch evaluates rule sets server-side so studios do not need to operate their own matchmaking workers.

Start a FlexMatch ticket with configuration RankedSquad-1v1 and player attributes skill=1500 and region=eu-west.

Game Session Placement Queues

Operations teams use GameLift queues to place game sessions across multiple fleets and regions, prioritising destinations by player latency. The API submits placement requests and reports back a session endpoint once capacity is found, with fallback to other regions if the primary fleet is full. Queues smooth match flow during peak load.

Start a game session placement on queue prod-global for 4 players with latency policy that prefers region eu-west-1 under 50ms.

Agent-Driven Match Operations via Jentic

AI agents use the GameLift API through Jentic to handle live operations such as scaling fleets ahead of expected player demand, adjusting matchmaking rule sets, and rolling builds via aliases. Jentic exposes GameLift operations as discoverable tools so an agent can search by intent and execute the matching call. This compresses operator response time during launch and event spikes.

Search Jentic for create gamelift fleet, load the CreateFleet schema, and execute it for build build-abc, instance type c5.xlarge, and target 20 instances in us-east-1.

Key Endpoints

104 endpoints — jentic publishes the only available openapi specification for amazon gamelift, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=GameLift.CreateBuild

POST

/#X-Amz-Target=GameLift.CreateFleet

Create a fleet of game server instances

POST

/#X-Amz-Target=GameLift.CreateGameSession

Start a new game session

POST

/#X-Amz-Target=GameLift.CreateGameServerGroup

Create a FleetIQ game server group

POST

/#X-Amz-Target=GameLift.AcceptMatch

Accept or reject a FlexMatch proposal

POST

/#X-Amz-Target=GameLift.CreateAlias

Create an alias that routes to a fleet

POST

/#X-Amz-Target=GameLift.ClaimGameServer

Claim a FleetIQ game server for a player

POST

/#X-Amz-Target=GameLift.CreateBuild

POST

/#X-Amz-Target=GameLift.CreateFleet

Create a fleet of game server instances

POST

/#X-Amz-Target=GameLift.CreateGameSession

Start a new game session

POST

/#X-Amz-Target=GameLift.CreateGameServerGroup

Create a FleetIQ game server group

POST

/#X-Amz-Target=GameLift.AcceptMatch

Accept or reject a FlexMatch proposal

POST

/#X-Amz-Target=GameLift.CreateAlias

Create an alias that routes to a fleet

POST

/#X-Amz-Target=GameLift.ClaimGameServer

Claim a FleetIQ game server for a player

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Amazon GameLift by hand means building SigV4 request signing, resolving the regional gamelift.{region}.amazonaws.com host, and handling the X-Amz-Target action dispatch plus AWS retries yourself. Through Jentic you install once, import GameLift from the API Directory, store the AWS access keys once, and your agent calls it.

Permission scoping

GameLift dispatches every action through a single endpoint with the operation named in the request, so scope the agent to the operations it needs, such as creating a fleet, game session, or match. Destructive operations like deleting a fleet or game server group stay out of that set unless you add them.

Credential isolation

Your AWS access keys for GameLift are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a game server fleet' or 'start a game session', and Jentic returns the matching GameLift operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Amazon GameLift API through Jentic.

Why is there no official OpenAPI spec for Amazon GameLift?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon GameLift via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Amazon GameLift API use?

GameLift uses AWS Signature Version 4 request signing. Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so the agent never sees the raw secret access key.

Can I run FlexMatch matchmaking with this API?

Yes. StartMatchmaking submits a ticket against a matchmaking configuration with player attributes. AcceptMatch and DescribeMatchmaking complete the flow once FlexMatch proposes a match assembled from queued players.

What are the rate limits for the Amazon GameLift API?

AWS applies per-account, per-region throttling. Mutating fleet operations and DescribeGameSessions have separate throttling buckets. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec.

How do I create a game server fleet through Jentic?

Search Jentic for create gamelift fleet, load the CreateFleet schema, and execute it with build ID, EC2 instance type, runtime configuration, and target instance count. Jentic returns the new fleet ID and status.

Does this API host the game session network traffic itself?

No. This API manages fleets, sessions, and matchmaking. Actual gameplay packets flow directly between clients and game server processes running on the fleet's EC2 instances using the ports configured in the fleet.

Can I limit what my agent is allowed to do with the Amazon GameLift API?

Yes. GameLift dispatches every action through a single endpoint with the operation named in the request, and because you run Jentic One yourself, your own rules decide which of those operations the agent may call. You can allow it to create fleets, place game sessions, and start FlexMatch matchmaking while keeping destructive calls such as deleting a fleet or a game server group out of its allowed set. The agent can only invoke the operations and credentials you have granted, so it never reaches a GameLift action you did not permit.

AWS Amazon GameLift

Browse all Amazonaws APIs

AI ReadinessFoundational (C+)60/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeapiKey104 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Deploy multiplayer game servers, manage fleets and builds, run FlexMatch matchmaking, and place players into game sessions through Amazon GameLift.

Use for: I need to deploy a new build to a GameLift fleet, Create a fleet of game servers in eu-west-1 and us-east-1, Place a game session for four players via the queue, Start a FlexMatch matchmaking ticket for a player squad

Not supported: Does not handle in-game voice chat, player accounts, billing, or in-game economy - use for game server hosting, matchmaking, and session placement only.

Jentic publishes the only available OpenAPI specification for Amazon GameLift, keeping it validated and agent-ready. Amazon GameLift is AWS's managed service for hosting session-based multiplayer game servers in the cloud. The API covers fleets, builds, scripts, aliases, game sessions, player sessions, FlexMatch matchmaking, queues, and GameLift FleetIQ for cost-optimised Spot capacity. It is built for game studios that need to deploy custom server binaries to global AWS regions, scale match capacity dynamically, and route players into matches with low latency.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

49%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

83%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Amazon GameLift to your agent

Capabilities

Start building with Amazon GameLift API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AWS Amazon GameLift

Jentic AI Readiness Score

Amazon GameLift

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness