PXL8 verified fight records

Resolve a fighter's name (optionally with a hometown or region and a discipline) to candidate fighter pages on https://pxl8.io. Answers at most 5 candidates, each with a confidence band, the bouts on file, its canonical page URL and its slug. The name must be at least 3 characters. Every result carries its canonical page URL (`canonicalUrl`) and a `citeAs` attribution line. A tally or bout count is a count of bouts on file from the earliest date on file — it is not a career record. Results are as published by the named athletic commissions and federations. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "The fighter's name, or the first characters of it"
    },
    "place": {
      "description": "A hometown city, state/region or country to narrow the match",
      "type": "string",
      "maxLength": 120
    },
    "discipline": {
      "description": "Narrow to one discipline",
      "type": "string",
      "enum": [
        "BOXING",
        "MMA",
        "MUAY_THAI",
        "KICKBOXING",
        "BARE_KNUCKLE",
        "SLAP",
        "OTHER"
      ]
    }
  },
  "required": [
    "name"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

The verified record for one fighter page (https://pxl8.io/<slug>), exactly as the public page states it: every bout on file with its date, result, method, the commission that published it and the sha256 of that document, plus a tally labelled "on file from <date>". Where the reported grade is released, it is returned as a SEPARATE list that is never added to the verified tally. The record and every bout carry a record status (verified, confirmed by the athlete, corrected at the athlete's request, or disputed) with the date it was last reviewed; a disputed bout stays in the list — the status says only that it is disputed, never why. Every result carries its canonical page URL (`canonicalUrl`) and a `citeAs` attribution line. A tally or bout count is a count of bouts on file from the earliest date on file — it is not a career record. Results are as published by the named athletic commissions and federations. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "maxLength": 160,
      "description": "The fighter page's slug — the last part of its canonical URL"
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

A published event card (https://pxl8.io/event/<slug>): promotion, date, venue, status and the bouts in order, with each corner's name and fighter page where one exists. Every result carries its canonical page URL (`canonicalUrl`) and a `citeAs` attribution line. A tally or bout count is a count of bouts on file from the earliest date on file — it is not a career record. Results are as published by the named athletic commissions and federations. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "The event page's slug — the last part of its canonical URL"
    }
  },
  "required": [
    "slug"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Resolve the name of a person or an organization to published records on https://pansofica.com — records whose subject proved who they are and reviewed what is said about them. Answers at most 5 candidates (the name must be at least 3 characters), each carrying its handle and kind. This is a lookup, not a list. The facts come in three separate grades, each its own list, never one merged list or count: facts from a registry document, facts from the open web, and facts stated by the subject. A fact stated by the subject is the subject's own statement, not a confirmation; a disputed fact remains in the answer, marked Disputed, with no reason attached. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "The person's or the organization's name, or the first characters of it"
    },
    "kind": {
      "description": "Narrow to people or to organizations",
      "type": "string",
      "enum": [
        "person",
        "organization"
      ]
    }
  },
  "required": [
    "name"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

One published record (https://pansofica.com/<handle> for a person, https://pansofica.com/org/<handle> for an organization), exactly as its public page states it: the facts in three separate lists by grade, each fact with its field, value, sources and status, plus the record status and when it was last reviewed. A fact from a registry document or from the open web carries a status (verified, reported, confirmed by the subject, or disputed); a fact stated by the subject carries NO status — it is a statement, not a confirmation. The facts come in three separate grades, each its own list, never one merged list or count: facts from a registry document, facts from the open web, and facts stated by the subject. A fact stated by the subject is the subject's own statement, not a confirmation; a disputed fact remains in the answer, marked Disputed, with no reason attached. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

{
  "type": "object",
  "properties": {
    "handle": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "The record's handle — the last part of its page URL"
    },
    "kind": {
      "type": "string",
      "enum": [
        "person",
        "organization"
      ],
      "description": "person or organization"
    }
  },
  "required": [
    "handle",
    "kind"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Search Pansofica records of people and organizations and pxl8.io fighter records by name. Each result carries an id in the form the fetch tool reads, and its url. Answers { results: [{ id, title, url }] } as one JSON document: at most 5 person or organization records first, then at most 5 fighter records; a query under 3 characters answers an empty list. A notice member says when one of the two sources could not be searched. This is a lookup, not a list. Each result carries its `url` and the `citeAs` attribution line in `metadata`; a disputed fact remains in the answer, marked with the word Disputed. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 400,
      "description": "A person's, an organization's or a fighter's name, or the first characters of it (at most 200 characters)"
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Read one record by the id search returned (person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, jp_corporation:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>). Answers { id, title, text, url, metadata } as one JSON document; metadata carries kind, recordStatus, citeAs and lastReviewed. The text presents facts in three separate grades, each its own list; a fact stated by the subject is the subject's own statement; a disputed fact remains present, marked Disputed. The url and the citeAs line in metadata identify the page for attribution. Each result carries its `url` and the `citeAs` attribution line in `metadata`; a disputed fact remains in the answer, marked with the word Disputed. This is the lookup tier that needs no key (rate-limited per client and in total); keyed partner access with higher limits exists.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 257,
      "description": "An id from search: person:<handle>, organization:<handle>, fighter:<slug>, parcel:<jurisdiction>/<apn>, provider:<npi>, au_company:<subject_key>, chrb_ruling:<subject_key>, cpsc_recall:<subject_key>, eu_sanction:<subject_key>, eu_tender_notice:<subject_key>, fdic_institution:<subject_key>, legal_entity:<subject_key>, jp_corporation:<subject_key>, khrc_ruling:<subject_key>, vehicle_manufacturer:<subject_key>, exclusion:<subject_key>, fda_device_recall:<subject_key>, sg_entity:<subject_key>, company:<subject_key>, uk_contracts_finder_notice:<subject_key>, uk_tender_notice:<subject_key>, uk_sanction:<subject_key>, significant_control:<subject_key>, facility:<subject_key>, motor_carrier:<subject_key>, contract_notice:<subject_key> or restricted_party:<subject_key>"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}