---
name: admit-protocol-vvs
description: Help a family apply to Verde Valley School (grades 9-12, boarding and day, Sedona, Arizona) from documents on their own computer. Read this before touching the API.
version: 0.1-draft
---

# Applying to Verde Valley School with your agent

This school speaks **Admit Protocol** (https://admitprotocol.com): a folder on the family's computer is the application, and an agent carries it to any school that publishes a skill like this one.

Verde Valley School (grades 9-12, boarding and day, Sedona, Arizona) accepts applications from a family's own AI agent. You are that agent. You will gather what the family already has, ask for what is missing, read everything back to them, and send it. A person at the school reads every application. Nothing here is scored by software.

**The school's policy in one line: the agent facilitates the application; the student writes. The AI does not write for the student.** There is no application fee.

Base URL: `https://admitprotocol.com/vvs`

## Rules

1. **The student writes. You facilitate.** The application asks for a piece of writing in the student's own voice. You may ask the student questions, point at files, transcribe what they wrote by hand, and fix nothing. You may not draft, rewrite, polish, suggest wording for, or "improve" it, even if asked. Submit it as it is, typos included. The school reads it for thinking, interest and honesty, not for quality, and would rather see rough and real than smooth and borrowed. Every writing item carries an attestation that the student wrote it unaided, and the family confirms that before you send. If the student wants help, the help is a question ("what do you mean here?"), never a sentence.
2. **Ask before you send.** Show the family exactly what you are about to submit, field by field, and wait for their yes. Same for every file.
3. **Only what the family gives you.** Do not search the web for the student or fill gaps with guesses. A field you do not know stays empty.
4. **A parent or guardian approves the application.** The student may run the whole thing with you. The verified email must belong to a parent or guardian, not the student, and nothing is sent until that person has given you the code.
5. **Incomplete is fine.** Send what exists today; add the rest later. The school considers applications with missing pieces.
6. **Keep the token.** After the parent verifies their email you get an `application_token`. Store it in the family's folder as `.admit-protocol/vvs.token` so later sessions can add items. Never print it in chat or logs.

## What to tell families about their data

Applications from students who do not enroll are deleted two years after the admissions cycle closes; applications from students who enroll are deleted from this service one year after enrollment. The student's details and writing are stored encrypted; only signed-in admissions staff read them. Privacy policy: https://admitprotocol.com/privacy.

## The flow

1. `GET /v1/schema` once per session. Fields and enums come from there, not from this file.
2. Look at the folder you were started in (or the one the family names). Typical contents: a note about the student, the student's answers to the prompts, a parent's statement, report cards or transcripts, test scores, awards, an IEP or 504 plan, a list of teachers who could recommend. Map each file to an item type below and tell the family what you found. Ask what is missing; do not insist. If the folder is empty or nearly so, offer to lay out the starter files first: `GET /v1/starter` (or the `starter_folder` tool) returns `[{path, contents}]`, one file per field group and per writing prompt with the question inside; write them into the folder and let the family fill them in.
3. Build the application payload and read it back.
4. `POST /v1/applications` with the payload. The response has `application_id`; a 6-digit code goes to the parent email.
5. Ask the parent for the code. `POST /v1/applications/{id}/verify` with it. The response has `application_token`. Save it (rule 6).
6. Add items: `POST /v1/applications/{id}/items` for text, `POST /v1/applications/{id}/items/file` for files (PDF, JPG, PNG, HEIC, DOCX; 20 MB each). Writing goes as text where possible so the school can read it on a phone.
7. `GET /v1/applications/{id}` shows the checklist: what is received, what is missing, and `next_action` in plain words. Read it to the family.
8. When the required writing and the student's identity are in (`GET /v1/applications/{id}` lists what is still needed), `POST /v1/applications/{id}/submit`. This is when the school sees the application in its admissions system. Tell the family what happens next (below).
9. Later sessions: read the token from `.admit-protocol/vvs.token`, call `GET /v1/applications/{id}`, add what is new.

If the family only wants to express interest, stop after step 5. The school sees a started application as an inquiry and may reach out.

## Item types

| type | what it is | required to submit |
|---|---|---|
| `writing` | An answer to one of the school's prompts below, in the student's own words, with `prompt` set to the prompt key. | yes |
| `parent_statement` | A note from a parent or guardian, in their own words: who the student is at home, what they hope the school will be for them. Text or a file. | no |
| `transcript` | Official or unofficial transcript. | no |
| `report_card` | Any recent report card or grade summary. Counts in place of a transcript for now. | no |
| `test_score` | SSAT, ISEE, PSAT or anything else. Optional. | no |
| `english_competency` | TOEFL, IELTS or Duolingo, for students whose schooling was not in English. | no |
| `iep_504` | An IEP, 504 plan or learning evaluation, if the family wants the school to see it. | no |
| `awards` | Awards, honors, or recognitions, as a list or a file. | no |
| `additional` | Anything else: a portfolio link, a project, a letter from the family. | no |
| `recommendation_*` | Not sent by the family. See "Recommendations". | no |

## The school's writing prompts

Each answer is its own `writing` item with `prompt` set to the key. Prompts under "choose one" are alternatives: the student answers one of them. Word counts are the school's guidance; send what the student wrote and mention the count if it is far off. Do not trim or pad it.

1. `reading` (required), 200-250 words: Aside from books or articles assigned for school, what book(s), article(s), podcast(s), and/or documentary(s) have you most enjoyed in the past year and why?
2. `achievement` (required), 200-250 words: Describe EITHER an academic/extracurricular achievement OR a challenge that had a meaningful impact on you. What did it take to accomplish the achievement or overcome the challenge, and what did you learn from that experience?
3. `three-words` (required), 200-250 words: Each person has unique characteristics that define who they are. Choose three words that best describe you as a person, and explain how they represent you.
4. **Choose one** (250-500 words, required):
   - `essay-event`: Explain an event or activity that has impacted your life and/or your way of thinking.
   - `essay-regret`: Explain a time when you made a decision you regretted. Explain why you made that decision. How would you approach the same situation differently if you could now?
   - `essay-advice`: What is the best piece of advice you have ever received? From whom did you receive the advice, and how did you apply it?
   - `essay-left-out`: Describe a moment when you felt left out or that you did not fit in well with others. What did you learn about yourself and others? How did you overcome that situation?
   - `essay-quote`: What is your favorite quote from a movie, book, or a line from a song or poem? Please name the movie, poem, or song, and tell us what it means for you.
5. `project` (required), any length: At Verde Valley School we really value student input. During our end-of-year Project Period we ask students to submit proposals for projects they would like to see offered or lead themselves. Given the chance to develop a one-week project in the arts, sciences, outdoors (or something we have not thought of yet), what would you propose, in detail? Why? Why should students sign up for your project?

Ask for the answers as files in the folder (one file per prompt, any format) or typed by the student. If an answer is missing, say which prompt and move on; it can come later.
## Recommendations

The school likes a math recommendation, an English recommendation, and one from a principal or counselor; a personal one is welcome. The family does not write or collect these. Give the names and school email addresses of the recommenders with `POST /v1/applications/{id}/requests` and the school emails each one a link. The family sees "requested" and "received", never the content. If the family cannot name recommenders yet, skip it; the school can ask later.

## Payload (shape only; the live schema is authoritative)

```json
{
  "parent": { "name": "", "email": "", "relationship": "mother|father|guardian|other", "phone": "" },
  "student": {
    "first_name": "", "last_name": "", "preferred_name": "", "date_of_birth": "YYYY-MM-DD",
    "current_school": "", "current_grade": "", "city": "", "state_or_region": "", "country": "",
    "languages_at_home": "", "international": false
  },
  "entering_year": "<from the schema>",
  "entering_grade": "9|10|11|12",
  "boarding_or_day": "boarding|day|undecided",
  "financial_aid_interest": false,
  "how_you_found_us": "",
  "agent": { "name": "Claude Code", "version": "" }
}
```

Writing item:

```json
{ "type": "writing", "prompt": "reading", "title": "optional", "text": "...",
  "attestation": { "written_by": "student", "agent_edited": false, "confirmed_by": "parent" } }
```

The server refuses a writing item whose attestation says anything other than `written_by: "student"` and `agent_edited: false`.

## What happens after submit

- The application appears in the school's admissions system, with a link to the documents. A person on the admissions team reads it, usually within a week.
- The family hears from the school by email about an interview and a visit.
- `GET /v1/applications/{id}` keeps working: it shows which items the school has reviewed and the current stage. Decisions are not delivered through this API; the school emails the family.
- To withdraw: `POST /v1/applications/{id}/withdraw`.

## Errors

| status | meaning | what to do |
|---|---|---|
| 400 | a field or file was rejected; the body says which | fix and retry |
| 401 | missing or expired token | ask the parent to request a new code with `POST /v1/applications/{id}/resend` |
| 409 | already submitted, or a second parent email | read `GET /v1/applications/{id}` and continue from there |
| 413 | file too large | compress or split; 20 MB each |
| 429 | too fast | wait a minute |

## For MCP clients

Claude Desktop, Claude mobile, Cursor and ChatGPT can connect to `https://admitprotocol.com/vvs/mcp` instead of calling the REST endpoints. The tools are the same operations: `get_application_schema`, `start_application`, `verify_email`, `resend_code`, `update_application`, `add_item`, `add_file`, `request_recommendation`, `get_status`, `submit_application`, `withdraw`. The rules above apply unchanged.

## About the school

Verde Valley School is an independent boarding and day high school on 150 acres in Sedona, Arizona, with an International Baccalaureate program, field expeditions, a working farm and a horse program. More at https://vvsaz.org. Questions about an application: admissions@vvsaz.org.
