Our own visit statistics are always on. Google Analytics, which helps us understand how people use our public pages (not your signed-in workspace), is enabled only with your permission. See our Privacy policy.

EverySearch Cross-check API

POST

API health

24h health
Normal
24h average time
—
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Runs one question through several retrieval chains that work in different ways, ranks the sources by how many mechanisms found them, then fetches the original text of the top-ranked sources. It answers how far a conclusion can be trusted, and when not to trust it, rather than just what was found

Price $2.78 per 1,000 requests ($0.002778 per call). Failed calls and empty results are not charged. One call counts as 4 searches: it runs 4 retrieval chains that work in different ways. If only some of them succeed, you pay for the ones that did, never more than the listed price.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Help me write a script that calls the EveryInfra "Cross-check" API.

API contract:
- Request: POST https://api.everyinfra.com/api/v1/search with the header Authorization: Bearer <API Key>. Read the key from the EVERYINFRA_API_KEY environment variable; do not put it in the code.
- In the request body, set tool to crosscheck and put the parameters in params.
- Required parameters:
  - q: The question or claim to check.
- Optional parameters:
  - num: Number of results each retrieval chain fetches.
  - since: Only sources after this date.
  - read_top: How many top-ranked sources to fetch the original text of; 0 fetches none.
  - depth: The default mix when mechanisms is not given: quick runs keyword only, standard adds semantic, deep runs all four. (allowed values: quick / standard / deep)
  - mechanisms: The retrieval mechanisms to run; when given, depth is ignored. (allowed values: keyword / index / semantic / reasoning / community)
- Example request body:
{
  "tool": "crosscheck",
  "params": {
    "q": "Python 3.13 release date",
    "depth": "quick",
    "num": 5
  }
}
- Billing: Price $2.78 per 1,000 requests ($0.002778 per call). Failed calls and empty results are not charged. One call counts as 4 searches: it runs 4 retrieval chains that work in different ways. If only some of them succeed, you pay for the ones that did, never more than the listed price.
- On 422, fix the parameters using the suggestions and allowed values in the error. On 429 or 503, wait for Retry-After and try again.

Before writing code, ask me how many items I need to process and what format to save the results in, then confirm the plan and the rough cost with me.

Request parameters

NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
toolbodystringYescrosscheckTool name, fixed value.
qbody.paramsstringYes-The question or claim to check.
numbody.paramsinteger (1–10)No8Number of results each retrieval chain fetches.
sincebody.paramsdateNo-Only sources after this date.
read_topbody.paramsinteger (0–)No2How many top-ranked sources to fetch the original text of; 0 fetches none.
depthbody.paramsstring (enum)NodeepThe default mix when mechanisms is not given: quick runs keyword only, standard adds semantic, deep runs all four.Allowed valuesquickstandarddeep
mechanismsbody.paramsarrayNo-The retrieval mechanisms to run; when given, depth is ignored.Allowed valueskeywordindexsemanticreasoningcommunity

Code samples

