Enterprise evaluation
Discuss the controls your team needs to assess.
Security
Understand how workspace authentication, tool permissions, key handling and source boundaries fit into an Aroai evaluation.
Aroai tools are available through an authenticated workspace. Authorization is checked by the server when a client discovers and calls a tool; display annotations are not access controls.
OAuth sign-in binds a client to a selected workspace. API keys are workspace credentials with configured scopes. Store keys in protected client credentials, rotate exposed secrets and revoke keys that are no longer needed.
A tool may call an external data provider or calendar utility. Check each tool's source, access requirements, cost and returned fields. A country or industry pack does not itself grant third-party access.
Review your client policy, data classification, permitted source use, vendor requirements and workspace operating process before using Aroai with sensitive information.
Discuss the controls your team needs to assess.
Review OAuth and API-key setup.
Report a suspected security issue to [email protected] with a concise description. Do not include credentials or unrelated personal data.
Local intelligence. Ready to build.
Connect a compatible client, choose a workflow and review the source fields that come back.