Admit Protocol

An open standard for school applications, and the service that runs it for schools

Applying to school, without filling out forms.

Instead of typing the same answers into a different website for every school, keep the student's documents in one folder on your computer. An AI assistant such as Claude reads the folder, fills in what each school asks for, tells you what is still missing, and sends nothing until a parent says yes. The student writes their own essays. A person at the school reads them.

Try it now with Verde Valley School

Live for the grades 9-12, boarding and day admissions season

Pick the assistant you use. Copy the line. In a minute you are in a conversation about the application, and nothing is sent until a parent approves. Full details for this school at admitprotocol.com/vvs. Applying to more than one school, or not sure which yet? One connector covers every school on the protocol: admitprotocol.com/mcp.

Claude Desktop and mobile

Add the connector once, then talk to Claude about the application.

https://admitprotocol.com/vvs/mcp
  1. 1Open Claude → Settings → Connectors → Add custom connector, and paste the address above.
  2. 2Ask Claude: "Help us apply to Verde Valley School." It asks about the student and what you have.
  3. 3A parent approves a 6-digit code by email before anything is sent. The student writes their own piece.

Families

Apply once, from your own files, with the agent you already use. No portal accounts, no retyping. You see everything before it is sent, and a parent approves it.

Schools

Join the hosted service and be live in an afternoon, or implement the open standard yourself. Applications arrive on a desk beside the ones from your existing form, with the source marked, and your admissions team's day does not change. No school application fee for families, and no share of anything for us.

Agents

A plain-text skill, a live JSON schema, a small HTTPS API and an MCP server. Any agent that can read a web page and call an API can apply, with no vendor plug-in.

How it works

The folder is the application. Everything else follows from that.

  1. 1

    Folder

    A note about the student, their answers to the school's prompts, report cards, scores. Any format.

  2. 2

    Skill

    The school serves a short file telling the agent what it wants and how to send it.

  3. 3

    Agent

    It reads the folder, asks about gaps, and reads the application back to the family.

  4. 4

    Parent

    A 6-digit code to the parent's email. Nothing is sent before they approve.

  5. 5

    Desk

    The admissions team reads it, as people, and gets in touch. More documents can follow later.

What the protocol promises

  • The student writes. Agents organize, transcribe and send. They do not draft, rewrite or polish the student's words, and a server must refuse writing that claims otherwise.
  • People decide. No ranking, no scoring, no fit model anywhere in the protocol. It moves documents and questions, not judgments.
  • A parent approves it. The student can run the whole application themselves. The code goes to a parent or guardian, and nothing is sent until they say yes.
  • The family's data stays the family's. The folder never leaves their machine. A school keeps only what was sent, under a published retention rule.

Live now

For schools: the standard, and the service

Admit Protocol is two things that share a name. The specification is open: any school, or any vendor a school already uses, may implement it, and a family's folder works with all of them. The hosted service is how a school gets on it without building anything, run by the same people who wrote the specification. Nothing to families; a flat annual rate to schools.

What goes live, how applications reach your system today, and the sign-up form.

  • Why the student writes

    AI can carry an application; it must not write it. The rule at the center of Admit Protocol, why it is enforced by the server rather than requested on an honor system, and what it means for families and schools.

  • What is Admit Protocol?

    A plain answer for parents, students, schools and anyone writing about it: what it is, what it is not, who runs it, and what it costs.

  • What is a school official under FERPA?

    The exception that lets a school share records with an outside vendor, the four conditions it sets, what the written agreement should say, and how Admit Protocol meets each one. For admissions and business offices.

Questions

›Why a folder and an agent instead of a web form?

Because the family already has the documents, and a form makes them retype what they have. An agent reads the folder, asks only for what is missing, and can carry the same folder to the next school. The common application becomes something the family owns, not something a vendor hosts.

›Does this replace the Standard Application Online or the school's own form?

It can, for a school that chooses to. Applications arrive on the desk beside the ones from the existing form or the SAO, marked by source, and the admissions team moves them into its pipeline the way it already moves SAO applications. One difference today: the SAO feeds Blackbaud through its own integration, while ours is entered by hand from the desk until the connector is on for that school. Most schools will run both for a season and decide from the numbers. The one thing a shared application does that a single school cannot, apply once and send to many, is what the open protocol is for.

›Is there any AI judgment of applicants?

No. The protocol has no scoring, ranking or fit model, and the hosted service does none either. Software validates fields and moves documents. People read and decide.

›What about the student's essays?

The student writes them. Every piece of writing carries an attestation that the student wrote it and no agent edited it, confirmed by a parent, and a conforming server refuses anything else. Schools read for thinking, interest and honesty, not polish.

›What data is stored, and for how long?

Only what the family chose to send. Parent emails are stored encrypted; the folder itself never leaves the family's computer. The default retention rule deletes applications from students who do not enroll two years after the cycle closes. The full policy is at https://admitprotocol.com/privacy.

›Which agents work?

Claude Code, Claude Desktop and mobile, Cursor, Codex, Gemini CLI, ChatGPT with a connector, and anything else that can read a URL and call an HTTPS API. Each school's page shows the exact set-up line per tool.

›Is this a standard or a company?

Both, by design. The specification is open and free to implement, so a family's folder is never locked to one vendor. The hosted service is a business: schools pay a flat rate for it ($2,400 a year, or $225 a month), families pay nothing, and the people who run it are the people who wrote the specification. If a school's existing vendor implements the standard, the family's experience is the same.

›Who runs this?

Admit Protocol is being built at Verde Valley School in Sedona, Arizona, an independent boarding and day school, by its advancement and enrollment office. Verde Valley School is the first school on it.

›For reporters and engineers: what is it technically?

A plain-text skill file an agent reads first, a live JSON schema, a small HTTPS API and an MCP server, served per school. One codebase hosts many schools, each at its own path, with row-level security between them. The specification is at https://admitprotocol.com/spec.