Project
A workspace holds related analyses, cases, profiles, evidence, and results.
Proof by QuantBayes
QuantBayes Studio turns your analysis into evidence-based conclusions. A community agrees what evidence is needed to verify work. QuantBayes lets you fulfil that checklist and trust your results.
A workspace holds related analyses, cases, profiles, evidence, and results.
A case holds the items being evaluated, such as AI outputs, engineering checks, clinical findings, design decisions, claims, targets, or review tasks.
A community or team defines the checklist of evidence required before scoring begins.
The user, pipeline, or agent adds evidence against each rule in the selected profile.
QuantBayes scores evidence sufficiency and returns uncertainty for every item.
The result is saved with its profile, evidence matrix, and audit trail.
Why it is trustable
A user, team, or community chooses the evidence rules that a result must satisfy.
Each answer, claim, finding, or decision is reviewed step by step, including missing evidence.
The QuantBayes engine measures evidence sufficiency and saves the full trail for review, including confidence intervals.
Works with
AI outputs, agent workflows, clinical findings, engineering checks, research claims, design decisions, and regulatory review.
Evidence made visible
Use the scientific method as an operating system for decisions: define the evidence, test the result, update confidence, and keep the full trail. Apply the same formal method wherever evidence matters, from AI outputs and clinical findings to design decisions, engineering checks, and automated workflows.
Where it fits
A profile defines what evidence is required. A case records the items being evaluated. A run saves the evidence matrix and the QuantBayes result.
Check whether an answer is supported by declared sources, evidence rules, and inspection steps.
Require an agent to return evidence against each rule before a result is accepted.
Turn literature claims, methods, datasets, and assumptions into inspectable evidence checks.
Review candidate findings against a versioned profile before ranking evidence sufficiency.
Confirm that design, test, safety, and release criteria have been checked.
Preserve the profile, evidence matrix, result, and report for later review.
API proof workflow
QuantBayes Studio is not another model. It is an evidence layer that can sit beside any model, agent, pipeline, or human review process.
The checklist is known before evidence sufficiency is scored.
Each item is checked against each rule using TRUE, FALSE, or NA.
The output is stored with the profile, matrix, result, and audit trail.
import os
import requests
qb_base_url = os.getenv("QB_BASE_URL", "http://localhost:3000")
qb_api_key = os.getenv("QB_API_KEY")
response = requests.post(
f"{qb_base_url}/api/v1/runs",
headers={
"Authorization": f"Bearer {qb_api_key}",
"Content-Type": "application/json"
},
json={
"case_uid": "analysis_001",
"profile_uid": "ai_evidence_review_v1"
},
timeout=30
)
response.raise_for_status()
print(response.json())library(httr)
library(jsonlite)
qb_base_url <- Sys.getenv("QB_BASE_URL", "http://localhost:3000")
qb_api_key <- Sys.getenv("QB_API_KEY")
res <- POST(
paste0(qb_base_url, "/api/v1/runs"),
add_headers(
Authorization = paste("Bearer", qb_api_key),
"Content-Type" = "application/json"
),
body = toJSON(
list(
case_uid = "analysis_001",
profile_uid = "ai_evidence_review_v1"
),
auto_unbox = TRUE
),
encode = "raw"
)
fromJSON(content(res, as = "text", encoding = "UTF-8"))curl "$QB_BASE_URL/api/v1/runs" \
-H "Authorization: Bearer $QB_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"case_uid": "analysis_001",
"profile_uid": "ai_evidence_review_v1"
}'FAQ
No. It is an evidence verification layer. It can be used beside AI models, agents, scientific pipelines, or human review workflows.
No. It measures evidence sufficiency under a declared rule set. The result remains tied to the evidence profile and checked evidence.
Yes. A model can produce an answer, plan, source list, or analysis. QuantBayes Studio can then verify the evidence record against a profile.
A profile is a reusable checklist of evidence rules. It defines what must be checked before a result is trusted.
A run saves the profile, evidence matrix, QuantBayes result, parameters, and report. This makes the result inspectable later.
No. The QuantBayes engine came from scientific evidence analysis, particularly clinical genetics, but QuantBayes Studio is general. It can be used for AI, research, engineering, clinical, and regulatory workflows.
A compact internal map for reviewing the current product flow while the Studio interface is still being refined.
| Order | Page | Purpose | Link |
|---|---|---|---|
| 1 | Studio | Main project, profile, case, and run workbench | Open |
| 2 | Profile database | Browse and compare evidence profiles | Open |
| 3 | New profile | Build or upload a reusable evidence profile | Open |
| 4 | Demo QEM case | Case evidence table with the selected profile | Open |
| 5 | Newest demo result | Saved result display with distribution plot and credible intervals | Open |