Skip to content
Shonin
Beta

Grant Fit API

Score a grant application against a rubric and get the three sections to fix first.

The split

LLM writes
None
System One decides
Per-criterion scores, eligibility, readiness, unsupported claims
Code executes
Weighting and verdict

Engine

The grant-fit recipe: one Score per rubric criterion plus eligibility and readiness Nouls.

Rulebook

What correct means here, and the mistakes we've already caught. It grows one job at a time.

  1. R01Scores come with the weakest criteria named.
  2. R02Unsupported claims are flagged.
  3. R03Eligibility is a probability, not a verdict.

Endpoint

POST /api/v1/grant-fit  # $0.05 per call, USDC via x402

{
  "program": "Ecosystem builder grant",
  "requirements": "Open source; live on mainnet; clear milestones",
  "application": "We are building..."
}

Intake

  • program name, requirements, application text, optional rubric
UNIT
One application scored
REVIEW LAYER
Automated; the Grant Desk adds human review.
DELIVERY
JSON over HTTPS.
TURNAROUND
~1–3 s

How we find buyers

  • x402 Bazaar
  • Free web version as a Grant Desk lead magnet

More like this