saascode
legal, compliance & regtech·run 94 · May 2026

Ninetyhinge

A foundation screening API separating party identity evidence, official list snapshots, media findings, nonprofit-status records, expenditure-responsibility questions, specialist review and grant decisions.

Genesis score6.52/10
Make Ninetyhinge real.0/500
500 more votes and Ninetyhinge is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Foundations, donor-advised funds and grantmakers may screen incoming major contributions and outgoing grants against sanctions, nonprofit-status and internal due-diligence requirements. The supplied research confirms freely downloadable official sanctions data, a commercial consolidated screening dataset and expensive enterprise alternatives. It reports no reviewed foundation-specific product combining these sources with expenditure-responsibility questions. Several related interfaces were unverified in the earlier stage, and the consolidated dataset requires a commercial license.

Ninetyhinge would preserve organization, case type, incoming donor or outgoing grantee, subject type, legal name, alias, date or year of birth if lawfully available, country, registration identifier, address assertion, identity evidence, source limitation, list source, list version, list effective time, candidate name match, match score, matching fields, conflicting fields, politically exposed-person candidate, adverse-media article, publisher, publication date, allegation summary, disposition unknown, nonprofit-eligibility source, eligibility record, revocation record, group-exemption assertion, expenditure-responsibility question, internal policy version, jurisdiction assertion, analyst finding, qualified legal or grants finding, subject notice where appropriate, correction, appeal, owner decision, payment or grant instruction, provider acknowledgment, destination readback, ongoing-review date, closure and deletion as distinct records.

A name match does not establish identity, sanctions status, political exposure or wrongdoing. Media allegations can be false, outdated, duplicated or irrelevant, and must never become a hidden guilt score. An eligibility listing may not resolve whether a particular grant, donor, expenditure or foreign organization is permitted. Expenditure responsibility is a legal and grants-administration process, not a model score. The API must not block funds, approve or reject donors or grantees, accuse subjects, file reports or infer political beliefs. Qualified reviewers retain authority and subjects need correction or appeal routes where appropriate.

The pilot should use synthetic donors and grantees, public list fixtures, fictional media and valueless payment events. The likely buyer is a foundation compliance, grants-operations, finance or donor-services owner, but case volume, policy scope, data licensing, identity evidence, review staffing, legal workflow, budget and willingness to adopt a specialist layer remain unverified.

Who pays — and why

A foundation compliance, grants-operations, finance or donor-services owner responsible for qualified review of incoming contributions and outgoing grants.

What it unlocks
An identity-resolution packet separating names, aliases, registration identifiers, addresses, identity evidence, source limitations, candidate matches and conflicts
A versioned screening record separating official list snapshots, politically exposed-person candidates, media allegations, nonprofit eligibility, revocation and group-exemption assertions
A review workflow separating expenditure-responsibility questions, internal policy, analyst findings, qualified legal or grants findings, notice, correction, appeal, owner decisions, payment readback and ongoing review
How Genesis scored it
6.52across seven criteria
tension 6temporal 8blindspot 5buyer 8leverage 8convergence 5why-not 5
8
Temporal window

The supplied record identifies recent disclosure and funding signals supporting current due-diligence attention.

8
Buyer persona

Foundation compliance, grants, finance and donor-services owners are actionable, while case volume and budget need validation.

5
Why nobody did it

The foundation-specific workflow gap is clear, but no strong structural barrier prevents incumbent expansion.

Why it scored well

The input identifies a clear foundation buyer, available official and licensed screening sources, and a specific grants-administration workflow absent from reviewed products.

What's holding it back

Several interfaces were unverified, identity resolution and media review require specialists, licensed data adds cost and general screening vendors can add foundation rules.

Signals detected3 sources crossed
SignalSupplied government-data research

SignalSupplied data-provider research

SignalSupplied competitor search

Direction briefninetyhinge.md
ninetyhinge.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.