Check application completeness API

Mark a requirement present only when an application section cites its id. The answer is not scored, and a complete set is not compliance.

The Check application completeness operation is part of the Grant Compliance API on BRAINIAC.software. Mark a requirement present only when an application section cites its id. The answer is not scored, and a complete set is not compliance. It is exposed as POST /api/v1/grant-compliance/application-completeness and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Grant guidelines, application text, budgets, evidence, and rules supplied in the request. Limitations: Grant rules, eligibility criteria, and approval outcomes are not invented. A met rule or a balanced budget is not an official approval or a compliance determination. Requirements, deadlines, and reporting obligations are read only from labeled lines or structured fields. Evidence is matched by the supplied requirement id. The strength of the evidence is not judged. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Extract grant requirements, Check supplied eligibility rules, Validate a grant budget, Check expenses against supplied rules. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/grant-compliance/application-completeness

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/grant-compliance/application-completeness" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "requirements": [
    {
      "id": "R1",
      "text": "The applicant must be a registered charity."
    },
    {
      "id": "R2",
      "text": "The project must serve London."
    }
  ],
  "sections": [
    {
      "requirementId": "R1",
      "text": "We are a registered charity."
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Grant Compliance APIFull docsHow it works