Use REST when you need stable, well-defined endpoints for traditional integrations (dashboards, scheduled reports). Use GraphQL when your client needs flexible, query-driven access (specific fields, deeply nested data). Use MCP when you're building AI agents that need to call tools through the standard Model Context Protocol.

All three share the same authentication, rate limiting, and data model. You can mix and match in the same integration.

Rate limits are applied per subscription tier (free / standard / premium) at the gateway.

For GraphQL specifically, requests are also evaluated for query cost using node quantifiers — large or deeply nested queries cost more, regardless of how many physical requests you send.

Your application is provisioned with access to a specific list of schools at onboarding. To add additional schools, request a quota change through your partner support channel. The list is reflected in the schools claim of your JWT and enforced at the API layer.