# BRAINIAC Grant Compliance Requirements Extractor

> BRAINIAC Grant Compliance Requirements Extractor is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-17).

Extracts structured grant compliance requirements from funding guidelines text and optionally cross-references them against supplied requirement items

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/grant-compliance/requirements-extract?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-grant-compliance-requirements-extractor-26daaa19
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BTYcdxmqT8y6m2vXBcQ30

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-grant-compliance-requirements-extractor-26daaa19 -d '<json body>'
```

Example prompt: Can you extract all the compliance requirements from this grant guidelines document? Here are the guidelines text and I also have two specific requirements I'd like checked: R1 'The applicant must be a registered charity' and R2 'Projects must serve the London borough'.

## When to prefer this

Use this endpoint when you need to programmatically extract and structure compliance requirements from grant or funding guidelines text, especially when no account setup or subscription is desired and pay-per-call billing via USDC on Base is preferred. It is particularly suited for agents automating grant due-diligence pipelines, nonprofit application workflows, or funding eligibility pre-screening at low per-call cost ($0.04). Prefer this over general-purpose LLM prompting when you need a consistent, schema-validated output with explicit sourcing of each requirement and built-in limitation disclosures.

## Known failure modes

- Guidelines text too long (exceeds 50,000 character limit) causing request rejection
- More than 40 requirement items submitted causing validation error
- Empty or missing guidelines field causing schema validation failure
- Requirement items missing required id or text fields
- Ambiguous or unstructured guidelines that yield no extractable labeled requirements — returns empty requirements array
- Payment not completed via x402 on Base causing 402 response before processing begins

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

A JSON object with status 'extracted', an array of parsed requirements each with an id, text, and source field indicating where in the guidelines the requirement originated, a findings array for any cross-referenced requirement items, a checkedAt timestamp, a list of limitations clarifying that compliance was not officially determined, and boolean fields officialApproval (always false) and complianceDetermined (always false).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "guidelines": {
   "type": "string",
   "maxLength": 50000,
   "minLength": 1
  },
  "requirements": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "text"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "text": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 40
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "extracted",
  "findings": [],
  "checkedAt": "2026-11-02T19:00:00.000Z",
  "limitations": [
   "This is not an official approval, and compliance was not determined.",
   "Rules, eligibility criteria, budgets, and evidence are used only when they are supplied in the request.",
   "Labeled lines are read as written. Unlabeled prose is not turned into a grant rule.",
   "A matching evidence id does not judge whether the evidence is sufficient."
  ],
  "requirements": [
   {
    "id": "R1",
    "text": "The applicant must be a registered charity.",
    "source": "guidelines"
   },
   {
    "id": "R2",
    "text": "The project must serve London.",
    "source": "guidelines"
   }
  ],
  "officialApproval": false,
  "complianceDetermined": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-grant-compliance-requirements-extractor-26daaa19/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
