Find the right district.
Resolve district identity and discover official datasets before asking a financial question.
District lookup / dataset discoveryCalifornia school finance / Agent ready
Your agent.
California
context.
The school-finance knowledge your AI is missing. Bring official SACS data, district context, and traceable evidence into the agent you already use.
Free public connector. Read-only tools. No SACS account needed.
A little context. A better starting point.
Your workspaceThe agent you already useA compatible remote MCP client
Model Context Protocol
sacs.aiContext layer
California school-finance context,
ready for the next question.
District identitySACS definitionsFinancial contextSource evidence
Official public CDE / SACS datasets
Context in. Evidence stays attached.
Built for the work ofDistrict finance teamsSchool business consultantsCounty offices of education
01 / The missing context
A capable agent.
A more informed conversation.
California school finance has its own language. SACS.ai brings the district, the reporting basis, and the source into view.
Give the numbers context.
Bring SACS code definitions, financial summaries, and comparisons into the conversation.
SACS ontology / public financialsKeep the evidence attached.
Get compact district context packs with dataset references, provenance, and explicit limitations.
Single district / bounded batches02 / Put it to work
Start with a district.
Ask a better question.
A useful first task: ask your agent for a briefing that keeps the numbers and their limitations together.
Try this in your connected agent
Use SACS.ai to prepare a district context pack for Kern High. Identify the district, show the available fiscal years and reporting bases, and summarize the latest available General Fund position. Include dataset references, source links where available, and limitations. Keep budgets, interims, and actuals distinct. Flag unavailable actuals and quarantined rows; do not fill gaps with estimates.
What to look for in the responseIllustrative
A district briefing
you can inspect.
An example structure, not a live data result.
- 01 / Identity
- District name and identifiers, resolved before analysis.
- 02 / Reporting context
- Fiscal year, reporting period, and basis kept explicit. A budget is not an actual.
- 03 / Evidence
- Dataset references and versions, with user-openable source links where available.
- 04 / Limitations
- Unavailable actuals stay marked unavailable. Quarantined rows stay out of conclusions.
Ask your agent to show its sources before you use the answer.
03 / Bring your own agent
One connection.
Your existing workflow.
MCP lets an AI agent call SACS.ai’s public tools when it needs California school-finance context.
Use a client that supports remote MCP over Streamable HTTP. Client setup and connector availability vary.
- 01
Add a remote MCP connection
In your agent’s connector settings, add SACS.ai using the endpoint above. This public connector does not require a SACS login or API key.
- 02
Enable the SACS tools
Allow your agent to use the connector in your conversation. Start with public district data.
- 03
Try the district briefing
Paste the first-use prompt, then check the reporting period, sources, and limitations in the answer.
Connection not working?
Check that your client supports remote Streamable HTTP and that the URL includes /mcp. Opening the endpoint in a browser is not a connection test. If a request is rate-limited, wait before trying again; for timeouts, try one district and a narrower period.
Still stuck? Email the client name and error to support. Individual client walkthroughs are still being validated.
04 / Where we’re going
Context first.
Signals and review next.
Start with useful public context. Build toward ongoing awareness and private review as practitioner needs become clear.
Available01
SACS Context
A public, read-only MCP connector. District lookup, SACS definitions, financial summaries, comparisons, and district context packs.
Up next02
Deeper context
More proven practitioner workflows, clearer coverage and freshness, easier setup, and a feedback loop shaped by real use.
Planned03
SACS Signals
District watchlists and verified reporting-cycle changes. Reviewed findings shared through School Finance Signal.
Later04
SACS Review
Private uploads, projection review, versioned workpapers, and scenario history, with controlled human approval.
Direction, not delivery dates. Watchlists, private review, paid plans, and organization controls are future capabilities.
Built to be inspected
Know what’s behind
the answer.
Sources, versions, and limitations belong in the work from the beginning.
What data can my agent access?
The public connector exposes bounded, read-only tools over official public CDE/SACS data. It does not provide private uploads, unrestricted SQL, or access to your local files. Coverage varies by district, year, reporting period, and basis; ask for available datasets first.
How current is the context?
Reporting releases and imports happen on different schedules. SACS.ai does not promise exhaustive or real-time coverage. Check the returned dataset version, reporting basis, and limitations on each request. A recent retrieval timestamp does not mean a new reporting cycle is available.
How should I use the evidence?
A dataset identifier helps trace a result inside SACS.ai; it is not necessarily a clickable primary-source link. Ask for source links where available and distinguish reported figures from your agent’s interpretation. Use professional review for consequential decisions.
What happens to my information?
The public tools are for public-data questions. Operational logs record bounded request and tool metadata, not prompts or returned financial rows by default. Your chosen agent provider has its own data policies. Do not send confidential documents through this public workflow.
Help shape what comes next
Put it to work.
Tell us what’s missing.
Useful, incomplete, incorrect, or stale? Share the district, reporting period, and request or data version if available. Public information only.