⭐ Facts Check API

Facts-Checking Webz.io’s on-demand fact checking uses AI to automatically identify factual claims in online text, such as news articles, blog posts, or forum posts. Each claim is then cross-verified by searching the web for other sources that support or refute it. The output clearly indicates whether the claim is Verified, False, or Unverified (when no references are found).

Want to see it in action? Try it out in our Demo or Playground environments.


Endpoint

This is the dedicated endpoint for the Fact-Check feature: https://api.webz.io/fact-check


API Calls

It can be used with HTTP GET and POST requests.

The table below outlines the required fields for each call, depending on the HTTP request type:

ParamDescriptionHTTP requestComment
uuidthe post's uuidGET
post_textthe text to analyzePOSTexpected to include
both 'title' + 'text' fields
post_linkthe link to the postPOST
datepost's published datePOST
tokenuser's tokenGET, POST

Expected structure:

https://api.webz.io/fact-check?token=[USER_TOKEN]&uuid=[POST_UUID]
https://api.webz.io/fact-check?token=[USER_TOKEN]&post_text=[POST_TITLE+POST_TEXT]&post_link=[POST_LINK]&date=[POST_PUBLISHED_DATE]

Limitations:

Fact-checking requires an input length of no less than 100 and no more than 10,000 characters.


Output Reference

The following table shows the fields returned by the API:

Field NameDescriptionComment
biasshows the detected political bias of the site
claimclaim extracted from the original post text
verifiedindicates whether the extracted claim has been verifiedpossible values:
true, false, unverified
referenceslist of sources cited to claim verification
textreference text supporting the claim verification
linkreference link supporting the claim verification

Response example:

{
  "bias": "left",
  "claims": [
    {
      "claim": "Iran's Supreme Leader Ayatollah Ali Khamenei has l...",
      "verified": "true",
      "references": [
        {
          "text": "Iran leader Khamenei sees his inner circle hollowed out ...",
          "link": "https://www.reuters.com/world/middle-east/i..."
        }
      ]
    },
    {
      "claim": "The loss of these advisers has created significant..",
      "verified": "true",
      "references": [
        {
          "text": "Iran leader Khamenei sees his inner circle hollowed ou...",
          "link": "https://www.cnn.com/world/middle-east/iran-lead..."
        }
      ]
    }
  ]
}

Error Handling

The table below lists the possible error codes our API response might return for improper request:

Error CodeDescription
204No content available - no relevant facts were found
400Invalid request - a valid UUID is required
400Invalid request - text length must be between 100 and 3000 characters
400Invalid request - post_text, post_link, post_date only supported with POST requests
401Unauthorized - token missing or incorrect
402Not enough API calls available

API Credits

Fact-Check is offered as a premium feature. While a regular NBDR request counts as 1 API call, every Fact-Check request counts as 5 API calls toward the user’s total usage.