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 (Discover — default signed-in and Hub iframe landing), create dock, preview gallery, prompts, docs, and authenticated dashboard (including Connect for MCP agents).

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 (prefer `/api/v1/jobs` — this is the slowest category).
  • `POST /api/v1/generate/image` — concept art / image generation.
  • `POST /api/v1/generate/voice` — voice synthesis.
  • `POST /api/v1/generate/music` — music generation (mock output only today).
  • `POST /api/v1/generate/vfx` — VFX / video clip generation.
  • `POST /api/v1/generate/editing` — image upscale, inpaint, outpaint, remove background.
  • `POST /api/v1/jobs` — submit an async generation job (any category); `GET /api/v1/jobs` lists yours, `GET /api/v1/jobs/:jobId` polls one.
  • `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).

Generation API — full reference

The REST surface above (`/api/v1/generate/*`, `/api/v1/jobs`, `/api/v1/credits`) has a full human-readable reference at https://nexus.portalgaming.com/for-agents/generation-api, and a complete OpenAPI 3.1 specification — request/response bodies, every error code, and job states — at https://nexus.portalgaming.com/openapi.yaml for codegen or API-import tooling.

Every request needs `Authorization: Bearer <api-key>` — Bearer only, no alternate header scheme. Keys are created self-serve at https://nexus.portalgaming.com/dashboard/keys once signed in: `gr_live_...` for real, billed generations, or `gr_test_...` for sandbox integration testing. Both forms hit the same base URL and the same endpoints — there is no separate test API.

Every category has at least one real, configured provider except `music` (mock output only, no configured provider yet) — an unconfigured provider degrades gracefully to a mock result rather than erroring. Check the returned URL to tell a mock (`https://cdn.gamerouter.dev/mock/...`) from a real one.

Third-party agent integration example

A minimal integration for a third-party AI agent platform — e.g. an in-game asset-generation skill — looks like this:

  1. A Portal Nexus user creates an API key at https://nexus.portalgaming.com/dashboard/keysand pastes it into the third-party platform's own connection setup — Portal Nexus never sees or stores that platform's credentials, and the key can be revoked independently at any time without touching the rest of the account.
  2. The platform calls `POST /api/v1/generate/:category` (or `POST /api/v1/jobs` for slower categories, notably `3d`) with that key as a Bearer token, exactly as documented above.
  3. For async jobs, it polls `GET /api/v1/jobs/:jobId` until `status` is `succeeded` or `failed`.
  4. The response's output URL is a plain public HTTPS URL — fetchable with no Portal Nexus session, ready to hand back to the end user or save into their game project.

This is the same REST surface every caller uses — the Portal Nexus dashboard, MCP clients, and third-party integrations all authenticate and bill identically, so there is no separate or restricted tier for external platforms.

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