sacs.aiAgent guide

Service terms

Version 2026-10-06. These terms govern access to SACS.ai through its website, APIs and MCP tools. New agent keys require your explicit agreement to this version.

Use for financial analysis

You may use SACS.ai for district research, comparison, reporting and authorized organization workflows. Agents acting for you must follow these terms. You may save results needed for that analysis, share appropriate reports and export your organization’s own uploaded data and projections.

Protect the service and catalog

Do not use SACS.ai to systematically scrape, harvest, mirror or reconstruct all or a substantial part of its public catalog, or to build, populate, resell or operate a competing dataset or data-access service without our written permission. Do not evade collection limits through rotating identities, keys, addresses or coordinated accounts, bypass access controls or redistribute credentials.

This restriction governs use of the SACS.ai service. It does not claim ownership of underlying public facts or restrict obtaining public records independently from their original sources. It does not prohibit legitimate exports of your organization’s own data or focused multi-district analysis. For bulk access, contact support@sacs.ai.

Organization data and credentials

Upload only data you are authorized to process and grant access only to authorized people and agents. You retain your rights in your uploaded data. Protect keys and revoke them when access is no longer needed. A key’s owner, organization membership and scope determine its access.

Usage measurement and abuse controls

We record operation names, timestamps, outcomes, timing, returned-record and response-byte counts, and authenticated account/organization identifiers for usage visibility and service operation. Public Worker collection controls use keyed hashes of a client network address and public lookup target; raw IP addresses and lookup text are not stored in this ledger. Usage events are retained for 90 days. Aggregate operating summaries may be retained longer.

The usage ledger does not contain prompts, tool arguments, financial amounts, passwords or API-key values. Uploads, saved reports and other application records have their own storage lifecycle. The existing local public MCP uses a separate sanitized operating-log feed.

Broad collection patterns may trigger a temporary limit and operator review. We may restrict access for misuse. A detection signal is a heuristic, not proof of misconduct; contact support if a legitimate workflow is affected. Usage displays are recorded activity, may undercount and are not billing statements.

Validate decisions and submissions

SACS.ai is independent software and is not affiliated with the California Department of Education. Data, calculations and migrated accounting checks may be incomplete or contain errors. Verify material decisions against source records and validate official submissions in SACS Web. A completed job or exported file is not CDE certification.

Changes and questions

We publish dated versions of these terms. Acceptance for new keys is recorded with the version in organization activity. Questions about access, permitted use or recorded usage can be sent to support@sacs.ai.