Now open Founding district cohort for 2026–27. Twelve California districts, locked pricing. Learn more →
Quilt
Book a walkthrough

For developers

Build education AI without rebuilding education infrastructure.

One secure, standardized way to reach the district data your agents need, from student information and assessment to attendance, finance, HR and the district’s own documents.

Request developer access Explore the platform

The gap

AI is changing education software. The infrastructure hasn’t caught up.

Building an agent gets easier every month. Connecting one to a school district does not, because the data sits in dozens of systems with their own APIs, permissions and security reviews.

Every AI company shouldn’t have to solve that independently, and every district shouldn’t have to run a fresh security review for each vendor that shows up. That’s the problem Quilt exists to take off both of you.

One question, five systems

“Which interventions are improving outcomes for chronically absent students?”

Before your agent can answer that, it has to reach

  • SIS · enrollment, attendance
  • Assessment platform
  • Intervention system
  • State reporting
  • District spreadsheets

Then the district’s definition of “chronically absent,” which is not always the state’s. Then permission to see any of it.

The layer

Connect once. Build anything.

Quilt sits between district systems and the AI applications that need to use them.

District systems

  • PowerSchoolStudent records
  • AeriesEnrollment and attendance
  • Infinite CampusGrades and schedules
  • SynergyStudent information
  • CanvasAssignment-level signal
  • FrontlineAbsence and staffing
  • MunisFinance and position control
  • Google WorkspaceIdentity and documents
  • Assessmenti-Ready, NWEA, CAASPP
  • Data warehouseEd-Fi or your own
  • DocumentsPolicy, LCAP, handbooks

Every system we connect to

Quilt

Connect

Integrate the systems a district already runs, including the nightly SFTP drop, because K–12 still runs on it.

Integrated
Normalize

Map inconsistent vendor schemas into one education model, so your code doesn’t branch on which SIS the district bought.

Canonical
Resolve

Recognize that a student, employee, school or program appearing in six systems is one entity, with one identity.

Deterministic
Authorize

Decide what each user, agent and application is allowed to reach, checked on every request rather than at login.

Enforced
Govern

Log and control how AI touches sensitive district information, in a record the district can read without calling you.

Auditable
Expose

Publish approved capabilities as tools, over MCP or a conventional API.

Your surface

Your AI

  • Analysis agents
  • Compliance agents
  • Finance agents
  • Instructional tools
  • Administrative copilots
  • Whatever you build next

01 · The interface

Your agent shouldn’t need to know how PowerSchool stores attendance.

It asks Quilt, and gets the same shape of answer whether the district next door runs Synergy or Infinite Campus.

Quilt handles the systems underneath. You build what your product does with the information.

How the tool layer is authorized

Approved capabilities
get_student_attendance()
get_assessment_history()
get_course_enrollments()
get_budget_actuals()
find_students_meeting_criteria()
get_program_outcomes()

# every call is scoped to the caller,
# checked against district policy,
# and written to an audit the district owns

02 · Protocol

MCP-native, and API-friendly when that fits better.

Expose approved education capabilities straight to your agents over the Model Context Protocol, or integrate the conventional way. Either way, you never write a custom integration per district system.

03 · The control layer

Giving a model access to education data is easy. Giving it the right access is the hard part.

Fine-grained permissions

Access is decided by district, school, role, student population, data type, agent and application. Not by a single API key that either works or doesn’t.

Agent-scoped access

An attendance agent reaches attendance. It doesn’t quietly inherit payroll, special education or unrelated student records because it shares a credential with something that needs them.

Auditable activity

What an agent read, who asked for it, which record the answer came from and when. The district reads that log themselves rather than requesting it from you.

Governed tools

You get a set of approved capabilities, not a database login. There’s no general-purpose query tool to jailbreak into.

Source-aware responses

Information stays attached to the system it came from, so your product can cite a claim instead of asserting it.

District control

The district decides which applications connect, which agents run, what those agents can read and who may use them. You inherit that decision rather than negotiating it per district.

Quilt is read-only, and that applies to you too. Nothing your agent does through Quilt writes back to a district’s system of record. Your product can read, analyze and draft. A person in the district reviews and acts. If your application needs to write to an SIS, talk to us before you build around it.

04 · Coverage

The last generation connected applications to schools. This one connects agents to a whole district.

That takes more than rostering. An agent that’s useful to a cabinet has to understand six kinds of thing at once.

Students

Attendance, enrollment, assessments, courses, interventions, demographics and program participation.

People

Teachers, administrators, staff, roles, assignments and the permissions attached to each.

Organizations

Schools, departments, programs, cohorts and grade levels, with the dates each was true.

Finance

Budgets, expenditures, vendors, funding sources and contracts.

Operations

HR, staffing, transportation, facilities and compliance.

Knowledge

Board policy, plans, procedures, contracts and state guidance, the documents the numbers have to be read against.

05 · The math

Stop rebuilding the same integrations for every district.

Integration work doesn’t compound. Each district you sign starts it over, and the second one rarely runs the same stack as the first.

One connection to Quilt reaches the ecosystem behind it, and the district’s permission model comes with it rather than being rebuilt in your code.

Without Quilt

  • Your product → PowerSchool
  • Your product → Aeries
  • Your product → Infinite Campus
  • Your product → Canvas
  • Your product → Frontline
  • Your product → the finance system
  • Your product → the district warehouse

Then the next district, whose stack is different.

With Quilt

  • Your product → Quilt → the district ecosystem

The next district is a configuration, not a project.

06 · What you build

Spend year one on your product, not on connectors.

Say you’re building for superintendents. Instead of a year of integration work, your agent asks for what it needs and gets it back in a consistent shape.

You build the intelligence. We keep the infrastructure underneath it working, including the week a district upgrades its SIS.

What your agent can ask for

“Show enrollment changes by school over the past three years.”

“Compare chronic absenteeism with math growth.”

“Which software contracts expire this fiscal year?”

“Which schools are furthest behind their LCAP goals?”

“How much are we spending on programs with no measurable student usage?”

“Which positions have been unfilled for more than 60 days?”

The district decides

  • Which AI applications may connect at all.
  • Which agents those applications may run.
  • What information each of those agents can read.
  • Which staff are allowed to use them.
  • When that access ends, without calling the vendor.

07 · The other side

One connection for districts, too.

A district that connects its systems once doesn’t stand up a new pipeline, and a new security review, for every AI application it adopts.

That’s worth something to you as well. The reason district integrations take nine months is rarely the code. It’s the review. Districts already through that review with Quilt can evaluate your product on whether it’s good.

Applications connected schools to software. Quilt connects them to intelligence.

Tell us what you’re building and which district is waiting on it. We’ll tell you honestly whether Quilt reaches the data you need yet.

Request developer access Read the architecture