Sovrun Docs 2025
  • INTRO TO SOVRUN
    • Introduction to Sovrun
    • Autonomous Worlds
    • About Sovrun
      • Sovrun Genesis
      • Sovrun Labs
      • Sovrun Nexus
      • Case Study: Eve Frontier
      • Case Study: Plunder Quest
      • History of Sovrun (BreederDAO)
  • The SOVRN Token
    • About $SOVRN
    • Token Utility
    • $SOVRN Tokenomics
    • $SOVRN on EVM Chains
      • Ethereum
      • Hyperliquid
        • Network Info
          • Block Explorer
          • Acquiring test SOVRN
        • Sessionchains
      • Base
      • BREED to SOVRN Migration
  • Build with Sovrun
    • Chain Tactics
      • Who is Chain Tactics for?
      • Why Mod Chain Tactics?
      • Headless Client
      • Sovrun SDK
      • Game Phases
      • Game Mechanics
      • Game Architecture
      • Expanding Chain Tactics Across EVM-Compatible Chains
      • Chain Tactics Development Roadmap
      • Terminology
      • Getting Started Guides
        • Chain Tactics Local Development & Headless Client
        • Lightweight Unity Client
        • Chain Tactics Modding Tutorials
        • Troubleshooting Chain Tactics Local Development
    • ReadyGamer
      • Joint Venture
      • Services
      • Architecture
      • GAME Framework
      • ReadyGamer API
      • Integration Workflow
      • Roblox Integration
        • Roblox Demo Game - Carnival AI
        • AI Agent NPC's
        • Roblox AI Agent Module
          • Getting Started
          • Module Components
          • Creating a Smart NPC
          • Creating a Continuous Behaviour Script
  • More
    • Sovrun Website
Powered by GitBook
On this page
  • Direct ReadyGamer API Access (Existing Virtuals Agent)
  • Default template for POST Request
  • Default template for the Response
  • Direct ReadyGamer API Access (Existing Agent)
  • HTTPS Post Request Format
  • Response Format
  1. Build with Sovrun
  2. ReadyGamer

ReadyGamer API

PreviousGAME FrameworkNextIntegration Workflow

Last updated 19 days ago

Please reach out if you would like a specific endpoint created for you to start here >

Direct ReadyGamer API Access (Existing Virtuals Agent)

The following sections is if you have an existing Virtuals agent that you want to deploy in your game!

Your game should do an HTTPS Post request to the endpoint that we will provide you in order to send the chat data. The URL that we will create for you will be in this format:

https://api.ready-gamer.sovrun.org/api/<name_of_game>/<command>/chat

For example:

https://api.ready-gamer.sovrun.org/api/roblox/lightsout/chat

Method: POST

Headers: X-API-Key (Will be provided by Ready Gamer team separately)

Default template for POST Request

Below is the list of the default parameters for a basic chat integration to the Ready Gamer API. In case your game needs to send additional data i.e. environment data, please contact us so we can tailor fit the endpoint for you.

{
 "text": "how are you doing?",
 "userId": "123abc",
 "userName": "john",
 "agentName": "test_ready_gamer_agent",
 "agentId": "8",
}
  • text is the chat message coming from the user inside the game

  • userId is the user id of the player who's currently chatting with the agent npc..

  • userName is the name of the player who's currently chatting with the agent npc.

  • agentName is the name of the agent. This should be a unique value per specific agent. We will use this value to delegate the message to the corresponding agent.

    • For testing purposes, please use "test_ready_gamer_agent" as the agentName value.

  • agentId is the id of the agent relevant to the game. We added this to the template so that the game can properly delegate the message in case there are multiple instances of the same agent.

Default template for the Response

After calling the endpoint provided to you, the response will be in this format:

{
    "response": "i'm doing great john!", 
    "agentId": "8", 
    "agentName": "test_ready_gamer_agent"
}


Direct ReadyGamer API Access (Existing Agent)

The following sections is if you have an existing agent that you want to deploy in your game!

To prepare your agent for integration with the Ready Gamer API, your agent should have an endpoint with a capability to accept HTTPS POST requests in the format below.

HTTPS Post Request Format

{
    "message": "how are you doing?",
    "name_of_player": "john",
    "environment": ""
} 
  • message is the chat message coming from the game.

  • name_of_player is the name of the player who's currently chatting with the agent.

  • environment is a string containing information describing the current game state.

Response Format

Regardless of what custom functions the agent was built to do, it should respond to the request in this format:

{
    "response": "i'm doing great john!"
}
  • response is the processed message reply of the agent.

Once your agent endpoint is ready to accept this request, please contact us so we can connect you to the Ready Gamer API.

ReadyGamer API Access Request