AccuraCite · Schema

VerifyResult

CitationsResearchBibliographyAcademicVerificationAI Safety

Properties

Name Type Description
verification_status string
mismatches array Populated only when verification_status is "mismatch". Any of: title, author, year, DOI, journal, volume, issue, page.
reason stringnull Set for some not_found results (e.g. a dead URL); otherwise null.
source stringnull Database that supplied `citation`: OpenAlex, Crossref, Semantic Scholar, PubMed, DBLP, arXiv, or Google Scholar. "Publisher Metadata" and "URL Direct Check" mean a URL was fetched directly instead.
retracted boolean Independent of verification_status: a citation can be a real, correctly-matched paper (verification_status "verified") and still be retracted. Sourced from retraction metadata already published by Ope
citation object Null only if nothing at all was found. When verification_status is not_found, this may still be populated as the closest candidate match, not a confirmed one — always branch on verification_status, ne
View JSON Schema on GitHub

JSON Schema

accuracite-verify-result-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/accuracite/main/json-schema/accuracite-verify-result-schema.json",
  "title": "VerifyResult",
  "x-generated": "2026-10-02",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/accuracite-openapi.json#/components/schemas/VerifyResult",
  "type": "object",
  "properties": {
    "verification_status": {
      "type": "string",
      "enum": [
        "verified",
        "mismatch",
        "not_found"
      ]
    },
    "mismatches": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Populated only when verification_status is \"mismatch\". Any of: title, author, year, DOI, journal, volume, issue, page."
    },
    "reason": {
      "type": [
        "string",
        "null"
      ],
      "description": "Set for some not_found results (e.g. a dead URL); otherwise null."
    },
    "source": {
      "type": [
        "string",
        "null"
      ],
      "description": "Database that supplied `citation`: OpenAlex, Crossref, Semantic Scholar, PubMed, DBLP, arXiv, or Google Scholar. \"Publisher Metadata\" and \"URL Direct Check\" mean a URL was fetched directly instead."
    },
    "retracted": {
      "type": "boolean",
      "description": "Independent of verification_status: a citation can be a real, correctly-matched paper (verification_status \"verified\") and still be retracted. Sourced from retraction metadata already published by OpenAlex, Crossref, and PubMed; corroborated the same way the rest of verification is, so any one provider flagging it is enough. False does not mean \"confirmed not retracted\" -- only that none of the providers consulted flagged it."
    },
    "citation": {
      "oneOf": [
        {
          "$ref": "#/$defs/Citation"
        },
        {
          "type": "null"
        }
      ],
      "description": "Null only if nothing at all was found. When verification_status is not_found, this may still be populated as the closest candidate match, not a confirmed one — always branch on verification_status, never on whether citation is present."
    }
  },
  "$defs": {
    "Citation": {
      "type": "object",
      "properties": {
        "title": {
          "type": [
            "string",
            "null"
          ]
        },
        "author": {
          "type": [
            "string",
            "null"
          ]
        },
        "doi": {
          "type": [
            "string",
            "null"
          ]
        },
        "url": {
          "type": [
            "string",
            "null"
          ],
          "format": "uri"
        },
        "year": {
          "type": [
            "string",
            "null"
          ]
        },
        "bibtex_entry_type": {
          "type": [
            "string",
            "null"
          ]
        },
        "volume": {
          "type": [
            "string",
            "null"
          ]
        },
        "issue": {
          "type": [
            "string",
            "null"
          ]
        },
        "page": {
          "type": [
            "string",
            "null"
          ]
        },
        "publisher": {
          "type": [
            "string",
            "null"
          ]
        },
        "container_title": {
          "type": [
            "string",
            "null"
          ]
        },
        "abstract": {
          "type": [
            "string",
            "null"
          ]
        }
      }
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/accuracite-verify-result"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.