Welcome to Cloud Score

Your application sends its requests to Cloud Score instead of to a provider. For every request, Cloud Score scans the prompt for sensitive content, works out what kind of task it is, finds the enabled models that can do it, applies your policies and budgets, checks whether the answer is already in its cache, picks the winning model on cost, speed, and quality, runs it with retries and failover, checks the answer, and records exactly what happened and what it cost.

You manage all of that from the Cloud Score admin app: which providers are connected, which models may compete, the rules that shape each decision, and the keys your applications use.

Every request runs the same sequence of stations. You will meet these names on the Playground's Route board and in every request's detail in Observability.

A request ends in one of three recorded states: completed when a model answered or a cached answer was served, blocked when a policy, a budget, or AI Security refused it, and failed when Cloud Score tried and could not deliver.

Each account is its own workspace. Overview and Playground sit above the Analytics, Gateway, Agents and Admin groups. This is what each is for. See The sidebar for every entry.