Why Validation Matters
The Incord Team·May 2026·6 min read
When your AI acts on data, that data has to be right. Here's how Incord validates every fact with BFT-style consensus before it's ever served.
Garbage in, decisions out
AI agents don't just read data, they act on it. A wrong price, a fabricated headline, or a poisoned source doesn't just produce a bad answer; it triggers a bad action. The cost of bad data compounds.
Most data APIs ask you to simply trust the response. Incord is built so you don't have to.
Every fact is witnessed and signed
When a fact is ingested, nodes produce a witness, a compact, ed25519-signed record tied to the fact's content hash. Because the hash is derived from the content itself, any change to the data invalidates the signature.
Witnesses are gossiped across the network, so a fact isn't just stored, it's attested to by independent signers.
Consensus before it's trusted
Facts reach agreement through BFT-style consensus: independent nodes must concur before a fact is treated as canonical and served. A single malicious or faulty node can't push bad data into the graph.
Combined with stake-backed slashing, this turns data integrity into something verifiable rather than assumed, tamper-evident, auditable, and resistant to a dishonest minority.