<commit_before>Every response from the api must follow this format, including errors, searches, gets, posts, authorization, **all responses**.  UPPER_CASE is used to represent a variable.  They're defined following this snippet.

```json
{
    "TYPE": [
      {
        "id": "THING_ID",
        "OTHER_TYPE_ID": "ID",
        "OTHER_TYPE_ID_MULTI": ["ID", "ID"]
        "MISC_PROPERTY": MISC_VALUE,
        "OTHER_MISC_PROPERTY": OTHER_MISC_VALUE
      }
    ]
}

```

<dl>
  <dt> `TYPE`
  <dd> type is the resouce type.  Examples: person, student, teacher, grade, assignment, session
  <dd> there may be multiple values for a type
  <dd> there may be multiple types on a response
  <dd> `GET /api/TYPE/id` should give the data for an object type

  <dt> `id`
  <dd> an id that is unique to this object within its type
  <dd> `GET /api/TYPE/id` should give the data for an object type

  <dt> `OTHER_TYPE_ID`
  <dd> another type name such as: personId, studentId, teacherId, etc.
  <dd> removing the "Id" suffix is the TYPE of that object; `GET /api/TYPE/ID` should resolve that object

  <dt> `OTHER_TYPE_ID_MULTI`
  <dd> the key is the same as `OTHER_TYPE_ID` e.g. personId, studentId, teacherId
  <dd> if it's possible for there to be multiple related documents of the same type, it should have an array response
<commit_msg>Fixed spelling and corrected json.<commit_after>Every response from the api must follow this format, including errors, searches, gets, posts, authorization, **all responses**.  UPPER_CASE is used to represent a variable.  They're defined following this snippet.

```json
{
    "TYPE": [
      {
        "id": "THING_ID",
        "OTHER_TYPE_ID": "ID",
        "OTHER_TYPE_ID_MULTI": ["ID", "ID"],
        "MISC_PROPERTY": "$MISC_VALUE",
        "OTHER_MISC_PROPERTY": "$OTHER_MISC_VALUE"
      }
    ]
}

```

<dl>
  <dt> `TYPE`
  <dd> type is the resource type.  Examples: person, student, teacher, grade, assignment, session
  <dd> there may be multiple values for a type
  <dd> there may be multiple types on a response
  <dd> `GET /api/TYPE/id` should give the data for an object type

  <dt> `id`
  <dd> an id that is unique to this object within its type
  <dd> `GET /api/TYPE/id` should give the data for an object type

  <dt> `OTHER_TYPE_ID`
  <dd> another type name such as: personId, studentId, teacherId, etc.
  <dd> removing the "Id" suffix is the TYPE of that object; `GET /api/TYPE/ID` should resolve that object

  <dt> `OTHER_TYPE_ID_MULTI`
  <dd> the key is the same as `OTHER_TYPE_ID` e.g. personId, studentId, teacherId
  <dd> if it's possible for there to be multiple related documents of the same type, it should have an array response

{'fraction_non_alphanumeric': 0.10494975809452921, 'fraction_numerical': 0.0, 'mean_word_length': 3.4949832775919734, 'pattern_counts': {'":': 12, '<': 33, '<?xml version=': 0, '>': 33, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5232678', 'n_tokens_mistral': 890, 'n_tokens_neox': 853, 'n_words': 356}