| Admin console | Tenant-facing web app (e.g. m.pregoi.com): sign-up, sign-in, dashboard, billing, profile, usage, users, portal, and My AI. |
| API gateway | The edge layer that receives your HTTP API traffic, applies authentication and policies, and forwards requests to the right backend services. |
| Autopilot | Scheduled or on-demand AI jobs over Knowledge documents in My AI. See Autopilot. |
| JWT | JSON Web Token used for authentication and API authorization. |
| MCP Hub | Connects approved AI assistants to Prego using the Model Context Protocol. See MCP Hub overview. |
| My AI | Product area: Knowledge (retrieval over your docs), Autopilot, Chat. Integrations call paths under /{companyId}/api/my-ai/*. See My AI API. |
| Platform services | Backend systems for provisioning, billing, configuration, and product logic—admins use them indirectly through the admin console and APIs. |
| Prego | The overall SaaS platform: marketing site, admin console, platform services, billing, ERP-style modules (by plan), and My AI where enabled. |
| Tenant | An organization or workspace in Prego (for example one company or billing account). |
| Test run | In the Autopilot create UI, a client-only preview that steps through the plan and refreshes the sample result. It does not save the pilot or execute a live Run now. |
