Terms
Draft, November 17, 2026. These terms cover admitprotocol.com, every school's pages under it, the API and MCP server each school page serves, and any school address that points at the hosted service. The open specification itself is at /spec and may be implemented by anyone under its own license; nothing here restricts that.
Who we are
Admit Protocol is operated from Verde Valley School in Sedona, Arizona, which is also the first school on it. "We" on this page means the operator of the hosted service. "The school" means the school an application is sent to. Questions: hello@admitprotocol.com.
For families
- It is free. We charge families nothing, and no school on the service may charge a fee through it.
- The student writes. Every piece of writing is sent with a statement that the student wrote it and that no AI edited it, confirmed by a parent or guardian. Sending writing under that statement when it is not true is a misrepresentation to the school, and the school may treat it as it would any other false statement on an application.
- A parent or guardian approves. An application can be prepared by the student, but the email code and the final approval go to a parent or guardian, who is responsible for what is sent.
- What you send goes to the school. Once sent, the application is the school's to read and keep under its published retention rule and our privacy policy. You may withdraw it at any time; the school may already have read it.
- Sending is not admission. The service moves documents. Every decision about an applicant is the school's, made by its people under its own policies. We take no part in it.
- Your agent is yours. You choose the assistant and are responsible for what it sends on your behalf. Read the application back before approving it; that is what the approval step is for.
- Do not send more than asked. Medical, financial or other sensitive information that a school did not ask for should not be sent through the service. A school may ask for a learning plan (IEP or 504) where it is relevant to the application; send it only when the school asks.
For schools
- A signed agreement comes first. A school goes live only after signing our school agreement, which makes us a "school official" under FERPA: the applications are the school's, we act on its instructions, use the data for nothing else, pass it to no one, and delete it on the published schedule or on request. This page summarizes that agreement; where they differ, the signed agreement governs.
- The school controls access. The school names the staff who may see its applications, through its own Google accounts, and may remove them at any time. Every staff view and download is logged where the school can see it.
- The school reads and decides. We provide no scoring, ranking or recommendation, and the school agrees not to ask us for one. The service carries the family's material to the school's people.
- Price. A flat rate per school, $2,400 a year prepaid or $225 a month, never a share of fees or a per-application charge. The first 25 schools to sign up pay nothing until the 2027-28 school year begins on July 1, 2027; from that date every school pays the rate, founding schools included. Any change to the rate is published at least 60 days before it applies, and a school may leave at the end of any paid term.
- Leaving. On request we export every application the school holds, in open formats, and then delete the school's tenant, with a written record of the deletion.
- Your own systems. Until a connector is on for the school, moving an application into its admissions system is the school's staff's work, from the desk. We make no promise about any third-party system's behavior.
For agents and the people who build them
- The API and MCP server at each school's address exist for one purpose: carrying a real family's application to that school with that family's knowledge and a parent's approval. Use for anything else, including bulk, speculative or test applications to a live school, scraping, or probing, is not permitted. Test against the sample school or your own instance of the open specification.
- An agent must not write, rewrite or polish the student's writing, and must not send the written-by-student statement for text it produced. A conforming server refuses writing without that statement; an agent that lies in it puts its family at risk, not us.
- Tokens are issued per application to the family and must not be shared, stored centrally by a vendor, or used after the family withdraws.
- We may rate-limit, suspend or block access that breaks these rules, and we will tell the affected family where we can.
Availability and liability
The service is provided as it is, during a pilot, by a small team, and we do not promise it will always be up or error-free. Schools keep their existing application paths open alongside it, and a family who cannot reach the service should contact the school directly; no school on the service may hold a technical failure against an applicant. To the extent the law allows, our liability to any party is limited to the amount that party paid us in the preceding year, which for families is nothing. Nothing here limits what we owe a school under its signed agreement, or liability that the law does not allow us to limit.
Changes
We may update these terms. Material changes are dated at the top of this page and, for schools, sent to the school's contact before they take effect. Continued use after the date is acceptance; a school that does not accept may leave under the terms above.
Law
These terms are governed by the law of the State of Arizona, and disputes are heard in the courts of Yavapai County, Arizona, unless a school's signed agreement says otherwise.
Contact
hello@admitprotocol.com. Questions about a particular application go to the school it was sent to.