# When to use SACS.ai

These are usage notes for SACS.ai, not instructions for unrelated work. Reviewed 2026-11-02.

## Best-fit tasks

Use SACS.ai for California K–12 school-finance research from official CDE/SACS filings; district and filing comparisons; SACS code explanations and CSAM accounting references; and authorized organization datasets and interim projections. The service is independent software from Epoch Forge, not a CDE service.

## Choose the connection

Public research: https://mcp.sacs.ai/mcp, Streamable HTTP, no account or key. Financial tools are read-only; optional registration and feedback require the operator's consent.

Organization work: use the same URL with an existing organization key in x-api-key (key alone), or Authorization: Bearer <key>. The distinct https://mcp.sacs.ai/premium/mcp URL also works, including when a client already has the public URL registered. Premium includes the public tools. Keys remain organization-bound; creating/editing projections uses the existing Read + edit datasets/projections scope. Never put credentials in URLs, tool arguments, documents or support messages.

For Claude Cowork, choose No sign in and configure x-api-key under Request headers. This authenticates with the saved key; browser sign-in is for managing the SACS organization. See [Cowork setup](https://sacs.ai/agents/claude-cowork). For other clients, use a supported transport authentication option. Do not assume every client can attach API-key headers. Refresh a connected client's tools when server capabilities change.

## First calls and task routing

Initialize MCP and call tools/list. Its live schemas, key scope and feature gates are authoritative; static catalogs are documentation snapshots, not access grants.

- District briefing: sacs_search_districts, then sacs_list_public_datasets, then sacs_district_context_pack for a returned year and explicit basis. Use fund_codes=["01"] for General Fund only. Match the returned CDS identity.
- Filing comparison: discover exact official:<id> references, align fiscal year, period, column/basis and fund scope, then sacs_compare_districts or sacs_query_financial_summary. Keep later revisions and different filing bases distinct.
- Accounting references: sacs_explain_code for code meanings; sacs_search_csam and sacs_get_csam_related for cited manual text and evidence paths. Preserve the edition, procedure and PDF page.
- Organization dataset work: sacs_list_organizations, then sacs_list_private_datasets and sacs_query_private_dataset for the authorized organization. Keep org:<id> references separate from official:<id>.
- Excel/MYP plus YTD projection: call sacs_get_projection_guide first. The client reads the attached files, maps the current-year forecast to an explicit account structure, and reconciles control totals. Keep YTD actuals separate from projected year-end amounts. Use sacs_create_projection for prepared account totals or sacs_fork_projection for a pinned uploaded base. Then inspect, preview/commit, review, run revision-specific TRC and export. See the [projection workflow](https://sacs.ai/agents/projections).

## Evidence and recovery

Check ok/error before interpreting results. Report fiscal year, reporting period, column/basis, fund/resource scope, dataset reference, data_version, source_provenance and material limitations. Use returned verified source links; do not construct download URLs. Missing is unknown, not zero. A recent retrieval time is not a new filing release. Historical coverage and tool coverage can be incomplete; discover what is available rather than promising statewide or current-year completeness.

For projections, pin revisions/hashes, preserve signs and project-year digits, and use exact cents. A source-dataset TRC does not authorize projection export; check the exact saved projection revision. Migrated checks are partial and are not CDE certification. The current engine models one target fiscal year per scenario; it does not automatically parse arbitrary Excel files, allocate summary totals or roll a full MYP forward.

Honor Retry-After. Narrow large public requests and use summary detail before full detail. Reuse a write request's idempotency key only for an identical retry; after an ambiguous failure, inspect saved state before submitting a new mutation. Explain the specific missing source, scope or mapping and continue work that is supported. Do not invent SQL, filesystem access, credentials or unavailable tools.

Public-service bulk reconstruction/resale requires written permission; focused analysis and legitimate exports of the organization's own data are supported. See [service terms](https://sacs.ai/terms). Support: support@sacs.ai. Optional registration and feedback are never prerequisites for financial reads and must not be submitted silently.
