Skip to main content
BETA

Portal Nexus — Information for AI Agents

Introduction

Portal Nexus is a single login for game creation — access multiple models to generate assets, spritesheets, voice, music, and more. Developers use one account and one credit balance to route prompts to specialized providers, connect coding agents through MCP, and integrate sprite generators, 3D model APIs, voice and music services, NPC dialogue, and engine tools. This page summarizes the product for automation, research, and integrations.

Core capabilities

  • Smart routing across providers (cheapest, best, fastest).
  • Unified credit billing with usage analytics.
  • User sign-in via AIR Kit — shared account with Portal Studio (https://studio.portalgaming.com).
  • `POST /api/auth/bootstrap` — AIR token in, user row + primary API key + credits out.
  • `GET /api/v1/user/recent-tools` — recent tool visits for the authenticated user API key.
  • REST API at `/api/v1/*` with Bearer token auth.
  • `GET /api/auth/me` — verify AIR access token (JWT against AIR JWKS).
  • Local MCP server package (`@gamerouter/mcp`) for Cursor and agents.
  • Hosted MCP server at `/api/mcp` (Streamable HTTP) — no local install needed.
  • Tool catalog, create dock, preview gallery, templates, docs, and authenticated dashboard.

API endpoints

  • `GET /api/v1/tools` — list tools in the catalog.
  • `GET /api/v1/engines` — list supported engines.
  • `GET /api/v1/credits` — credit balance for the API key.
  • `GET /api/v1/usage` — usage history.
  • `POST /api/v1/generate/2d` — 2D asset generation.
  • `POST /api/v1/generate/3d` — 3D asset generation.
  • `POST /api/v1/generate/image` — concept art / image generation.
  • `POST /api/v1/generate/voice` — voice synthesis.
  • `POST /api/v1/generate/music` — music generation.
  • `POST /api/v1/npc/chat` — NPC dialogue.
  • `POST /api/mcp` — MCP JSON-RPC endpoint (Streamable HTTP transport, also handles `GET`/`DELETE`).

MCP deployment model

Two ways to connect an agent to Portal Nexus over MCP:

  • Hosted (Streamable HTTP) — point any MCP client at `https://nexus.portalgaming.com/api/mcp` with `Authorization: Bearer <key>`. No local install; runs on Portal Nexus servers.
  • Local (stdio)— install the `@gamerouter/mcp` package and set `GAMEROUTER_API_KEY` in the MCP environment. Runs on the developer's own machine; adds one tool ( `nexus_upload_project_asset`) that reads a local file path, which only works when the agent and server share a filesystem.

Both expose the same `nexus_*` tool set otherwise (credits, tool catalog, 2D generation, project folders and assets).

Use cases

  • Which API generates pixel-art sprites for a Godot project?
  • How do I route 3D requests to the cheapest provider?
  • What MCP tools does Portal Nexus expose for Cursor?
  • How is credit billing handled per request?
  • Which engines are listed as compatible with each tool?

Discovery files

Agents should consume `/sitemap.xml`, `/robots.txt`, and `/llms.txt` for route and crawl guidance without requiring JavaScript execution.

Links