Skip to content
AI Agent

Install with AI Agent

Copy & paste this prompt

Install the Hyperstone Unity SDK in this project. Follow these steps: 1. Read the integration recipe: https://hyperstone.ai/docs/llms.txt 2. Use the documentation that best fits your context window: - Minimal (fast): https://hyperstone.ai/docs/llms.txt - Full (comprehensive): https://hyperstone.ai/docs/llms-full.txt - Small (optimized): https://hyperstone.ai/docs/llms-small.txt 3. Execute the installation following the recipe instructions. 4. Verify that the SDK is correctly installed and integrated into the project.

Server-to-Server Integration

Overview

Section titled “Overview”

The Server-to-Server (S2S) integration allows your backend to communicate directly with Hyperstone’s optimization engine via a REST API. This is ideal for:

  • Server-side game logic that requires optimized parameters.
  • Applications where client-side SDK integration is not feasible.
  • Security-sensitive environments where configuration must be validated server-side.

The goal of this guide is to demonstrate that integrating Hyperstone into your existing backend architecture is straightforward and robust.

Authentication & Security

Section titled “Authentication & Security”

All S2S requests must be authenticated using your Application ID and Application Secret, which can be found in the Hyperstone Console.

Signing Custom User IDs

Section titled “Signing Custom User IDs”

To ensure the integrity of user data, Hyperstone requires that any client-provided User IDs (uid) be cryptographically signed. If you are willing to use custom user identifiers reach out to our engineering team.

Fetching Configuration

Section titled “Fetching Configuration”

To receive an optimized configuration for a user, your server sends a request containing user attributes. The Hyperstone engine evaluates these attributes against active optimizations and returns the best configuration.

Geo-Location Attributes

Section titled “Geo-Location Attributes”

For features relying on geographic targeting (e.g., country-specific pricing or difficulty), you should:

  1. Provide the end user’s IP address via standard headers (e.g., X-Forwarded-For).
  2. Alternatively, you can explicitly provide geolocation attributes in the request payload.

Tracking Metrics & Engagement

Section titled “Tracking Metrics & Engagement”

Because the S2S integration bypasses the client SDK, your backend is responsible for tracking and reporting user engagement and session metrics.

Session & Engagement Tracking

Section titled “Session & Engagement Tracking”

You should implement logic on your side to track:

  • Session Start/End: When a user begins or ends an interaction.
  • Engagement Time: The duration of active user involvement.

Batching & Rate Limits

Section titled “Batching & Rate Limits”

To ensure high performance and system stability:

  • Batch Metrics: Do not send metrics one-by-one as they occur. Instead, accumulate metrics on your side and send them in batches.
  • Respect Rate Limits: The S2S API has strict rate limits. Batching is the primary method to stay within these limits while ensuring all data is captured.

Integration Roadmap

Section titled “Integration Roadmap”

As this feature is under active development, specific endpoint URLs and request parameters are subject to change. We recommend reaching out to our engineering team for the most current API specification and to join our early access program.