Verify this file
The Parquet files are built by a scheduled job from the public JSON and published as static files. Our server then fetches them, hashes them and signs the result with the same Ed25519 key that signs every open API answer. This button hashes the exact bytes your browser downloaded (the same bytes DuckDB queries) and checks that signature against the published key. No step trusts this page's word.
Schema
Loading the manifest…
What the columns mean, and what they do not
- checks_public (0 to 6): how many of the six buyer checks the project makes public: permit, deposit protection, construction progress, plans, developer track record, no guaranteed returns. A high number means documents are public, not that they are genuine.
- checks_confirmed (0 to 6): how many of those were confirmed by an official registry or an independent source. level_* says how each check was confirmed: registry, independent, developer (self-declared), contradicted or none.
- claims_*: developer claims we tested, by result. advertised_yield_pct is what the developer advertises, not a return anyone has measured.
- Projects are anonymous (ids like BALI-014) until verification is complete. The file holds the fields already public in /data/bali-cases.json and nothing else. Some markets have only one or two projects: averages there say little, so the example queries filter small groups out.
Use it outside the browser
Files: kolaboro.parquet · kolaboro-markets.parquet · manifest · signed manifest · public keys. Licence CC BY 4.0, credit Kolaboro. AI agents can query the same data through our MCP server.
Not financial or legal advice. Scores describe what each developer makes public, checked against registers and independent sources where we could. See how we score.