Inthegame
Inthegame (Synced Apps Technologies Ltd.) is a viewer-interaction and CTV/OTT engagement platform. Its patented no-code layer injects interactive in-stream overlays — polls, trivia, ratings, wikis, offers and a points shop — into live and recorded video across smart TVs and mobile devices, driving engagement and monetization for streaming platforms and broadcasters. The API exposes two surfaces: an adminApi for broadcasters to manage streamers/channels and inject engagements, and a userApi for end-viewers to register, play, answer, chat, buy and climb real-time leaderboards, with a Socket.IO channel pushing live engagement events.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Inthegame the way a machine reads it — 27 machine-readable artifacts across 21 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Inthegame scores 44.9/100 (thin), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Inthegame
Each block below is one kind of artifact we hold for Inthegame. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Inthegame admin API
The admin API from Inthegame — 1 operation(s) for admin.
Inthegame analytics API
The analytics API from Inthegame — 3 operation(s) for analytics.
Inthegame category API
The category API from Inthegame — 5 operation(s) for category.
Inthegame chat API
The chat API from Inthegame — 3 operation(s) for chat.
Inthegame entity API
The entity API from Inthegame — 7 operation(s) for entity.
Inthegame general API
The general API from Inthegame — 1 operation(s) for general.
Inthegame item API
The item API from Inthegame — 6 operation(s) for item.
Inthegame leaderboard API
The leaderboard API from Inthegame — 1 operation(s) for leaderboard.
Inthegame moderationData API
The moderationData API from Inthegame — 3 operation(s) for moderationdata.
Inthegame poll API
The poll API from Inthegame — 7 operation(s) for poll.
Inthegame promotion API
The promotion API from Inthegame — 5 operation(s) for promotion.
Inthegame rating API
The rating API from Inthegame — 6 operation(s) for rating.
Inthegame shop API
The shop API from Inthegame — 7 operation(s) for shop.
Inthegame socket API
The socket API from Inthegame — 1 operation(s) for socket.
Inthegame sponsor API
The sponsor API from Inthegame — 5 operation(s) for sponsor.
Inthegame streamer API
The streamer API from Inthegame — 16 operation(s) for streamer.
Inthegame translations API
The translations API from Inthegame — 6 operation(s) for translations.
Inthegame trivia API
The trivia API from Inthegame — 6 operation(s) for trivia.
Inthegame uploads API
The uploads API from Inthegame — 3 operation(s) for uploads.
Inthegame user API
The user API from Inthegame — 11 operation(s) for user.
Inthegame wiki API
The wiki API from Inthegame — 5 operation(s) for wiki.
Scroll within the panel for all 21 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
inthegame-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Inthegame Realtime (Socket.IO)
Real-time viewer-engagement events pushed over Socket.IO. The socket traces server messages to the app, keeping viewer state in sync when admins inject polls, ratings, trivia, o...
ASYNCAPIExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Inthegame Examples
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Inthegame — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
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
← All providers · Data indexed from github.com/api-evangelist/inthegame · machine-readable index on apis.io