Provenance

Verify an answer.

Every answer Quinn produces is signed with an Ed25519 key. Anyone can check that an answer is the answer we gave — with no account, no API key, and no need to trust us.

The public key

This is the key that signs every receipt. It is served without authentication:

curl -s https://quintarthai.com/api/v1/lineage/pubkey

{
  "algorithm": "ed25519",
  "public_key_hex": "0837d21d8c4f0396c4df8adb1bb4738d3d07b599786bc9eec308076e04728fab",
  "note": "Verify any receipt’s signature over its signed_payload with this key."
}

Checking a receipt

Each answer carries a receipt id. Pass it to the verifier — also keyless:

curl -s https://quintarthai.com/api/v1/lineage/verify/<receipt_id>

The response tells you whether the signature holds over the stored payload:

{
  "receipt_id": "...",
  "signature_valid": true,
  "disputed": false,
  "algorithm": "ed25519",
  "payload": { ... }
}

You do not have to take our word for that response either. The payload is the exact material that was signed — you can verify the signature yourself, offline, against the public key above.

What the receipt contains

Deliberately, the receipt does not contain your question or the answer text. It carries their SHA-256 hashes, so a receipt can be shared and checked without exposing the conversation.

Field	What it is
`query_sha256`	SHA-256 of the question. Proves which question, without revealing it.
`answer_sha256`	SHA-256 of the answer. Changing one character breaks the match.
`tools_used`	Which engines and data tools ran to produce it.
`model`	Which inference path answered.
`created_at`	When it was signed.

What this does and does not prove. A valid signature proves the answer is byte-for-byte the one we produced, at the time recorded, using the tools listed. It is not a claim that the answer is correct, and it is not investment advice. It means the record cannot be quietly revised afterwards — including by us.

Disputing one

A receipt can be disputed. A disputed receipt keeps its signature but carries "disputed": true in every future verification, so the dispute travels with the record rather than being resolved out of sight.

The same principle, applied to our own results

We publish findings that go against us. The cross-border disclosure map is a worked example: we classified all 59 dual-listed pairs by filing regime and published the result — with_cross_border_divergence: 0. The breakdown matters more than the headline. 42 pairs are identical by design, because MJDS filers wrap the Canadian AIF into the SEC filing; 6 cross-file the same 10-K on SEDAR+ under NI 51-102; and 11 have no SEC filing at all — for those the zero means no US record exists to compare, not that a comparison ran and found nothing. It is a classification of filing regime, not a content diff. Every count above comes from the same public endpoint, so you can check it rather than take our word:

curl -s https://quintarthai.com/api/v1/cross-border/map