About cite8

Cite8 is a citation-grounded clinical RAG service. Every clinical claim it answers links back to a peer-reviewed source. Every cited source is independently verified by a separate model against the claim it's supposed to support. The service abstains when evidence is thin. The methodology is publicly documented and every audit is reproducible via the cite8 API.

What cite8 does

Three modes of access, one underlying pipeline:

Verification — pass cite8 a clinical claim (or a full markdown article with embedded PMID / PubMed-URL / DOI citations), get back a per-citation audit: did the cited paper actually support the claim, partially support it, contradict it, or address an unrelated topic? Used as an editorial gate for health publishers.
Retrieval + synthesis — hybrid vector + keyword retrieval against a curated PubMed corpus, with reranked top-k passed to a generation model that produces cited answers. Every [N] marker in the answer resolves to a real PMID with a PubMed URL.
Abstention — if the corpus doesn't contain sources sufficiently relevant to the question, cite8 says so explicitly instead of speculating. Abstention is a first-class verdict, not a fallback.

How cite8 is used

The same cite8 deployment serves three audiences from the same core pipeline:

REST API at https://cite8.dev/api/v1/*, OpenAPI 3.1 spec at /openapi.yaml, Bearer-token auth.
MCP server at POST /mcp — Claude Code, Claude Desktop, and claude.ai custom connectors can use cite8 as a native tool with zero per-agent integration code. Setup snippets provided with API key issuance.
Human UI at https://cite8.dev/ — single-page web app for ad-hoc queries, claim verification, and corpus search.

Who operates cite8

Cite8 is operated by Talisman Health Enterprise Management, LLC. The service is offered to health publishers, agents, and clinicians as a verification API. The verification methodology is documented in detail on the verification page; partner inquiries: [email protected].

The credibility of "verified by cite8" doesn't depend on institutional independence — it depends on the verification being reproducible. Any consumer of a verified article can re-run the audit against the same markdown input by calling POST /api/v1/verify-article; the resulting per-citation verdicts will match. The audit trail is the trust signal.

Verification badge for partner sites

Sites that pass content through cite8 can embed the verification badge in their footer or per-article metadata. The badge links back to cite8's verification page, which is the canonical description of what "verified by cite8" means.

Embed snippet:

<a href="https://cite8.dev/verification" rel="noopener">
  <img src="https://cite8.dev/badge.svg" alt="Verified by cite8" width="160" height="48" />
</a>

Stable identifiers

Cite8's Schema.org Organization entity has a stable @id of https://cite8.dev/#org. Health publishers integrating verification into their JSON-LD should reference this @id in reviewedBy or verifier properties:

{
  "@context": "https://schema.org",
  "@type": "MedicalWebPage",
  "headline": "...",
  "author": { "@type": "Person", "name": "..." },
  "reviewedBy": {
    "@type": "Organization",
    "@id": "https://cite8.dev/#org"
  },
  "lastReviewed": "2026-05-27"
}

The @id survives hostname changes, redirects, and the eventual production migration to cite8.dev as the primary domain. Reference the @id, not the URL.