SDK overview

Prego exposes HTTP APIs that your team can call from browser apps, backend services, or automation. This page is an orientation for integrators; for request paths and payloads, start from the API overview and My AI API as needed.

Common setups

• Web applications — Your frontend calls Prego using the same sign-in your users already have (tokens or cookies as configured). Keep secrets on the server; call Prego from a backend when handling privileged operations.
• Server-side jobs — Scheduled reports, imports, or integrations run from your infrastructure using service credentials your administrator provisions.
• AI assistants via MCP — For connecting assistants to Prego through the Model Context Protocol, see MCP Hub overview.

Practices we recommend

• Scope by environment — Use non-production tenants or sandboxes while building and testing.
• Rotate credentials — Plan for API key or token rotation with your admin team.
• Respect rate limits — Back off and batch work when the API signals throttling.

Next steps

• API overview — Base URLs and authentication.
• My AI API — Knowledge, Autopilot, and chat-style flows.
• Quick start — First steps for developers and optional private stacks.
• Authentication guide — How users and services authenticate to Prego.