# GeniusPro Docs — full context > Consolidated AI-readable context for GeniusPro documentation. ## home Source: https://docs.geniuspro.io/markdown/home # GeniusPro documentation Simon Says — build more, spend less. Every frontier model through one API, one key, one bill. ## What do you want to do? | I want to… | Start here | | ---------- | ---------- | | **Use AI in the browser** (no code) | [Chat → Ainslie & command center](/chat/ainslie) or [first conversation](/chat/getting-started) | | **Set up my company account** | [Platform → Getting started](/platform/getting-started) | | **Build a reusable assistant for my team** | [CATs → Getting started](/cats/getting-started) | | **Integrate from my app or scripts** | [API → Quickstart](/developer/getting-started) | ## What GeniusPro is One account, one bill, every major AI model. **Simon** picks the right capability per task — or you pick a named slug (`simon-says-chat`, `simon-says-coding`, …) or a direct model ID. **Private. US-based providers only. Invite-only while we scale.** ## Docs by section - **[Chat](/chat/overview)** — [chat.geniuspro.io](https://chat.geniuspro.io): **Ainslie** copilot, **My Goals** / **My Work**, studios, knowledge, and billing in one command center. - **[Platform](/platform/overview)** — org, team, workspaces, clients, billing, API keys. - **[CATs](/cats/overview)** — custom workflows your team shares. - **[Studio](/studio/overview)** — compare models and ship prompts (private beta). - **[API](/developer/overview)** — OpenAI-compatible integration for developers. ## Typical first week 1. [Create your account](/platform/getting-started). 2. [Send a few real prompts in chat](/chat/getting-started). 3. Optional: [build one CAT](/cats/getting-started) your team will reuse. 4. Optional: [one API request](/developer/getting-started) when engineering is ready. You can skip steps — but if you are not sure where to start, do them in that order. --- ## platform/overview Source: https://docs.geniuspro.io/markdown/platform/overview # Platform overview One account, one key, one bill. Every frontier model — and Simon picks the smartest one for each task. ## Simon Says — build more, spend less GeniusPro is the platform for working with AI at your company. Every frontier model lives behind one endpoint, one key, and one invoice — and **Simon** picks the smartest, most cost-effective model for each task. The platform runs on three things: 1. **Simon** — the model picker. You can call `simon-says` and let it choose, or pick a self-upgrading name like `simon-says-chat` / `simon-says-coding` — same slug forever, always-current quality. 2. **CATs** — Custom AI Transformers. Multi-step workflows you build for your business, callable from the chat app or the API. 3. **Tiger Mode** — durable execution for long-running CATs. Workflows persist progress and resume on failure instead of dying mid-run. ## What you actually get - **Every frontier model behind one API.** OpenAI, Anthropic, Google, and xAI — all accessible with one OpenAI-compatible endpoint. - **One key. One invoice.** No juggling vendor portals, no separate contracts, no surprise bills. - **US-based AI providers only.** Every model you reach through GeniusPro runs on a US-based provider. - **Private. Invite-only.** We're onboarding carefully while we scale. If you're reading this, you have access — your teammates will need an invite link from you or from us. - **Savings by default.** Simon keeps small prompts on small models and sends the hard ones to the big ones, so you pay frontier prices only when it actually matters. ## Four ways to use it On the same platform, in the same organization, using the same billing: - **Chat** — the everyday app at [chat.geniuspro.io](https://chat.geniuspro.io). Models, CATs, files, and voice. Start at [Chat docs](/chat/overview). - **CATs** — custom AI workflows. Prompts, chained steps (KITTNs), long-running runs in Tiger Mode. - **API** — OpenAI-compatible endpoint for your product and scripts. - **Studio** — compare models side by side and ship prompts to the API. Private beta. ## How the pieces fit together 1. You create an **organization**. This is your company's top-level space and where billing lives. 2. Inside it you create one or more **workspaces** — usually one per product, client, or team. 3. Inside a workspace you, your teammates, and any CATs you've built live side by side. 4. You generate **API keys** at the organization level and call GeniusPro from anywhere. That's the whole mental model. Keep reading or jump straight to [Platform → Getting started](/platform/getting-started). --- ## platform/getting-started Source: https://docs.geniuspro.io/markdown/platform/getting-started # Getting started Request an invite, create your account, set up your org, and open the chat app in about five minutes. ## 0. GeniusPro is invite-only We're onboarding companies in a controlled rollout. If you don't have an invite yet, request one at [geniuspro.io](https://geniuspro.io). If a teammate already has an account, ask them to invite you from **Platform → Team** — they can do it in one click. The rest of this page assumes you have an invite link or an existing account. ## 1. Create your account Go to [platform.geniuspro.io](https://platform.geniuspro.io) and click **Sign up**. Use your work email — it makes inviting teammates later much easier. You can sign up with email or with Google. Either works. You'll land on your organization dashboard as soon as your email is verified. ## 2. Name your organization Your organization is usually your company name. You can rename it later from **Platform → Settings**. A first workspace called *Default* is created for you automatically. Most people never need more than one workspace when starting out — you can create more later from the workspace switcher. ## 3. Pick a plan From **Platform → Billing**, pick the plan that fits your expected usage. You can start small, hit send on real prompts, and upgrade later — nothing locks you in. See [Plans & billing](/platform/billing) for what each plan includes. ## 4. Invite your team Open **Platform → Team** and click **Invite**. Enter their work emails and pick a role. They get an invite link; once they accept they're in the same organization and can see shared CATs. More on roles in [Team & roles](/platform/team). ## 5. Open the chat app Click **Open chat** from the header, or go to [chat.geniuspro.io](https://chat.geniuspro.io). You're signed in automatically — same account. Follow [Chat → Your first conversation](/chat/getting-started) for a short walkthrough (model menu, first message, history). ## 6. What next Most people go one of these directions: - **Keep using chat** — [Everyday tips](/chat/everyday) for files, voice, and model choice. - **Build a custom assistant** — [CATs → Getting started](/cats/getting-started). - **Wire GeniusPro into your code** — start at [API → Quickstart](/developer/getting-started). --- ## platform/organizations Source: https://docs.geniuspro.io/markdown/platform/organizations # Organizations Your organization is the top-level container for your team, workspaces, CATs, and billing. ## What an organization is An organization is your company on GeniusPro. It owns: - **Billing** — one subscription per organization. - **Team members** — people you invite. - **API keys** — keys are scoped to an organization. - **Workspaces** — the places where CATs and chats live. You can belong to more than one organization (for example, your own and a client's). Switch between them from the top-left menu in the platform app. ## What lives where | Thing | Scope | Notes | | -------------- | --------------- | --------------------------------------------------------------- | | Billing plan | Organization | One plan per organization. | | Members | Organization | Invited once; can be added to one or more workspaces. | | API keys | Organization | Usable from any workspace in that organization. | | Workspaces | Inside the org | Separate spaces for projects, teams, or clients. | | CATs | Inside a workspace | Can be shared to the whole workspace, to a client, or kept private. | | Chat history | Per user | Private to the user who had the conversation. | ## When to create a second organization Most companies only need one organization. Consider a second one when: - You run a separate business entity with its own billing. - You're an agency and want completely separate billing and team for a client. If you just want to keep work separate between two internal teams, use **workspaces** instead. ## Renaming and deleting You can rename your organization from **Platform → Settings**. Deleting an organization is permanent and removes all workspaces, CATs, API keys, and history inside it. You need to be the owner to delete. --- ## platform/workspaces Source: https://docs.geniuspro.io/markdown/platform/workspaces # Workspaces Workspaces are where CATs and chats live. Use them to separate projects, teams, or clients. ## What a workspace is A workspace is a container inside your organization. Each workspace has: - Its own **CATs**. - Its own **members** (drawn from your organization). - Its own **chat history** (each user sees only their own history). Think of workspaces like folders: they help you keep work separate without creating a whole new account. ## When to make a new workspace Create a new workspace when: - You want a different set of CATs for a different product or team. - You want to share a subset of your team on one project. - You're working with a client and want their materials separate. If you just want to organize your own personal CATs, you probably don't need more than one. ## Creating a workspace 1. Open the workspace switcher (top-left in the Platform app). 2. Click **New workspace**. 3. Give it a name and click **Create**. You're added as the owner automatically. Add teammates from **Workspace settings → Members**. ## Switching workspaces Use the top-left switcher at any time. Your CATs, team view, and settings update to match the current workspace. Your chat history follows you — it's tied to your user, not the workspace. ## Default workspace Every organization starts with one workspace called *Default*. You can rename it or delete it (as long as it isn't the only one left). ## Transferring a workspace to another organization If you are an **owner** or **admin** in both organizations, you can move a workspace from **Workspace settings → Danger zone → Transfer to organization**. Before the transfer completes, GeniusPro shows a preview and blocks unsafe cases: - The source organization must keep at least one other workspace. - Linked clients must be removed first (clients stay with their organization). - You must confirm by typing the workspace name. What happens on transfer: - Returnable credits go back to the source organization; remaining non-returnable credits are cleared. - Billing, funding, and auto-recharge settings are cleared. - Members who are not already in the target organization lose workspace access. - API keys attached from the source organization are detached. - CATs stay with the workspace and move to the target organization. - Historical usage and billing ledger entries remain attributed to the source organization. Both organizations' owners receive an email when the transfer completes. --- ## platform/team Source: https://docs.geniuspro.io/markdown/platform/team # Team & roles Invite teammates, assign roles, and manage who can change what. ## Inviting teammates Open **Platform → Team** and click **Invite**. Enter one or more work emails separated by commas, pick a role, and click **Send**. - They get an email link. - When they accept, they land in your organization. - They can immediately sign in and, if they have a workspace role, use the chat app and CATs. If they already have a GeniusPro account, accepting the invite just adds your organization to their list — they keep their own account. ## Roles Roles apply at two levels: | Role | Scope | Can | | --------------- | ------------- | --------------------------------------------------------------------- | | **Owner** | Organization | Everything: billing, delete org, manage all members and workspaces. | | **Admin** | Organization | Manage members, API keys, and workspaces. Cannot delete the org. | | **Member** | Organization | Sign in; join workspaces they're added to. | | **Workspace admin** | Workspace | Add/remove workspace members, manage CATs, change workspace settings. | | **Workspace member** | Workspace | Use CATs in that workspace; build their own CATs if allowed. | You can hold different roles in different workspaces. A person can be a *Member* in the org and a *Workspace admin* in one project. ## Transferring ownership From **Platform → Team**, open the menu next to a member and click **Make owner**. You'll be asked to confirm — an organization has exactly one owner at a time. ## Removing someone From **Platform → Team**, open the menu and click **Remove from organization**. They lose access immediately. Their own chat history is deleted. Any CATs they built stay in the workspace they were in, owned by that workspace. --- ## platform/clients Source: https://docs.geniuspro.io/markdown/platform/clients # Clients Track client accounts, assign teammates to them, and share CATs per-client. ## When to use clients Clients are an optional layer for agencies, consultants, and internal teams who deliver work for multiple end customers. They let you: - Keep a list of the clients you work with. - Assign which teammates work on which client. - Scope CATs to one client instead of the whole workspace. If you're not running client work, you can ignore this section entirely — you don't need to use it. ## Creating a client 1. Open **Platform → Clients**. 2. Click **New client**. 3. Enter a name, optional logo, and notes. 4. Save. The client now shows up in the **Clients** dropdown in the chat app and in the CAT builder's share settings. ## Assigning teammates From a client's page, click **Assign members** and pick the teammates who should have access. Only assigned teammates see the client's CATs and chat filters. ## Scoping a CAT to a client In the [CAT builder](/cats/building), choose **Share with: a client** and pick the client. Only assigned teammates will see it. ## Archiving a client Open the client's page and click **Archive**. Archived clients stay in your records but are hidden from the day-to-day dropdowns. You can restore them any time. --- ## platform/billing Source: https://docs.geniuspro.io/markdown/platform/billing # Plans & billing How plans, usage, upgrades, and invoices work on GeniusPro. ## How plans work GeniusPro is priced per seat plus usage. You pick a plan for the organization; each active teammate counts as one seat. Usage is measured in the tokens you send and receive across chat, CATs, and API calls — all on the same bill. - Paid plans add higher usage limits, priority support, and advanced features. - All plans get access to the same models — the plan decides limits, not capability. - Simon keeps costs down by default: small prompts use economical models; hard tasks use frontier models only when they need to. See the live plan lineup at **Platform → Billing**. It's the single source of truth for what each plan includes right now. ## Upgrading or changing plans 1. Open **Platform → Billing**. 2. Click **Change plan**. 3. Pick the new plan and confirm. Upgrades take effect immediately. Downgrades take effect at the end of your current billing period so you don't lose usage you already paid for. ## Seats A seat is one active teammate in your organization. You're billed for the peak number of active seats in a billing period. Invited-but-not-yet-accepted people don't count as seats. ## Usage Usage is measured per request: - Input tokens (what you send). - Output tokens (what the model returns). - A small markup that covers orchestration, storage, and retries. You can see your usage in real time at **Platform → Billing → Usage**. It updates within a couple of minutes of each request. ## Invoices & receipts Invoices are emailed monthly to the organization's billing email. You can download any of them at **Platform → Billing → Invoices**. Change the billing email, payment method, or company details from **Platform → Billing → Billing info**. ## Cancelling From **Platform → Billing**, click **Cancel subscription**. You keep full access until the end of the current period, then drop to the free tier. Your CATs, team, and history stay — you won't lose anything. --- ## platform/api-keys Source: https://docs.geniuspro.io/markdown/platform/api-keys # API keys Create API keys for yourself or your team, name them, rotate them, and revoke them. ## What API keys are for You need an API key to call the GeniusPro API from code, scripts, or any OpenAI-compatible SDK. API keys are tied to your **organization** — anyone on the team using the same key gets the same billing. Never commit an API key to git, never ship it in client-side code, and never paste it into a chat. ## Creating a key 1. Open **Platform → API keys**. 2. Click **Create key**. 3. Give it a descriptive name (for example: *Staging server*, *Local laptop*, *CI pipeline*). 4. Click **Create**. The key is shown **once**. Copy it somewhere safe — you won't be able to see it again. If you lose a key, create a new one and revoke the old one. ## Using a key Add it as a header on every request: ```http Authorization: Bearer gp_live_... ``` That's all you need. See [API → Authentication](/developer/authentication) for the details. ## Rotating keys safely Rotate keys any time you suspect one leaked or when a teammate leaves. The safe pattern is: 1. Create a new key. 2. Update your apps to use the new key. 3. Deploy the change. 4. Revoke the old key from **Platform → API keys**. You can have many keys active at once, so there's zero downtime — the old key works until you actively revoke it. ## Revoking a key Open the key's menu and click **Revoke**. Revocation is instant. Any app using that key starts getting **401** errors within about **10 seconds** (positive validation cache TTL). If a teammate is **removed from the organization**, their org-scoped keys stop working — they do not fall back to a personal wallet. ## Scopes and limits Each key inherits the organization's plan limits. A single key doesn't have its own rate limit — usage across all keys in the organization counts against the same monthly and per-minute limits. --- ## platform/account Source: https://docs.geniuspro.io/markdown/platform/account # Account & security Your profile, password, two-factor auth, and sign-in sessions. ## Profile Open **Platform → Account** to set: - Display name. - Profile picture. - Default workspace to open after sign-in. These apply everywhere you use GeniusPro — platform, chat, and any tool built on the API. ## Password & sign-in Change your password from **Platform → Account → Security**. If you signed up with Google, you can add a password there too, so you can sign in with either. ## Two-factor authentication Enable 2FA from **Platform → Account → Security**. Scan the QR code with any authenticator app (1Password, Authy, Google Authenticator). Save the recovery codes somewhere safe — they're the only way back in if you lose your device. Organization admins can require 2FA for all members from **Platform → Settings → Security**. ## Active sessions See every device you're signed in on at **Platform → Account → Sessions**. If something looks unfamiliar, click **Sign out** next to it. To sign out everywhere, click **Sign out of all devices**. ## Deleting your account From **Platform → Account → Danger zone**, click **Delete account**. This removes your user, your chat history, and any CATs you personally own. If you're the owner of an organization, you have to transfer ownership or delete the organization first. This is a safety check so no company ever accidentally loses its workspace because someone closed their own account. --- ## chat/overview Source: https://docs.geniuspro.io/markdown/chat/overview # Chat overview The GeniusPro chat app — everyday AI at chat.geniuspro.io. Same account as Platform, one bill. ## What the chat app is The **chat app** at [chat.geniuspro.io](https://chat.geniuspro.io) is GeniusPro's **command center** — a full workspace, not only a message box. Your assistant **Ainslie** lives here: typed chat, live voice, navigation across the product, plus Canvas, studios, documents, goals, and billing in one sidebar. It uses the **same login** as [platform.geniuspro.io](https://platform.geniuspro.io). Usage counts toward your organization's plan. **Models** still use Simon slugs (`simon-says`, `simon-says-chat`, …) in the picker; **Ainslie** is the assistant experience wrapped around them. ## How it works today (by design) This is intentional — not a preview of a different product later. | Piece | Role | | ----- | ---- | | **Simon** | The **model** layer — slugs like `simon-says` and `simon-says-chat` power completions behind chat. | | **Ainslie** | The **copilot** — persona, voice, navigation, knowledge context, and in-chat actions (studios, canvas, search). You drive; she assists. | | **My Goals** | Your **outcomes roadmap** — Ainslie shapes headlines, outcomes, and next steps from your business context and saved goals. Refresh when you want an updated view; she does not run goals unattended. | | **My Work** | Your **review inbox** — saved runs and artifacts to open, approve, or send back. Not a background fleet executing tasks while you are away. | Think **Jarvis-style UI with a teammate**, not a silent autonomous operator. Ask Ainslie to open Goals or Work, talk through setup on My Goals, or start work in chat and find the results under My Work when a run is saved. ## Chat vs Platform vs API | You want to… | Go here | | ------------ | ------- | | Ask questions, draft copy, review files | **Chat** — [chat.geniuspro.io](https://chat.geniuspro.io) | | Invite teammates, billing, API keys, org settings | **Platform** — [platform.geniuspro.io](https://platform.geniuspro.io) | | Call GeniusPro from your product or scripts | **API** — [developer docs](/developer/overview) | ## What's in the sidebar | Section | Pages | What it's for | | ------- | ----- | ------------- | | **Chat** | New chat, My Chats | Talk to Ainslie; browse, pin, and summarize past threads. | | **Plan & Track** | My Goals, My Work | Outcomes roadmap (you + Ainslie) and saved runs to review — see [how it works today](#how-it-works-today-by-design) on this page. | | **My Studio** | Canvas, Image, Video | Writing, images, and video generation. | | **Knowledge** | My Documents, My Knowledge | File library and sources Ainslie can ground on. | | **Business** | My Business, My Team, My Integrations | Brand context, teammates, connected tools. | | **Account** | Profile, Billing, AI Settings, Settings | You, credits, how Ainslie behaves, preferences. | Full detail: [Ainslie & the command center](/chat/ainslie). You do not need every area on day one. Start with **New chat** and **My Chats**. ## Models and CATs in one place Above the message box, the **model menu** lists: - **Simon** — `simon-says` and self-upgrading slugs like `simon-says-chat` (recommended default). - **Your CATs** — custom workflows your team built (see [CATs](/cats/overview)). - **Direct slugs** — specific models when you need them (see [Models](/developer/models)). Pick the model **before** you send. Changing model mid-thread starts fresh context for that conversation. ## Next - [Ainslie & the command center](/chat/ainslie) — everything Ainslie and the app can do. - [First conversation](/chat/getting-started) — five-minute walkthrough. - [Everyday tips](/chat/everyday) — attachments, voice, history, workspaces. - [Build a CAT](/cats/getting-started) — turn a great prompt into something the whole team can reuse. --- ## chat/ainslie Source: https://docs.geniuspro.io/markdown/chat/ainslie # Ainslie & the command center What Ainslie can do in the chat app — chat, voice, navigation, studios, knowledge, goals, billing, and more. ## Who is Ainslie? **Ainslie** is your assistant inside [chat.geniuspro.io](https://chat.geniuspro.io). She answers in **typed chat** and **live voice**, can **open pages for you**, and works across the command center — not only on the New chat screen. You still choose a **model** or **CAT** from the menu (`simon-says`, `simon-says-chat`, `cat:your-slug`, …). **Simon** powers the reply; **Ainslie** is how GeniusPro presents the teammate — navigation, voice, page context, and command-center actions. Customize how she behaves under **My AI Settings** (display name, instructions, avatar look for chat and voice previews). ## Copilot today — not autopilot GeniusPro is built around a **modern command center** with Ainslie as your intelligent teammate: - **You stay in the loop** — conversations, refreshes on My Goals, and reviews on My Work happen when you engage them. - **Ainslie moves fast with you** — open pages, draft in Canvas, generate in studios, search the web, attach files, continue in voice from almost anywhere. - **Plan & Track is where outcomes and deliverables live** — not a separate autonomous agent hiding in the background. That is the product today. Deeper automation belongs in **CATs** and the **API** when you want repeatable workflows in code. ## Talk to Ainslie ### Typed chat (New chat) - Streamed replies, **edit** a past user message and resend, **regenerate** an answer, **fork** a thread from an earlier turn, or **retry** after a failed reply. - **Attach files** (paperclip) and **images** on the same message. - **Context** control on the composer: send **Recent**, **All**, or **Custom** messages from the thread so long chats stay within limits. - **Slash commands:** `/clear` (empty the box and attachments), `/model ` (switch model quickly). ### Live voice - Click the **microphone** on New chat (or continue a thread in voice where supported). - Talk naturally; Ainslie replies in audio. End the session when you are done (or say goodbye — she can end the call). - After a session, review it under **Voice transcripts** (duration, cost, full turn-by-turn text). Voice and language defaults: **Account** (credits, voice picker, language, mic/VAD tuning) and **My AI Settings**. ### Ask Ainslie to open a page In **chat or voice**, you can ask to go somewhere in the app — for example: - "Open My Billing" / "Go to Canvas" / "Show my goals" / "Open voice transcripts" Ainslie confirms and navigates. Same destinations work in **typed chat** (you see a short ack, then the page opens) and **voice**. | Destination | What you get | | ----------- | ------------ | | New chat | Fresh conversation workspace (home). | | My Chats | History — search, pin, archive, summarize, resume. | | Canvas Studio | Notes, outlines, drafts linked to sessions. | | Image / Video Studio | Generate visuals; ask Ainslie for creative direction before generating. | | My Documents | Upload and browse files. | | My Knowledge | Sources Ainslie uses for grounded answers. | | My Goals | Outcomes roadmap — Ainslie builds the live view from your business and goals; use voice or chat here during setup. | | My Work | Saved runs and artifacts — search, filter, approve or request changes. | | My Business | Brand name, logo, colors — context for the assistant. | | My Team / My Integrations | Teammates and connected tools. | | My Billing / Top up | Balance, invoices, add credits. | | Usage | Token and cost summary, charts, ledger preview. | | Account | Credits on profile, voice, language, live-call mic settings. | | My AI Settings | Assistant name, instructions, avatar character and background. | | Voice transcripts | Past voice sessions. | ### Ainslie while you work elsewhere On most pages, Ainslie can stay available in a **side dock** or **floating bubble** so you do not have to return to New chat for a quick question. Expand or minimize the panel from the header; on small screens the dock may open as a full-screen sheet. ## Create and manage work | Area | What you can do | | ---- | ---------------- | | **Canvas Studio** | Write and store documents (briefs, scripts, outlines). Start from chat or open saved Canvas work; use written briefs before Image/Video Studio. | | **Image Studio** | Generate campaign art, mockups, thumbnails; refine prompts; **Ask Ainslie** before generating. | | **Video Studio** | Generate clips from prompts; set duration/resolution; billing-aware history. | | **My Documents** | Central file library — upload, filter, open. | | **My Knowledge** | Add sources, check indexing status, tune what Ainslie may cite. | | **My Goals** | Outcomes and checklists — Ainslie proposes what matters and what to do next; you refresh the page view when you want an update. Onboarding quests live here when you are new. | | **My Work** | Every saved run in one place — open artifacts, checkpoints, and feedback without digging through chat history. | ## My Chats (history) Beyond "open an old thread": - **Search and filter** long lists. - **Pin** important threads. - **Archive** or restore. - **Rename** a conversation. - **Summarize** a transcript with AI. - **Resume** in the chat dock or full New chat view. ## Business and account (in the app) Same org as Platform — many tasks you can do without leaving chat: - **My Team** — invites and roles (deeper policy: [Platform → Team](/platform/team)). - **My Integrations** — connect external tools. - **My Billing** and **Top up** — prepaid credits and Stripe checkout. - **Usage** — spend and model breakdown for chat (and related) usage. - **My Profile** and **Settings** — account controls. ## What Ainslie does not do (by design) - **Run your business while you are offline** — no always-on autonomous operator across Goals and Work. - **Replace API keys and server integration** → [Platform → API keys](/platform/api-keys) and [API docs](/developer/overview). - **Replace team CATs** → [CATs builder](/cats/getting-started) on Platform (then pick the CAT in chat for repeatable workflows). - **Replace org-wide admin** → [platform.geniuspro.io](https://platform.geniuspro.io). ## Quick paths | I want to… | Go to | | ---------- | ----- | | First message | [Getting started](/chat/getting-started) | | Files, models, workspaces | [Everyday tips](/chat/everyday) | | Team CAT in chat | [Using a CAT](/cats/using) | | Voice API details | [API → Voice](/developer/voice) | --- ## chat/getting-started Source: https://docs.geniuspro.io/markdown/chat/getting-started # Your first conversation Open the chat app, send a message with simon-says, and know where to go next. ## Before you start You need a GeniusPro account. If you do not have one yet, follow [Platform → Getting started](/platform/getting-started) first. ## 1. Open the chat app Go to [chat.geniuspro.io](https://chat.geniuspro.io) or click **Open chat** from the Platform header. You should land on **New chat** with Ainslie ready — no separate setup wizard required. If you are new to the wider app, see [Ainslie & the command center](/chat/ainslie). ## 2. Pick a model (or keep the default) Click the **model name** above the message box. - **Not sure?** Choose **Simon** (`simon-says`) — it picks the best fit for each message. - **Writing or Q&A?** Choose **Simon Chat** (`simon-says-chat`). - **Code?** Choose **Simon Coding** (`simon-says-coding`). The menu groups models so you are not scrolling through a flat list. ## 3. Send your first message Type a real task, not just "hello" — for example: > Summarize our refund policy in five bullets for a customer email. Press **Enter** or click the send arrow. The reply streams in as it is generated. ## 4. Try a follow-up in the same thread Ask something that refers to the last answer, for example: > Make the tone warmer and shorter. The assistant keeps context for that conversation until you start **New chat**. ## 5. Open an old thread In the sidebar, click **My Chats**. Search or scroll, open a thread, and continue where you left off. Chat history is **private to you** — teammates do not see your personal threads. See [Platform → Workspaces](/platform/workspaces) for how workspace data is shared. ## 6. Optional: voice Click the **microphone** on the message bar to talk with Ainslie live (when enabled on your plan). Try asking her to **open My Chats** or **go to Image Studio** — she can navigate for you. See [Ainslie & the command center](/chat/ainslie) for voice transcripts, docked chat on other pages, and the full destination list. ## What to do next | Goal | Next step | | ---- | --------- | | Attach a PDF or image | [Everyday tips → Files](/chat/everyday#attach-files) | | Use a team CAT | [CATs → Using a CAT](/cats/using) | | Invite a colleague | [Platform → Team](/platform/team) | | Call from code | [API → Quickstart](/developer/getting-started) | --- ## chat/everyday Source: https://docs.geniuspro.io/markdown/chat/everyday # Everyday tips Attachments, voice, history, workspaces, and model choice — the chat features people use most. ## Attach files {#attach-files} Click the **paperclip** on the message bar (or drag files in) to add PDFs, images, or other supported files. Tips: - One message can include **text plus files** — e.g. "Summarize this deck" with a PDF attached. - Large files may take a moment to upload; wait for the attachment chip to appear before sending. - For huge files or reuse across many messages, consider the [API Files](/developer/files) flow in code; in chat, attachments are per message or thread depending on context settings. ## Images Use the image control when you want to add pictures without a document workflow. Good for screenshots, diagrams, and "what is in this photo?" questions. ## Choose the right model Quick guide: | Task | Start with | | ---- | ---------- | | General work, not sure | `simon-says` | | Writing, email, summaries | `simon-says-chat` | | Code | `simon-says-coding` | | Legal, finance, PM-style depth | Matching **expert** slug (e.g. `simon-says-lawyer`) | | Your team's workflow | A **CAT** from the model menu | | Exact third-party behavior | A **direct** slug from [Models](/developer/models) | Switching models **mid-conversation** clears context for that thread — start **New chat** if you change specialization. ## Use a CAT from chat 1. Open the model menu. 2. Find your CAT under **My CATs** or **Workspace CATs**. 3. Send messages as usual. Details: [CATs → Using a CAT](/cats/using). ## Voice When your plan includes voice: 1. Open **New chat** (or an existing thread you want to continue in voice). 2. Click the **microphone** on the composer. 3. Allow the browser to use your mic if prompted. 4. Click again to end the session. Pick voice quality in **My AI Settings** if your org exposes standard vs quality tiers. ## History and search - **My Chats** lists your past threads, newest first. - **Pin**, **archive**, **rename**, or run **Summarize** on a thread from history. - Use search when you have many threads. - Deleting a thread is permanent — export anything you need to keep elsewhere first. More: [Ainslie & the command center](/chat/ainslie) (My Chats section). ## Slash commands In the message box, type: - `/clear` — clear text and attachments. - `/model simon-says-coding` (or any slug you have) — switch model without opening the menu. ## Ask Ainslie to navigate Examples: "Open my billing", "Go to canvas", "Show usage". Works in typed chat and voice. Full list: [Ainslie & the command center](/chat/ainslie). ## Ainslie on other pages On Canvas, Studio, Documents, and most other routes, use the **side panel** or **floating bubble** to chat without leaving your work. ## Workspaces and clients If your company uses **workspaces** or **clients**, switch them from the workspace control (usually top of the app). That changes which CATs appear and how usage is grouped — not your personal chat login. Read [Workspaces](/platform/workspaces) and [Clients](/platform/clients) on the Platform side. ## Settings worth knowing | Setting | Where | | ------- | ----- | | Default model | **My AI Settings** | | Profile and password | **My Profile** / **Settings** (same account as Platform) | | Usage and plan | **My Billing** or Platform → Billing | ## When chat is not the right tool - **Automating** a product → [API](/developer/overview). - **Comparing many models on one prompt** → [Studio](/studio/overview) (beta). - **Publishing a reusable prompt + steps** → [CATs](/cats/getting-started). ## Stuck? - No access to chat → confirm your invite and org role with an admin ([Team](/platform/team)). - Model missing from the menu → your plan or workspace may not include it; check [Models](/developer/models) or ask an admin. - API keys and secrets belong on the server — never paste them into chat ([API keys](/platform/api-keys)). --- ## cats/overview Source: https://docs.geniuspro.io/markdown/cats/overview # CATs overview CATs are your custom AI workflows — a prompt, a model, optional chained steps, and Tiger Mode for long-running runs. ## What a CAT is A CAT — **Custom AI Transformer** — is a saved AI workflow that you build. Each CAT is made of: - A **system prompt** that defines how it should behave. - A **model** that powers it — pick any GeniusPro slug or a self-upgrading Simon name. - Optional **KITTNs** — extra steps that run in order and pass results forward. - Optional **Tiger Mode** — durable execution for CATs that take more than a minute. Once saved, a CAT has a slug. You can use it like any other model: pick it in the chat app, or call it over the API as `cat:your-slug`. ## Why you'd build one - **Consistency.** Stop pasting the same long prompt every time. - **Sharing.** Teammates pick your CAT instead of reinventing the prompt. - **Workflows.** Chain multiple steps — research, then draft, then review. - **Durability.** Put long-running workflows in Tiger Mode so they survive failures and restarts. - **Model choice.** Lock the CAT to `simon-says` (let Simon pick) or to a specific slug. ## A quick example A simple *Meeting summarizer* CAT might be: - **Prompt:** "You summarize meeting transcripts into bullet points: decisions, owners, deadlines." - **Model:** `simon-says-chat`. - **KITTNs:** none — a single-step CAT. A more advanced *Blueprint extractor* CAT might be: - **KITTN 1:** extract room names and dimensions from an uploaded PDF. - **KITTN 2:** cross-check with local building codes. - **KITTN 3:** output structured JSON. - **Tiger Mode:** on — each KITTN persists its output so a retry doesn't start from scratch. Both are CATs. The difference is just how many steps you want, how durable the run needs to be, and how structured the output has to look. ## Next - [Getting started](/cats/getting-started) — build your first CAT. - [How CATs work](/cats/how-it-works) — KITTNs, chaining, and context. - [Tiger Mode](/cats/tiger-mode) — durable execution for long-running CATs. --- ## cats/getting-started Source: https://docs.geniuspro.io/markdown/cats/getting-started # Getting started Build your first CAT in under ten minutes. ## 1. Open the CAT builder From the platform sidebar, click **CATs → New CAT**. You'll land in the builder. ## 2. Name it Pick a clear name like *Email rewriter* or *Blog outline*. The builder turns it into a slug automatically — for example, `email-rewriter`. You'll use that slug to call it later. ## 3. Write a system prompt This is the most important step. Tell the CAT: - **What it is.** ("You are an email rewriter.") - **What it should do.** ("Rewrite the user's email to be shorter, warmer, and more direct.") - **What it should not do.** ("Don't invent new information. Keep names and numbers unchanged.") - **How it should answer.** ("Respond only with the rewritten email — no preamble, no explanation.") Short and specific beats long and vague. Three or four lines is often enough. ## 4. Pick a model Start with `simon-says`. Simon looks at the prompt and picks the best fit. If you want a specific job, pick a named slug like `simon-says-chat` or `simon-says-coding` — the slug stays stable while quality improves over time. See the full list at [API → Models](/developer/models). ## 5. Test it Use the **Test** pane on the right. Paste a sample input and click **Run**. Adjust the system prompt until the output looks right for a few different inputs. ## 6. Save and share Click **Save**. You have two choices: - **Use it yourself** — it's available in the chat app and over the API immediately. - **Share it** — open [Sharing CATs](/cats/sharing) for your options. That's the whole loop. Name → prompt → model → test → save. --- ## cats/how-it-works Source: https://docs.geniuspro.io/markdown/cats/how-it-works # How CATs work KITTNs, chaining, context, and what happens in one call. ## One CAT, one call When someone calls your CAT — either from the chat app or over the API — one request comes into GeniusPro and one response goes back. What happens in the middle depends on how the CAT is built. If your CAT is a single step, the request: 1. Adds your system prompt. 2. Adds the user's message. 3. Sends it to the model you picked. 4. Returns the model's answer. That's a one-step CAT. Simple, fast, and enough for most cases. ## KITTNs (multi-step CATs) A **KITTN** — short for **Knowledge Input To Transform Node** — is one step inside a CAT. When you add more than one KITTN, they run in order and pass results forward. For example, a two-KITTN *Research brief* CAT might: 1. **KITTN 1 — Research.** Search the web and summarize the top results. 2. **KITTN 2 — Format.** Turn the research into a structured brief with headings. The output of KITTN 1 is automatically available to KITTN 2. You don't have to wire anything up by hand. ## Context Every KITTN sees: - The original user message. - The outputs of every KITTN that ran before it. - The CAT's overall system prompt. That's it. There's no hidden state — what you see in the builder is what the CAT knows. ## Streaming and long-running CATs If your CAT takes more than a couple of seconds, it streams updates back. In the chat app, you see progress in real time. Over the API, you get a stream of events. See [API → Using CATs](/developer/cats). For CATs that can take more than a minute — multi-step research, batch processing, long agent loops — turn on **Tiger Mode**. Runs persist to disk step-by-step, so if a step fails or your worker crashes, the CAT resumes from the last completed step instead of starting over. See [Tiger Mode](/cats/tiger-mode). ## When to add a KITTN vs. make a second CAT Add a KITTN when the steps really belong together — they always run in the same order on the same input. Make a separate CAT when you want a different *entry point* that someone can pick directly. Small and composable beats one giant CAT with every option. --- ## cats/building Source: https://docs.geniuspro.io/markdown/cats/building # Building a CAT Everything you can configure when designing a CAT — prompt, model, steps, and testing. ## The system prompt The system prompt is the set of instructions your CAT always runs with. Good system prompts are: - **Specific.** "Rewrite in a warm, direct tone" beats "write better". - **Constrained.** Tell it what not to do and what not to say. - **Format-aware.** If you want bullets, say so. If you want JSON, say exactly what shape. A useful structure is: ``` You are a . Goal: . Guidelines: - - - Output format: . ``` ## Picking a model | Goal | Start with | | ---------------------------- | ------------------------------- | | Let Simon decide | `simon-says` | | General writing and chat | `simon-says-chat` | | Coding and refactors | `simon-says-coding` | | Fast, cheap, simple tasks | `simon-says-coding-speed` | | Blueprint / drawing analysis | `simon-says-architecture-pro` | You can switch the model any time — just re-save. The system prompt stays. See [API → Models](/developer/models) for the full list. ## Adding KITTNs Click **Add step** to add a KITTN. Each KITTN has its own: - Short name. - Optional per-step prompt (stacks on top of the CAT's system prompt). - Model (you can mix models — use a fast one to classify, a strong one to generate). - Optional tools (web search, file reading). Re-order KITTNs by dragging. Delete them with the menu. ## Tools Some models support tools: - **Web search** — the model can pull in fresh info from the web. - **File read** — the model can read attachments a user sent. - **Code execution** — the model can run short Python snippets. Toggle tools on the model or KITTN where you want them. Tools cost a little more per call and can add latency, so only turn them on if the CAT needs them. ## Testing The right pane of the builder is a scratch chat against your CAT. Use it to: - Try three or four very different inputs. - Try an input you *know* is bad — do you get a sensible refusal? - Check the output format matches what your downstream code or team expects. Iterate on the prompt, not on the test cases. If a test fails, the prompt is (almost always) the fix. ## Versioning Every save creates a new version. Open the version history to compare previous prompts, restore an old one, or diff two versions. Published CATs always resolve to the latest saved version unless you pin a version in the share settings. --- ## cats/sharing Source: https://docs.geniuspro.io/markdown/cats/sharing # Sharing CATs Pick who can use your CAT — just you, your workspace, a specific client, or anyone with a link. ## Four ways to share Every CAT has a **Share with** setting: - **Only me** — private. Useful while you're still experimenting. - **Workspace** — everyone in the workspace sees it in the model picker. - **Client** — only teammates assigned to that client see it. See [Clients](/platform/clients). - **Link** — generate an unlisted share link. Anyone with the link and an API key in your organization can use it. Change the setting any time from the CAT's **Share** tab. Access is re-checked on every request, so revoking is instant. ## What a teammate sees When you share with a workspace or a client: - They see the CAT in the chat app's model dropdown. - They can call it over the API as `cat:your-slug`. - They can't edit it unless you add them as a co-editor. ## Co-editors From **Share → Co-editors**, pick teammates who should be able to edit the CAT's prompt, model, or KITTNs. Edits are versioned, so you can always roll back. ## Usage attribution Every call to a shared CAT is billed to the organization the caller is in (so, you). You'll see it in **Platform → Billing → Usage** split by CAT and by user. ## Renaming and unsharing Rename a CAT any time — the slug updates automatically. Unshare it by switching **Share with** to **Only me**; teammates lose access right away. Deleting a CAT is permanent and removes all its versions and history. --- ## cats/tiger-mode Source: https://docs.geniuspro.io/markdown/cats/tiger-mode # Tiger Mode Durable execution for long-running CATs. Runs persist progress, survive failures, and resume from the last completed step. ## What Tiger Mode is Tiger Mode is how GeniusPro runs CATs that take **more than about a minute**. Instead of holding an HTTP request open and losing everything if something fails, a Tiger run: - Persists every KITTN's input and output to disk as it goes. - Returns a `run_id` immediately and runs in the background. - Automatically retries failed steps (with backoff) instead of starting the whole CAT over. - Resumes from the last completed step if the worker restarts, your network blips, or a step errors. Think of it as "make this CAT a durable workflow" — the thing orchestrators like Temporal or Inngest do — but built into the platform. ## When to turn it on Turn Tiger Mode on for a CAT when any of these are true: - The CAT has steps that take a long time (long research, big document analysis, heavy generation). - The CAT runs for **longer than 60 seconds** end to end. - You're running the CAT in a batch job or from a background worker and you want durability. - You want to be able to kill the client and check back later. Leave it off for interactive CATs that finish in a few seconds — the extra persistence isn't worth it. ## Turning it on In the CAT builder, open **Settings → Execution mode** and pick **Tiger Mode**. Save. Every new run of that CAT now uses durable execution; anything already in flight finishes in whatever mode it started. ## What a Tiger run looks like Kick it off like any CAT, with `mode: "tiger"`: ```bash curl https://api.geniuspro.io/v1/cats/research-brief/runs \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "input": { "topic": "US tariffs, 2026" }, "mode": "tiger" }' ``` You get back: ```json { "id": "run_abc", "status": "queued" } ``` You can poll, listen on SSE, or check the **Runs** tab in the builder. See [API → Using CATs](/developer/cats) for the full shape. ## What happens on failure - If a KITTN fails, Tiger retries the *step* with exponential backoff (up to a configurable limit). - If the retries are exhausted, the whole run is marked failed and you can inspect which step broke and why in the **Runs** tab. - If the run hits the worker ceiling for the plan, Tiger pauses it and queues it to resume — it doesn't lose progress. ## Observability Each run keeps: - The input to every KITTN. - The raw model output from every KITTN. - The retry count and reason for any failures. - The user or API key that triggered it. Open **Platform → CATs → [your CAT] → Runs** to inspect any run. Useful when a teammate says "my CAT returned something weird" — open that run and you can see exactly which step did it. --- ## cats/using Source: https://docs.geniuspro.io/markdown/cats/using # Using a CAT Call your CAT from the chat app or from any API client — same slug, same behavior. ## From the chat app 1. Open [chat.geniuspro.io](https://chat.geniuspro.io) — see [Chat → Getting started](/chat/getting-started) if you are new to the app. 2. Click the model menu above the message box. 3. Pick your CAT (listed under **My CATs** or **Workspace CATs**). 4. Chat normally. The CAT's system prompt is applied on every message in that conversation. Switching models mid-conversation restarts the context. ## From the API Use the CAT's slug with the `cat:` prefix as the model name: ```bash curl https://api.geniuspro.io/v1/chat/completions \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "cat:email-rewriter", "messages": [ { "role": "user", "content": "Rewrite this: ..." } ] }' ``` Everything else — streaming, tool use, file attachments — works the same as any model. See [API → Using CATs](/developer/cats) for more. ## Streaming long-running CATs For multi-step CATs, add `"stream": true` (or `"progress_updates": true` for an SSE progress channel). You'll get progress events as each KITTN runs, then the final answer. ## Switching CAT versions By default, callers get the latest saved version. To pin a version for a specific app, pass `cat:your-slug@v12` as the model name. ## Debugging a CAT in production If a CAT is misbehaving for a teammate: 1. Open the CAT in the builder. 2. Click **Runs** — you'll see the last several calls anonymised by user. 3. Open one, see which KITTN produced what, and what the final output was. 4. Adjust the prompt, re-test, and save. --- ## studio/overview Source: https://docs.geniuspro.io/markdown/studio/overview # Studio overview Simon's cockpit — design prompts, compare models, ship to the API. ## What Studio is Studio is the workspace for building and testing AI on GeniusPro before you ship it. It's where you: - Run any prompt against `simon-says`, any self-upgrading `simon-says-*` slug, or any direct model slug. - Compare the **same prompt across multiple frontier models side by side** — see the output, cost, and latency of each. - Tune **temperature**, **max tokens**, and **thinking mode**. Watch cost update live before you run. - Define **structured outputs** with a JSON schema, or wire up **tools** the model can call. - Hit **Open in API** to copy the exact same call as curl, Python, or Node — paste it into your code. - When a prompt is good enough to ship, **promote it to a CAT** in one click. ## How Studio relates to the rest of GeniusPro - **Platform** — your org, team, billing, API keys. Unchanged. - **CATs** — shipped, versioned, shareable AI workflows. Studio is where you **design** them. CATs are where you **ship** them. - **API** — the OpenAI-compatible endpoint. Every Studio run is a real API call on your account — exportable as code with one click. Think of it as: *Studio is where you experiment. CATs are where you ship. The API is where it all runs.* ## Private beta Studio is rolling out in a private beta to existing GeniusPro organizations. If you want early access, email **support@geniuspro.io** or ask your account owner. ## In the meantime - Start with the API — [API → Quickstart](/developer/getting-started). - Build a CAT — [CATs → Getting started](/cats/getting-started). - Browse the three ways to call a model — [API → Models](/developer/models). --- ## developer/overview Source: https://docs.geniuspro.io/markdown/developer/overview # API overview One OpenAI-compatible API. Every frontier model, one key, one bill. ## What the API is for The GeniusPro API lets you call every major AI model — and every CAT your team has built — from your own code, through a single OpenAI-compatible endpoint. Instead of signing contracts with OpenAI, Anthropic, Google, and xAI separately, you get: - **One API key.** - **One invoice.** - **One endpoint** — `https://api.geniuspro.io/v1`. - **US-based AI providers only.** And on top of that, you get **Simon** — GeniusPro's model picker that routes each request to the right capability for the job. ## The three ways to call a model Every call uses the same `POST /v1/chat/completions` endpoint. What you put in `model` decides what happens: 1. **`"simon-says"`** — let Simon choose. Simon reads the task (chat, code, vision, long documents, reasoning, …) and picks the best fit. Good default when you just want the best answer. 2. **`"simon-says-chat"`, `"simon-says-coding"`, `"simon-says-architecture"`, …** — self-upgrading named models. The slug never changes; quality improves over time without edits to your integration. Good when you want a **stable contract** in your code with always-current capability. 3. **`"claude-opus-4-8"`, `"gpt-5.4"`, `"gemini-3.1-pro"`, …** — call a specific model directly. Same endpoint, same auth, same SDK. Good when you need a specific model's exact behavior. ## Shape of a request ```bash curl https://api.geniuspro.io/v1/chat/completions \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "simon-says", "messages": [ { "role": "user", "content": "Hello!" } ] }' ``` ## What you can do - **Chat** — `POST /v1/chat/completions` for text, images, files, tools, streaming. - **Models** — `GET /v1/models` lists everything your key can call (Simon, named models, direct slugs, your CATs). - **Files** — `POST /v1/files` uploads a PDF or image once; reference it later by `file_id`. - **Voice** — `POST /v1/audio/speech` (TTS), `POST /v1/audio/transcriptions` (STT), `POST /v1/realtime/sessions` + WebSocket for two-way voice. - **Video** — `POST /v1/videos` for async video generation (not chat completions). - **CATs** — call any `cat:your-slug` as the model name. Tiger Mode handles long-running ones. ## What this section covers This is the public integration guide. Admin, webhook, and billing-export endpoints exist but aren't documented here. If you need one of those, email **support@geniuspro.io**. ## Next - Using the browser instead of code? Start at [Chat](/chat/overview). - [Quickstart](/developer/getting-started) — your first request. - [Authentication](/developer/authentication) — API keys and headers. - [Errors, limits & routing](/developer/errors-limits) — status codes, usage fields, which endpoint to call. - [Models](/developer/models) — the three ways, every ID. --- ## developer/getting-started Source: https://docs.geniuspro.io/markdown/developer/getting-started # Quickstart Your first request — in curl, Python, and Node. ## 1. Get an API key Follow [Platform → API keys](/platform/api-keys) to create one. Keep it somewhere safe. ```bash export GENIUSPRO_API_KEY=gp_live_... ``` ## 2. Send your first request The default model is `simon-says`. Simon will pick the best model for whatever you send. ### curl ```bash curl https://api.geniuspro.io/v1/chat/completions \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "simon-says", "messages": [ { "role": "user", "content": "Say hello in one sentence." } ] }' ``` ### Python (OpenAI SDK) ```python from openai import OpenAI client = OpenAI( api_key=os.environ["GENIUSPRO_API_KEY"], base_url="https://api.geniuspro.io/v1", ) resp = client.chat.completions.create( model="simon-says", messages=[{"role": "user", "content": "Say hello in one sentence."}], ) print(resp.choices[0].message.content) print(resp.usage) # includes billed_cost_usd on GeniusPro ``` ### Node (OpenAI SDK) ```ts import OpenAI from "openai"; const client = new OpenAI({ apiKey: process.env.GENIUSPRO_API_KEY, baseURL: "https://api.geniuspro.io/v1", }); const resp = await client.chat.completions.create({ model: "simon-says", messages: [{ role: "user", content: "Say hello in one sentence." }], }); console.log(resp.choices[0].message.content); ``` ## 3. Stream the response Add `stream: true` and read events as they arrive: ```python stream = client.chat.completions.create( model="simon-says", messages=[{"role": "user", "content": "Stream me a short poem."}], stream=True, ) for event in stream: print(event.choices[0].delta.content or "", end="", flush=True) ``` ## 4. Pick a specific job When you know the task, call a named model directly: ```python client.chat.completions.create( model="simon-says-coding", # self-upgrading coding model messages=[{"role": "user", "content": "Write a binary search in Python."}], ) ``` ## 5. Call one of your CATs Replace the model with `cat:your-slug`: ```python client.chat.completions.create( model="cat:email-rewriter", messages=[{"role": "user", "content": "Rewrite this: ..."}], ) ``` That's the whole quickstart. Everything else — images, files, voice, tools, long-running CATs with Tiger Mode — is a variation on these basics. --- ## developer/authentication Source: https://docs.geniuspro.io/markdown/developer/authentication # Authentication How API keys, headers, and rotation work. ## The header Every request needs one of these headers: ```http Authorization: Bearer gp_live_... ``` Or, if your client doesn't support `Authorization`: ```http X-API-Key: gp_live_... ``` Both are identical — use whichever your framework makes easier. ## Getting a key Create one at **Platform → API keys**. See [API keys](/platform/api-keys) for the walk-through. The key is shown exactly once. If you lose it, revoke it and create a new one. ## Key format - **Live keys** start with `gp_live_`. - **Test keys** start with `gp_test_` (if your plan includes a sandbox). Treat both as secrets. Don't commit them, don't ship them in front-end code, and don't log them. ## Error codes | Status | Meaning | | ------ | ----------------------------------------------------------- | | 401 | Key missing, revoked, malformed, or the user is no longer an active member of the key's organization. | | 402 | Insufficient API credits for this request (wallet balance too low). | | 403 | Your key is valid but not allowed to use that model or CAT. | | 429 | Rate limited — back off and retry with exponential delay. | | 503 | Auth lookup temporarily unavailable — retry; do not treat as a revoked key. | Revoked keys stop working immediately, but a successfully validated key may be cached for up to **10 seconds** before revocation takes effect. Org-scoped keys only work while the key owner has an **active** `organization_members` row. If someone is removed from the org, their org-scoped keys return **401** (not a silent fallback to a personal wallet). See [Errors, limits & routing](/developer/errors-limits) for validation errors, streaming aborts, and which endpoint each model type expects. ## Rotation To rotate safely: 1. Create a new key. 2. Deploy the new key alongside the old one. 3. Revoke the old key. Multiple keys can be active at once. See [API keys](/platform/api-keys) for the full flow. ## CORS The API does not accept browser-side requests with an API key. Your API key should live on a server — call GeniusPro from your backend and proxy results to your front-end. If you need a browser-callable surface, let us know — we're working on a scoped browser-token flow. --- ## developer/errors-limits Source: https://docs.geniuspro.io/markdown/developer/errors-limits # Errors, limits & routing HTTP status codes, usage fields, streaming behavior, and which endpoint each model type expects. ## HTTP status codes | Status | When you see it | What to do | | ------ | ----------------- | ---------- | | **400** | Invalid JSON, validation failure, wrong endpoint for the model (e.g. voice model on chat completions). | Read the `error.message` — it usually names the correct endpoint. | | **401** | Missing/invalid API key, revoked key, or key owner no longer in the org. | Rotate the key; confirm the user is still an active org member. | | **402** | Insufficient API credits for this request or session. | Top up at **Platform → Billing**; check `usage` in **Platform → Billing → Usage**. | | **403** | Key is valid but cannot access that model or CAT. | Check plan, CAT sharing, and `GET /v1/models`. | | **409** | Conflict on a create (e.g. duplicate CAT slug). | Pick a different slug or update the existing resource. | | **413** | Request body exceeds the size limit (100 MB on chat). | Shrink the payload or upload large files via [`/v1/files`](/developer/files). | | **429** | Organization or endpoint rate limit. | Exponential backoff; usage is shared across all keys in the org. | | **502 / 503** | Upstream or auth dependency temporarily down. | Retry with backoff; quote `x-request-id` if it persists. | Error bodies follow OpenAI's shape: `{ "error": { "message": "…", "type": "…", "code": "…" } }`. Upstream provider errors are **sanitized** — you will not receive raw OpenAI/Anthropic/Google error payloads. ## Usage and billing fields Sync responses and the final streaming `usage` chunk include GeniusPro billing metadata: ```json { "usage": { "prompt_tokens": 120, "completion_tokens": 45, "total_tokens": 165, "prompt_tokens_details": { "cached_tokens": 0 }, "billed_cost_usd": 0.000412 } } ``` - **`billed_cost_usd`** — what GeniusPro charged your organization for that request (after markup). This is the number to log for cost attribution. - Token-based chat models are marked up **+15%** over upstream provider cost unless documented otherwise for a modality (embeddings, TTS, transcription, premium voice, and image generation use their own rate cards). - When the upstream reports an actual dollar cost (e.g. OpenRouter), that cost is authoritative for billing — cache and reasoning tokens are included automatically. Platform usage dashboards at **Platform → Billing → Usage** lag API responses by a couple of minutes. ## Streaming behavior With `stream: true` on `POST /v1/chat/completions`: 1. You receive OpenAI-compatible `chat.completion.chunk` events. 2. A final chunk includes `usage` with `billed_cost_usd`. 3. The stream ends with `data: [DONE]`. **Mid-stream credit guard (API keys):** if your organization's API credits drop below what is needed to continue, the server **aborts the stream** and emits an error event with a **402**-class message. You will not receive a full completion without sufficient balance. ## Endpoint routing Use this table before picking an endpoint: | You want… | Endpoint | Example `model` | | --------- | -------- | ----------------- | | Chat, tools, vision, CATs | `POST /v1/chat/completions` | `simon-says`, `cat:my-slug`, `claude-opus-4-8` | | Batch text-to-speech | `POST /v1/audio/speech` | `simon-says-tts` | | Batch transcription | `POST /v1/audio/transcriptions` | `simon-says-transcribe` | | Realtime two-way voice | `POST /v1/realtime/sessions` → WebSocket to `ws_url` | `simon-says-voice-standard` | | Video generation (async) | `POST /v1/videos` | `simon-says-video` | | List models | `GET /v1/models` | — | | Public catalog (no key) | `GET /v1/models/catalog` | — | Sending a realtime voice slug to chat completions returns **400** with `code` pointing you to `POST /v1/realtime/sessions`. Sending a video slug to chat completions returns **400** pointing to `POST /v1/videos`. ## Request size limits | Limit | Value | | ----- | ----- | | Chat request body | 100 MB | | Single file upload | 50 MB | | Messages per chat request | 200 | | Active files per user | 100 | | File retention | 7 days | Filenames uploaded via `/v1/files` are sanitized server-side (path segments and unsafe characters stripped). ## Rate limits Rate limits apply at the **organization** level, not per key. All active keys in the org share the same per-minute and monthly caps for your plan. Realtime session mint (`POST /v1/realtime/sessions`) has its own per-user throttle. If the limiter backend is briefly unavailable, mint may still succeed (fail-open) — abuse is monitored separately. ## Tracing Every response includes `x-request-id` (ULID). Realtime mint responses also echo `request_id` in the JSON body. Include it when contacting **support@geniuspro.io**. --- ## developer/models Source: https://docs.geniuspro.io/markdown/developer/models # Models Every GeniusPro model slug you can call — experts, task slugs, specialists, direct slugs, plus your CATs. Authoritative live list at /v1/models/catalog. ## Authoritative machine-readable list Before anything else, the authoritative list of every publicly callable GeniusPro model slug lives here — **no API key required**: - **Live JSON catalog:** [`https://api.geniuspro.io/v1/models/catalog`](https://api.geniuspro.io/v1/models/catalog) - **Per-key list (includes your CATs):** `GET /v1/models` with your API key. If an AI tool told you a GeniusPro model slug "doesn't exist," fetch the catalog URL above. It is the live source of truth and refreshes every few minutes. The docs page you're reading now tracks it, but the JSON endpoint wins if they ever disagree. The catalog is grouped into the same four tiers this page uses (plus **CATs**, which are per API key and never appear in the public JSON): 1. **Experts** — professional-role `simon-says-*` slugs (finance, legal, PM, etc.). 2. **Task orchestrators** — `simon-says` and family slugs tuned for a job (chat, coding, voice, vision, …). 3. **Specialists** — one slug per task pattern, tuned for that pattern. 4. **Direct** — specific model slugs when you need exact, provider-named behavior. ```bash curl https://api.geniuspro.io/v1/models/catalog ``` Returns: ```json { "base_url": "https://api.geniuspro.io", "counts": { "experts": 10, "orchestrators": 24, "benchmarked": 17, "direct": 40, "total": 91 }, "experts": [ { "id": "simon-says-finance", "category": "reasoning", "types": [] } ], "orchestrators": [ { "id": "simon-says", "category": "orchestrator", "types": [] }, { "id": "simon-says-coding", "category": "coding", "types": [] } ], "benchmarked": [ { "id": "simon-says-math", "category": "reasoning", "types": ["benchmark"] }, { "id": "simon-says-logic", "category": "reasoning", "types": ["benchmark"] } ], "direct": [ { "id": "gpt-5.4", "category": "chat", "types": [] }, { "id": "claude-opus-4-8", "category": "coding", "types": [] }, { "id": "gemini-3.1-pro", "category": "chat", "types": [] }, { "id": "grok-3", "category": "chat", "types": [] }, { "id": "sam3", "category": "vision", "types": [] } ], "updated_at": "…", "links": { "authoritative_api": "…", "human_docs": "…", "llms_txt": "…", "openapi": "…", "discovery": "…" } } ``` Numbers move as models are added or retired. Always refetch rather than caching hardcoded slugs. ## Tier 1 — Experts (professional roles) These `simon-says-*` slugs are **independently callable** — same `POST /v1/chat/completions` body as every other model. GeniusPro applies domain discipline (live-data verification rules, uncertainty contracts, and specialist system framing where configured) so they behave like a finance analyst, lawyer, PM, etc., not a generic chatbot. | Slug | What it's for | | ---- | ------------- | | `simon-says-finance` | Markets, corporate finance, valuation workflows (live figures require tool verification). | | `simon-says-lawyer` | Legal reading and analysis (not a substitute for licensed counsel). | | `simon-says-accountant` | Accounting reasoning and financial statement questions. | | `simon-says-analyst` | Structured business / data analysis. | | `simon-says-pm` | Product management drafting and prioritization. | | `simon-says-sales` | Sales messaging and outreach. | | `simon-says-marketing` | Marketing copy and campaigns. | | `simon-says-teacher` | Instructional explanations. | | `simon-says-architecture` | Systems and software architecture reasoning. | | `simon-says-architecture-pro` | Deeper architecture review. | The live catalog endpoint returns every expert slug currently in rotation — fetch [`/v1/models/catalog`](https://api.geniuspro.io/v1/models/catalog) for the authoritative list. ## Tier 2 — Task slugs (self-upgrading) ``` model: "simon-says" ``` Send any request to `simon-says` and Simon picks the best fit for that prompt. Hard prompts may use more than one model — you'll see that reflected in usage. Named **task** slugs are tuned for a specific **family of tasks** instead of per-prompt picking: | Slug | What it's for | | -------------------------------- | -------------------------------------------------------- | | `simon-says` | General auto-router. When in doubt, send here. | | `simon-says-chat` | Chat, Q&A, summaries, writing. | | `simon-says-coding` | Everyday code generation and refactors. | | `simon-says-coding-speed` | Fastest coding answers. | | `simon-says-coding-balanced` | Middle ground between speed and quality. | | `simon-says-coding-quality` | Highest-quality coding answers. | | `simon-says-coding-super` | Long, hard coding problems with big contexts. | | `simon-says-reasoning` | Analysis, research, structured thinking. | | `simon-says-design` | Creative, UX, marketing copy. | | `simon-says-agents` | Multi-step agent workflows. | | `simon-says-image` | Image generation. | | `simon-says-vision` | Image understanding and OCR. | | `simon-says-voice` | Realtime two-way voice (alias for `simon-says-voice-standard`). | | `simon-says-voice-standard` | Realtime voice — standard quality. | | `simon-says-voice-quality` | Realtime voice — highest quality. | | `simon-says-tts` | Batch text-to-speech (`POST /v1/audio/speech`). | | `simon-says-transcribe` | Batch speech-to-text (`POST /v1/audio/transcriptions`). | **The slugs never change.** Capability behind each slug improves as we ship updates. Your code doesn't. Use this tier when you want a **stable contract in your code** with always-current models. ## Tier 3 — Specialists Same `simon-says-*` family, but each slug is **tuned for one task pattern** (math, SQL, long documents, …) instead of per-prompt picking. Use when you know the task and want a fixed specialist slug. | Slug | What it's for | | -------------------------------- | ---------------------------------------------------- | | `simon-says-math` | Arithmetic, algebra, symbolic math. | | `simon-says-logic` | Structured logical reasoning puzzles. | | `simon-says-long-docs` | Reading and summarizing long documents. | | `simon-says-terminal` | Producing shell commands / terminal workflows. | | `simon-says-sql` | SQL analysis and generation. | The live catalog endpoint returns every specialist slug currently available; the list above is illustrative. Fetch [`/v1/models/catalog`](https://api.geniuspro.io/v1/models/catalog) for the current list. ## Tier 4 — Direct model slugs Call these when you need a specific model's exact behavior or want to match an external benchmark. Same `POST /v1/chat/completions` endpoint, same auth, same SDK — the `model` field is the provider slug (for example `gpt-5.4`, `claude-opus-4-8`). - **OpenAI:** `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.3-codex`, `gpt-5.2`, `gpt-4o`, `gpt-4o-mini`. - **Anthropic:** `claude-opus-4-8`, `claude-opus-4-7`, `claude-opus-4.6`, `claude-sonnet-4.6`, `claude-sonnet-4.5`, `claude-haiku-4.5`. - **Google:** `gemini-3.1-pro`, `gemini-3-flash-preview`, `gemini-2.5-pro`. - **xAI:** `grok-3`. - **Vision:** `sam3` — SAM 3 image segmentation. Exact slugs available to your key depend on your plan — call `GET /v1/models` for your live list, or [`GET /v1/models/catalog`](https://api.geniuspro.io/v1/models/catalog) for the full public universe. ## CATs Every CAT your key can reach is callable as `cat:`. CATs are user- and workspace-specific so they live in `GET /v1/models` (authenticated), not in the public catalog. See [Using CATs](/developer/cats). ## Context & limits Model-specific context windows, max image sizes, and output lengths are returned by `GET /v1/models`. Starting points: - **Request body limit:** 100 MB. - **`/v1/files` individual file limit:** 50 MB. - **Max messages per request:** 200. If you exceed a limit you get a 413 (body too big) or a 400 with the specific limit that was exceeded. ## Endpoint routing (important) Not every model slug works on `POST /v1/chat/completions`. If you send the wrong combination, you get a **400** with a pointer to the right surface: | Model type | Call instead | | ---------- | ------------ | | Realtime voice (`simon-says-voice-*`) | `POST /v1/realtime/sessions`, then open the returned `ws_url`. See [Voice](/developer/voice). | | Batch TTS (`simon-says-tts`) | `POST /v1/audio/speech` | | Batch STT (`simon-says-transcribe`) | `POST /v1/audio/transcriptions` | | Video (`simon-says-video*`) | `POST /v1/videos` | Full status-code reference: [Errors, limits & routing](/developer/errors-limits). ## For AI agents reading this page If you're an AI assistant helping a developer integrate GeniusPro and you need to verify a model slug exists or list available models, fetch the JSON catalog directly — it is the source of truth: - [`https://api.geniuspro.io/v1/models/catalog`](https://api.geniuspro.io/v1/models/catalog) — public, unauthenticated, CORS-open, cacheable. - [`https://api.geniuspro.io/openapi.json`](https://api.geniuspro.io/openapi.json) — full OpenAPI spec. - [`https://api.geniuspro.io/`](https://api.geniuspro.io/) — discovery index linking all of the above. --- ## developer/clients Source: https://docs.geniuspro.io/markdown/developer/clients # SDKs & clients GeniusPro is OpenAI-compatible. Use the OpenAI SDK, LangChain, LiteLLM, the Vercel AI SDK, or plain HTTP. ## OpenAI SDK Works in every major language. Point it at our base URL: **Python** ```python from openai import OpenAI client = OpenAI( api_key=os.environ["GENIUSPRO_API_KEY"], base_url="https://api.geniuspro.io/v1", ) ``` **Node / TypeScript** ```ts import OpenAI from "openai"; const client = new OpenAI({ apiKey: process.env.GENIUSPRO_API_KEY, baseURL: "https://api.geniuspro.io/v1", }); ``` From there, every method — `chat.completions.create`, `files.create`, `audio.speech.create`, streaming, tool calls — works the same as it does against OpenAI. The only thing that changes is the model name. ## LangChain ```python from langchain_openai import ChatOpenAI llm = ChatOpenAI( model="simon-says", api_key=os.environ["GENIUSPRO_API_KEY"], base_url="https://api.geniuspro.io/v1", ) ``` Same pattern: `base_url` + GeniusPro key + a GeniusPro model name. ## LiteLLM ```python import litellm resp = litellm.completion( model="openai/simon-says", messages=[{"role": "user", "content": "Hello!"}], api_key=os.environ["GENIUSPRO_API_KEY"], api_base="https://api.geniuspro.io/v1", ) ``` ## Vercel AI SDK ```ts import { createOpenAI } from "@ai-sdk/openai"; const geniuspro = createOpenAI({ apiKey: process.env.GENIUSPRO_API_KEY, baseURL: "https://api.geniuspro.io/v1", }); const { text } = await generateText({ model: geniuspro("simon-says"), prompt: "Say hello", }); ``` ## Plain HTTP Any language that can POST JSON works: ```bash curl https://api.geniuspro.io/v1/chat/completions \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "simon-says", "messages": [{ "role": "user", "content": "Hi" }] }' ``` ## Streaming All of the above support streaming with the OpenAI-compatible `stream: true` flag. No extra configuration. Streamed responses include a final `usage` chunk with `billed_cost_usd` (your GeniusPro charge for that request). If your organization's API credits run out mid-stream, the server stops the stream and emits an error event — see [Errors, limits & routing](/developer/errors-limits). --- ## developer/files Source: https://docs.geniuspro.io/markdown/developer/files # Files Upload a PDF or image once, reference it by file_id in chat requests. Bypasses body-size limits. ## When to use files Use the Files API when: - Your attachment is bigger than fits inline (tens of MB of PDF, high-resolution images). - You want to send the same file to multiple turns or multiple CATs without re-uploading. - You want the model to read a native PDF — all pages, in one context. Small one-off images are fine inline. Everything else goes through `/v1/files`. ## Limits - **Max file size:** 50 MB. - **Active files per user:** 100. - **Retention:** 7 days, then auto-deleted. - **Allowed types:** PDF, PNG, JPEG, WebP, GIF, TXT, Markdown, CSV, JSON. ## Upload flow Three steps (same shape as OpenAI's Files API): 1. **Register** — `POST /v1/files` with filename, mime type, and purpose. Returns a signed URL. 2. **Upload** — `PUT` the bytes to the signed URL. No auth header needed. 3. **Complete** — `POST /v1/files/{id}/complete` to mark the file ready. ### Step 1 — register ```bash curl https://api.geniuspro.io/v1/files \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "filename": "blueprint.pdf", "mime_type": "application/pdf", "purpose": "user_data" }' ``` Response: ```json { "id": "file-abc123", "status": "pending", "upload_url": "https://...signed...", "upload_method": "PUT", "upload_headers": { "Content-Type": "application/pdf" } } ``` ### Step 2 — upload bytes ```bash curl -X PUT "$UPLOAD_URL" \ -H "Content-Type: application/pdf" \ --data-binary @blueprint.pdf ``` ### Step 3 — complete ```bash curl -X POST https://api.geniuspro.io/v1/files/file-abc123/complete \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" ``` ## Using the file in a chat Reference it from any `user` message part: ```json { "model": "simon-says-architecture-pro", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Summarize this blueprint." }, { "type": "file", "file_id": "file-abc123" } ] } ] } ``` Images work the same way — use `{ "type": "image_url", "image_url": { "url": "file://file-abc123" } }` if you want the explicit image path, or the same `file` part above. ## Listing, fetching, deleting - `GET /v1/files` — list your files. - `GET /v1/files/{id}` — one file's metadata. - `DELETE /v1/files/{id}` — remove it early. All three require your API key. --- ## developer/voice Source: https://docs.geniuspro.io/markdown/developer/voice # Voice Text-to-speech, speech-to-text, and realtime two-way voice via session mint + WebSocket. ## Voice model slugs | Slug | Surface | What it's for | | ---- | ------- | ------------- | | `simon-says-voice-standard` | Realtime | Two-way voice — standard quality. Default for chat voice. | | `simon-says-voice-quality` | Realtime | Two-way voice — highest quality. | | `simon-says-voice` | Realtime | Alias for `simon-says-voice-standard`. | | `simon-says-tts` | `POST /v1/audio/speech` | Batch text-to-speech (one-shot audio file). | | `simon-says-transcribe` | `POST /v1/audio/transcriptions` | Batch speech-to-text. | Realtime models **cannot** be called through `POST /v1/chat/completions`. Batch TTS/STT models **cannot** be used for realtime WebSocket sessions. See [Models → Endpoint routing](/developer/models#endpoint-routing-important). ## Text-to-speech (batch) Turn text into audio. Pick a voice id from `GET /v1/audio/voices` (or any voice shown in the chat app): ```bash curl https://api.geniuspro.io/v1/audio/speech \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "simon-says-tts", "voice": "alloy", "input": "Hello, this is GeniusPro." }' \ --output out.mp3 ``` Response is an audio stream (`audio/mpeg` by default). Change the format with `"response_format": "wav"` or `"opus"`. Python: ```python resp = client.audio.speech.create( model="simon-says-tts", voice="alloy", input="Hello, this is GeniusPro.", ) resp.stream_to_file("out.mp3") ``` If your wallet cannot cover the charge, the request returns **402** before any audio is returned. ## Speech-to-text (batch) Transcribe audio: ```bash curl https://api.geniuspro.io/v1/audio/transcriptions \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -F file=@meeting.mp3 \ -F model=simon-says-transcribe ``` Response: ```json { "text": "Full transcript of the audio..." } ``` Add `"response_format": "verbose_json"` for timestamped segments, or `"language": "en"` to lock the language. ## Voices List available voices at `GET /v1/audio/voices`. Voices are shared between the chat app and the API. ## Limits - **Per file:** 25 MB audio upload. - **Per TTS request:** 4,000 characters of input. - **Formats accepted for STT:** mp3, mp4, m4a, wav, webm, ogg. ## Realtime (two-way voice) Realtime is a **two-step** flow: mint a short-lived session over HTTPS, then open a WebSocket to the returned `ws_url`. ### 1. Mint a session ```bash curl -X POST https://api.geniuspro.io/v1/realtime/sessions \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "simon-says-voice-standard", "voice": "alloy", "instructions": "You are a concise assistant." }' ``` | Field | Required | Notes | | ----- | -------- | ----- | | `model` | Yes | `simon-says-voice-standard`, `simon-says-voice-quality`, or `simon-says-voice`. | | `voice` | No | Must be on the model's allow-list; omit for the model default. | | `instructions` | No | System persona, max 8,000 characters. PII-scrubbed before storage and upstream. | **Credit floor:** your organization needs at least **$0.50** in API credits to mint. Otherwise you get **402**. Example response: ```json { "provider": "openai", "model": "simon-says-voice-standard", "upstream_model": "gpt-realtime-mini", "session_id": "sess_…", "token": "rts_…", "value": "rts_…", "ws_url": "wss://realtime.geniuspro.io/v1/realtime?model=simon-says-voice-standard", "expires_at": "2026-07-01T12:10:00.000Z", "voice": "alloy", "request_id": "01J…" } ``` - **Use the exact `ws_url` returned** — do not hardcode a host. - **`token` is single-use** and expires in about **10 minutes** (`expires_at`). - **`value`** is a legacy alias for `token` (same string). - Quote `request_id` (or the `x-request-id` response header) in support tickets. ### 2. Open the WebSocket **Server-side** (Node, Python workers, etc.) — send the token on the upgrade: ```http GET /v1/realtime?model=simon-says-voice-standard HTTP/1.1 Host: realtime.geniuspro.io Authorization: Bearer rts_… Upgrade: websocket ``` **Browsers** cannot set arbitrary headers on `WebSocket`. Pass the token via `Sec-WebSocket-Protocol` instead of putting it in the URL: ```ts const protocols = [`token.${session.token}`]; const ws = new WebSocket(session.ws_url, protocols); ``` Appending `?token=rts_…` to the URL still works for backward compatibility but is **deprecated** — tokens in URLs leak via logs, proxies, and referrers. Prefer `Authorization` (servers) or `Sec-WebSocket-Protocol: token.` (browsers). ### 3. Wire protocol After connect, speak the **OpenAI Realtime** client event format (`session.update`, `input_audio_buffer.append`, `response.create`, …). GeniusPro's proxy translates to the upstream provider (OpenAI or Google) based on the model you minted. Billing for the session is reconciled when the WebSocket closes (audio/text token usage). A small prepay is reserved at mint time. ## Troubleshooting | Symptom | Likely cause | | ------- | ------------- | | **401** on mint | Invalid or revoked API key, or key owner removed from the org. | | **402** on mint | Wallet below the $0.50 realtime floor. | | **400** on mint | Unknown model slug, disallowed `voice`, or `instructions` over 8,000 chars. | | **401** on WebSocket | Expired token, token already used, or wrong auth method for your client. | | **400** on chat completions with a voice model | Wrong surface — mint with `POST /v1/realtime/sessions` instead. | See [Errors, limits & routing](/developer/errors-limits) for the full status-code table. --- ## developer/cats Source: https://docs.geniuspro.io/markdown/developer/cats # Using CATs Call your custom CATs as models — same endpoint, same SDKs, one extra prefix. Long-running CATs use Tiger Mode. ## How it works Every CAT is addressable as a model ID: ``` cat: ``` So if your CAT is named *Email rewriter* (slug: `email-rewriter`), you call it like this: ```python client.chat.completions.create( model="cat:email-rewriter", messages=[{"role": "user", "content": "Rewrite this: ..."}], ) ``` Streaming, files, images — all work identically to calling a regular model. ## Pinning a version By default a CAT resolves to its latest saved version. To pin: ``` model: "cat:email-rewriter@v12" ``` Pinning is a good idea for production. Bump the version deliberately when you roll out a prompt change. ## Streaming progress from multi-step CATs Multi-step CATs can stream progress events while each step runs. Add `progress_updates: true`: ```json { "model": "cat:research-brief", "progress_updates": true, "stream": true, "messages": [{ "role": "user", "content": "Brief me on ." }] } ``` You get events in this shape: ```json { "type": "progress", "step": "research", "message": "Searching the web..." } { "type": "progress", "step": "format", "message": "Drafting brief..." } { "type": "complete", "output": "..." } ``` Clients that don't understand progress events can safely ignore them — the final chat completion still comes through. ## Long-running CATs (Tiger Mode) If a CAT can take more than ~60 seconds — long research, big batch processing, multi-step workflows — run it in **Tiger Mode**. Instead of blocking an HTTP request, Tiger Mode persists progress, survives failures, and lets you poll for status. Start a run: ```bash curl https://api.geniuspro.io/v1/cats/research-brief/runs \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "input": { "topic": "US tariffs, 2026" }, "mode": "tiger" }' ``` Response: ```json { "id": "run_abc", "status": "queued" } ``` Poll: ```bash curl https://api.geniuspro.io/v1/cats/research-brief/runs/run_abc \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" ``` Or listen on the SSE stream at `/v1/cats//runs//events`. Runs are durable: if a step fails or your worker restarts mid-run, the CAT resumes from the last completed step instead of starting over. See [CATs → Tiger Mode](/cats/tiger-mode) for the concept. ## Debugging - `GET /v1/models` shows every CAT your key can call. - The CAT builder at **Platform → CATs → [your CAT] → Runs** shows every recent call and what each step produced. - If a CAT returns a 403, your key doesn't have access — check the CAT's **Share** tab. ## Organizing access CATs are shared at the workspace or client level (see [Sharing CATs](/cats/sharing)). An API key can call any CAT its organization can see. --- ## developer/security Source: https://docs.geniuspro.io/markdown/developer/security # Security & privacy No training on API traffic, PII scrubbed from logs by default, opt-in edge scrubbing via X-GP-Scrub-Prompt, TLS in transit, encryption at rest. ## TL;DR - **No training on your data.** GeniusPro never uses your prompts or responses to train any model. Models reachable through the API run on commercial terms that do not train on customer API traffic. - **PII scrubbed from logs by default.** Emails, phone numbers, SSNs, Luhn-valid credit cards, IPv4/IPv6 addresses, and API-key-shaped tokens are masked with typed markers (`` etc.) before any prompt or response is persisted. - **Opt-in edge scrubbing.** Send `X-GP-Scrub-Prompt: true` (or `scrub_pii: true` in the body) to have PII scrubbed *before* the request is forwarded to the model. - **TLS 1.2+ in transit.** Encryption at rest for all persisted data. API keys stored as salted SHA-256 hashes. - **Compliance.** SOC 2 Type II + ISO 27001 covered across every link in our stack today. HIPAA BAA available on the enterprise tier — currently operating in production for enterprise customers. Canonical public-facing policy: [https://geniuspro.io/security](https://geniuspro.io/security). ## Opt-in edge PII scrubbing By default we scrub PII from **our own logs and stored rows**, but the prompt still reaches the model intact — many legitimate workflows (resume parsing, customer-email summarization, contact extraction) need PII in the request. When you don't need that, flip one flag and PII is removed at the GeniusPro edge *before* the model ever sees it. ### Header ```bash curl https://api.geniuspro.io/v1/chat/completions \ -H "Authorization: Bearer $GENIUSPRO_API_KEY" \ -H "X-GP-Scrub-Prompt: true" \ -H "Content-Type: application/json" \ -d '{ "model": "simon-says", "messages": [ { "role": "user", "content": "Summarize this lead: Alice Chen, alice@example.com, 415-555-1212." } ] }' ``` ### Body flag ```ts const resp = await client.chat.completions.create({ model: "simon-says", messages: [{ role: "user", content: "Summarize this lead: Alice Chen, alice@example.com, 415-555-1212." }], scrub_pii: true, }); ``` Either path is equivalent; use whichever fits your stack. The substitution markers are ``, ``, ``, ``, ``, ``, and ``. ## What's scrubbed from logs (default-on) | Type | Regex class | Marker | |---|---|---| | Email | RFC-5322 conservative | `` | | US phone | `(xxx) xxx-xxxx` and variants | `` | | SSN | `xxx-xx-xxxx` | `` | | Credit card | 13–19 digits, Luhn-valid | `` | | IPv4 | RFC-791 | `` | | IPv6 | RFC-4291 | `` | | API key | Common prefixes + JWT shape | `` | This applies to chat history, long-term memory, realtime session instructions, and simon-says-dev review rows. ## Compliance - **SOC 2 Type II / ISO 27001 — covered across the stack today.** Database, application hosting, voice services, and model access for compliance-sensitive traffic run on infrastructure with current attestations. No extra paperwork needed for standard routing. - **HIPAA — available on the enterprise tier under signed BAAs.** HIPAA-covered workspaces are wired so every link in the chain — model access and data storage — carries a signed BAA. Currently operating in production for enterprise customers. We share the specific vendor chain under NDA during onboarding and security-questionnaire review, not on public surfaces. ## Machine-readable proofs Every control on this page is advertised to AI agents and procurement crawlers via: - `GET https://api.geniuspro.io/` — `security` block with all controls + compliance posture. - `GET https://api.geniuspro.io/openapi.json` — `x-security-policy` extension. - `GET https://api.geniuspro.io/.well-known/ai-plugin.json` — `security_policy_url` + security clause in `description_for_model`. - `GET https://docs.geniuspro.io/llms.txt` — linked inline. ## Contact - Policy questions or enterprise compliance setup: [https://geniuspro.io/#invite](https://geniuspro.io/#invite). - Vulnerability reports: **security@geniuspro.io**. --- ## developer/ai-usage Source: https://docs.geniuspro.io/markdown/developer/ai-usage # AI usage policy Rules for AI agents, crawlers, and retrieval-augmented systems reading GeniusPro public surfaces. OK to summarize/link/cite; not OK to copy verbatim, train on, or harvest PII from. ## Who this applies to If you are an AI agent, LLM-backed crawler, retrieval-augmented assistant, coding agent, or any automated system that fetches content from `geniuspro.io`, `docs.geniuspro.io`, or `api.geniuspro.io`, these rules apply to every request you make. Canonical public-facing policy: [https://geniuspro.io/ai-usage](https://geniuspro.io/ai-usage). ## The four rules ### 1. OK: read, summarize, link, and cite — with attribution GeniusPro publishes a discovery index, an OpenAPI spec, `ai-plugin.json`, `llms.txt`, JSON-LD on every marketing page, and a public model catalog at `https://api.geniuspro.io/v1/models/catalog` specifically so AI agents can learn the surface and cite correct model slugs. Summarizing and linking back to canonical URLs is welcome. ### 2. Not OK: verbatim copying without attribution Do not paste prose, code samples, or docs text verbatim into responses unless you include a visible citation to the canonical URL. If a user asks for an exact quote, include a link they can verify. ### 3. Not OK: training foundation models on GeniusPro content Do not use GeniusPro marketing copy, documentation, code samples, API specifications, model catalog entries, or structured data for any gradient-updating process — pre-training, continued pre-training, supervised fine-tuning, RLHF, DPO, distillation, etc. — without written permission (`legal@geniuspro.io`). Retrieval-augmented generation at query time is fine as long as output respects rule 2 (attribution) and rule 4 (PII). ### 4. Not OK: collecting or redistributing PII from public surfaces Any personally identifiable information that appears on a GeniusPro surface (contact emails, names in bios, etc.) is published so humans can reach us, not for bulk extraction. Treat any such value as out-of-scope for caching, embedding, or republishing. ## What about data I send to the API? That is covered by the separate [Security & privacy](/developer/security) policy, not this AI-usage policy. In short: customer data sent to `api.geniuspro.io/v1` is never used to train any model, is PII-scrubbed from our logs by default, and can be further scrubbed at the edge via `X-GP-Scrub-Prompt` before it is forwarded to a model. ## Attribution format Link to the canonical URL for the fact you are citing: - Model existence: [https://api.geniuspro.io/v1/models/catalog](https://api.geniuspro.io/v1/models/catalog) - Pricing and availability: [https://geniuspro.io/models](https://geniuspro.io/models) - Security posture: [https://geniuspro.io/security](https://geniuspro.io/security) - This policy: [https://geniuspro.io/ai-usage](https://geniuspro.io/ai-usage) Never invent model slugs, pricing, or capabilities we do not publish. ## Where this policy is advertised Same rules are exposed in every place AI agents look: - `GET https://docs.geniuspro.io/llms.txt` — `## AI usage policy` section with bulleted rules. - `GET https://api.geniuspro.io/` — `ai_usage` block with `ok[]`, `not_ok[]`, and `permission_contact`. - `GET https://api.geniuspro.io/.well-known/ai-plugin.json` — `ai_usage_policy_url` field + inline clause in `description_for_model`. - `GET https://api.geniuspro.io/openapi.json` — `x-ai-usage-policy` extension. - JSON-LD `CreativeWork` + `FAQPage` on [https://geniuspro.io/ai-usage](https://geniuspro.io/ai-usage). ## Enforcement We actively monitor for verbatim republishing and for training-dataset inclusion of GeniusPro content. When we discover a violation we start with a removal request to the platform owner, escalate to DMCA or the equivalent regional takedown process, and reserve all other legal remedies available to us. ## Contact - Permission requests: **legal@geniuspro.io**. - Security incidents or responsible-disclosure reports: **security@geniuspro.io**.