Answers that show their work.
Orves Kore is knowledge for AI agents and for companies. Every fact links to the exact place it came from. Anything that cannot be proven is marked as unproven, never guessed.
# create a Kore for one customer POST /v1/kores { "name": "acme-corp" }
{ "claims": [
{ "text": "The contract renews on September 1, 2026.",
"verdict": "SUPPORTED",
"source": "amendment_v2.pdf · p.4 ¶3" },
{ "text": "Renewal may be postponed again.",
"verdict": "ABSTAINED" } ] }Proof is built in, not bolted on.
Facts, not paragraphs
Every answer is split into facts. Each links to the exact source and is marked supported, contradicted or unproven.
Says “I don’t know”
When a statement cannot be proven from the sources, Orves Kore says so instead of inventing an answer.
Conflicts are kept
Conflicting sources are never silently overwritten. Both are kept, with the history of what was known and when.
Verifiable offline
An answer bundle carries its facts, sources and verdicts, so it can be verified offline without trusting us.
A Kore per customer
Create one Kore for the company, for each team or for each of your own customers. Kores per user work as memory for an agent. The Platform API adds contradiction alerts and cryptographic deletion.
Private by default
The customer operator cannot read an end user’s Kore without that user’s explicit, revocable consent. Customer data is never used to train models.
From source to proven answer.
Sources
Your documents and recordings, brought in through Orves Ingest.
Orves Kore
Facts are stored with sources, history and conflicts.
Facts and verdicts
Each fact is supported, contradicted or unproven.
Answer bundle
An answer you can verify on its own.
Measured before claimed.
We publish a quantitative claim only when a benchmark receipt exists and is linked. None exists yet, so no number appears here. Benchmark coming.
Delivery
Use the Platform API over REST and MCP, with SDKs. Nothing to host.
Where your work happens
REST, MCP and SDKs all return the same proof with every answer.