# Portal Studio

> Canonical site: https://portal-gameteam.vercel.app
> Parent ecosystem: https://portalgaming.com/
> Update this file on major product, route, API, or provider changes (see docs/AGENT_DISCOVERY.md).

## What is Portal Studio?
Portal Studio is a visual workspace for orchestrating coding and creative AI agents. Teams connect agents to a shared spatial canvas, coordinate multi-agent workflows, and collaborate in real time instead of juggling disconnected terminals.

This deployment (`portal-gameteam`) hosts the public marketing site, the Studio web app, and serverless API routes.

## Core capabilities
- Spatial agent map with roster, connection health, and session visibility
- Multi-agent orchestration from one control surface
- Shared workspaces and agent-to-agent sessions
- Provider connection flows (API keys, gateways, managed agents)
- Marketing site localization: English, Korean, Japanese (EN / KO / JP)

## Key pages (marketing)
- Welcome: https://portal-gameteam.vercel.app/
- About: https://portal-gameteam.vercel.app/about.html
- How it works: https://portal-gameteam.vercel.app/how-it-works.html
- Tutorials (provider guides): https://portal-gameteam.vercel.app/tutorials.html
- Contact: https://portal-gameteam.vercel.app/contact.html
- For AI agents (HTML): https://portal-gameteam.vercel.app/for-agents
- Studio app: https://portal-gameteam.vercel.app/app/index.html

## Agent discovery
- llms.txt: https://portal-gameteam.vercel.app/llms.txt
- For agents page: https://portal-gameteam.vercel.app/for-agents
- Robots: https://portal-gameteam.vercel.app/robots.txt
- Sitemap: https://portal-gameteam.vercel.app/sitemap.xml

## Supported agent providers (connection tutorials)
Documented on /tutorials.html (expandable guides):
- Claude (Anthropic API)
- OpenAI (Assistants API)
- OpenClaw (local gateway + public URL)
- Hermes (compatible endpoint)
- Virtuals Protocol
- Portal-managed agents (Shards billing)
- Minds (email-based AI)
- Custom OpenAI-compatible endpoints

## API & backend (this deployment)
- Health: GET https://portal-gameteam.vercel.app/health
- API prefix: https://portal-gameteam.vercel.app/api/ (serverless; see repo `api/` and `backend/`)
- Minds bridge: https://portal-gameteam.vercel.app/minds/

Repo conventions: `docs/BACKEND.md`, `docs/API_REFERENCE.md`, `AGENT_PROVIDERS.md`.

## Who we serve
- Game developers and technical artists using AI agents in production workflows
- Studios coordinating multiple agents across a project
- Creators prototyping multi-agent pipelines before hardening in engine/tooling

## Contact & social
- Contact form: https://portal-gameteam.vercel.app/contact.html
- Support email: mailto:support@portalgaming.com
- X (Twitter): https://x.com/Portalcoin
- Broader Portal products & partnerships: https://portalgaming.com/

## Technology (public-facing)
- Marketing: static HTML + shared chrome (`public/site-chrome.js`, `public/site-i18n.js`)
- Studio app: single-page HTML client (`app/index.html`) with canvas UI
- Backend: Node serverless on Vercel (`api/index.ts`, `backend/`)
- Auth/session patterns: see `docs/PROJECT_OVERVIEW.md` and backend auth modules

## Frequently asked questions

Q: What is Portal Studio in one sentence?
A: A spatial studio where teams connect, visualize, and steer multiple AI agents in one shared workspace.

Q: How do users launch the app?
A: Open /app/index.html (or “Launch App” on marketing pages). Entry can skip onboarding via `?enter=skip`.

Q: Where are provider connection instructions?
A: On /tutorials.html — requirements and step-by-step guides per provider.

Q: Does the marketing site support multiple languages?
A: Yes. Top-nav toggle cycles EN → KO → JP. Message files: `public/messages/en.json`, `ko.json`, `ja.json`.

Q: Is there a page specifically for AI agents and LLMs?
A: Yes. Use /for-agents and this /llms.txt file. Also consume /sitemap.xml and /robots.txt.

Q: How does Portal Studio relate to portalgaming.com?
A: portalgaming.com is the Portal company site (portfolio, partnerships, GameRouter, GameGen, GameHub, etc.). This repo is the Portal Studio product experience and app.

Q: How should agents stay up to date?
A: Prefer /llms.txt and /for-agents over scraping the canvas app. Re-fetch after deploys that change routes, providers, or capabilities listed here.