bash
curl -X POST 'https://api.everyinfra.com/api/v1/search' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "tool": "crosscheck",
  "params": {
    "q": "Python 3.13 release date",
    "depth": "quick",
    "num": 5
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Real response

Captured October 24, 2026 at 18:28 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed. id, billing and quota differ on every call, so only their shape is shown.

json
{
  "id": "req_…",
    "object": "search.crosscheck",
    "query": "Python 3.13 release date",
    "lanes": [
      {
        "lane": "keyword",
        "label": "关键词索引",
        "mechanism": "keyword",
        "corpus": "open_web",
        "description": "按查询词与链接权重召回,覆盖广、时效好,但只能找到标题或正文里确实含有查询词的页面",
        "status": "ok",
        "results": 5,
        "latency_ms": 2386
      },
      {
        "lane": "index",
        "label": "索引检索",
        "mechanism": "index",
        "corpus": "open_web",
        "description": "自有网页索引,条目自带正文摘要,适合直接判断这一页说了什么",
        "status": "ok",
        "results": 5,
        "latency_ms": 5437
      }
    ],
    "independence": {
      "mechanisms_planned": 2,
      "mechanisms_live": 2,
      "lanes_planned": 2,
      "lanes_live": 2,
      "degraded": false,
      "live": [
        "index",
        "keyword"
      ],
      "missing": []
    },
    "agreement": {
      "by_url": [
        {
          "url": "https://docs.python.org/3/whatsnew/3.13.html",
          "title": "What's New In Python 3.13",
          "mechanisms": [
            "index",
            "keyword"
          ],
          "lanes": [
            "index",
            "keyword"
          ],
          "mechanism_count": 2
        },
        {
          "url": "https://peps.python.org/pep-0719/",
          "title": "PEP 719 – Python 3.13 Release Schedule",
          "mechanisms": [
            "index",
            "keyword"
          ],
          "lanes": [
            "index",
            "keyword"
          ],
          "mechanism_count": 2
        },
        {
          "url": "https://endoflife.date/python",
          "title": "Python",
          "mechanisms": [
            "keyword"
          ],
          "lanes": [
            "keyword"
          ],
          "mechanism_count": 1
        }
      ],
      "by_domain": [
        {
          "domain": "docs.python.org",
          "mechanisms": [
            "index",
            "keyword"
          ],
          "lanes": [
            "index",
            "keyword"
          ],
          "mechanism_count": 2
        },
        {
          "domain": "peps.python.org",
          "mechanisms": [
            "index",
            "keyword"
          ],
          "lanes": [
            "index",
            "keyword"
          ],
          "mechanism_count": 2
        },
        {
          "domain": "python.org",
          "mechanisms": [
            "index",
            "keyword"
          ],
          "lanes": [
            "index",
            "keyword"
          ],
          "mechanism_count": 2
        }
      ],
      "max_url_mechanisms": 2,
      "max_domain_mechanisms": 2
    },
    "unique_finds": [
      {
        "url": "https://endoflife.date/python",
        "title": "Python",
        "mechanism": "keyword",
        "lane": "keyword"
      },
      {
        "url": "https://www.reddit.com/r/Python/comments/1fybncq/python_313_released/",
        "title": "Python 3.13 released",
        "mechanism": "keyword",
        "lane": "keyword"
      },
      {
        "url": "https://thenewstack.io/python-3-13-blazing-new-trails-in-performance-and-scale",
        "title": "Python 3.13: Blazing New Trails in Performance and Scale - The New Stack",
        "mechanism": "index",
        "lane": "index"
      }
    ],
    "answers": [],
    "excerpts": [
      {
        "url": "https://docs.python.org/3/whatsnew/3.13.html",
        "mechanism_count": 2,
        "content": "### Navigation\n\n* [index](../genindex.html \"General Index\")\n* [modules](../py-modindex.html \"Python Module Index\") |\n* [next](3.12.html \"What’s New In Python 3.12\") |\n* [previous](3.14.html \"What’s new in Python 3.14\") |\n* [Python](https://www.python.org/) »\n* [3.15.1 Documentati…",
        "fetched": false
      },
      {
        "url": "https://peps.python.org/pep-0719/",
        "mechanism_count": 2,
        "content": "# Python Enhancement Proposals\n\n* [Python](https://www.python.org/ \"The Python Programming Language\") »\n* [PEP Index](../ \"Python Enhancement Proposals (PEPs)\") »\n* PEP 719\nPEP 719 – Python 3.13 Release Schedule\n\n# PEP 719 – Python 3.13 Release Schedule\n\nAuthor:\n:   Thomas Wouter…",
        "fetched": false
      }
    ],
    "verdict": {
      "level": "weak",
      "text": "⚠ 只有 2 条独立检索链在跑,交叉验证强度显著下降(满强度为 3 种以上互不相同的检索机制) 两种机制之间的一致只是弱印证:机制越少,一致越可能来自同源取材而非互相印证。请以一手原文为准。 有 2 种机制落在**同一个页面**上,这比落在同一个域名上强得多(同域名可能是不同帖子在说相反的话)。"
    },
    "notes": [],
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Errors and billing

401
Missing or invalid key.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors