The AUMO provider

The AUMO provider is the only one that doesn't depend on you bringing an account. Instead of registering an external service's credential, the organization requests access and AUMO provides it.

For platform users, the result is identical: it shows up in the Providers list like any other, and its models are assigned to workspaces the same way.

How access is granted

The flow has two ends and isn't completed on your side alone:

1. Your organization requests the AUMO provider.
2. The request stays pending until someone on the AUMO side approves it.
3. On approval, the quotas and the enabled models are defined.
4. The organization syncs the provider, and the approved models start showing up.

While the request is pending, the provider doesn't serve calls. There is nothing to adjust on your end in the meantime.

Negotiated quotas

Unlike your own account, where the ceiling is your contract with the vendor, the AUMO provider comes with limits defined at approval time.

These limits are independent of the Quotas you configure on the platform. Your quotas split consumption among workspaces and people; the negotiated limit is the external ceiling, above all of that.

A quota refusal can therefore come from two sources: your own cap on the platform or the limit agreed with AUMO.

Enabled models

The list of models the AUMO provider offers is defined at approval, not by you. If an expected model doesn't show up when assigning to a workspace, the way forward is to talk to AUMO, not to look for a setting on the platform.

Some internal features require specific AUMO models. The platform's Chat Agent, for example, only accepts AUMO models with vision capability.

Next steps

• Register your own accounts with other services in Register a provider.
• Split consumption among teams in Quotas.