Install Jentic One Beta

Connect the Good Grants API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Good Grants API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgood-grants%2Fgood-grants" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgood-grants%2Fgood-grants" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Good Grants API.

Create and update applications submitted to a grant round

Allocate budget across applications, categories, and rounds

Build and version application forms with custom fields and chapters

Manage contributors and reviewers with role-based access to a round

Record and reconcile payments disbursed to successful applicants

GET STARTED

Start building with Good Grants API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Good Grants API for, with concrete tasks.

★ External Application Portal

Grant-making organisations build custom-branded portals that submit applications via the Good Grants API while keeping all programme management inside Good Grants. The API's forms and fields endpoints expose the form schema so the portal renders the same questions, and POST /application creates the record under the chosen round.

Render form form_xyz from /form/{slug} on a custom portal and POST a completed application against round round_2026.

Award Disbursement Reconciliation

Finance teams reconcile awarded grants by reading allocations and payments through the API, matching them against bank-side disbursements, and updating fund balances. The /allocation and /payment endpoint groups give a single source of truth for how much of each fund has been committed and paid.

List all payments for season season_2026 and produce a CSV showing applicant, amount allocated, and amount paid.

Review Committee Workflow

Programme managers add contributors with reviewer roles to a round, assign applications for scoring, and progress applications through stages as scores come in. Webhook subscriptions push status changes back to a Slack channel or CRM so the committee tracks progress without polling.

Add user@example.com as a reviewer on round round_q2 and subscribe a webhook to fire when any application in that round changes status.

AI Triage Agent via Jentic

An AI agent can read incoming applications, flag missing documents, and assign reviewers based on subject expertise - all by calling the Good Grants API through Jentic. The agent searches for the right operation by intent, loads the schema, and executes against the regional Good Grants base URL with the x-api-key held in the vault.

List applications in round round_q2, fetch each application's documents, and tag any application missing the required budget document.

Key Endpoints

81 endpoints — the good grants api exposes 81 endpoints for managing the full lifecycle of a grant or award programme, covering accounts, applications, allocations, categories, chapters, contributors, documents, fields, forms, funds, payments, rounds, seasons, users, and webhooks.

METHOD

PATH

DESCRIPTION

GET

/application

List applications

POST

/application

Create an application

GET

/allocation

List allocations

POST

/allocation

Create an allocation

POST

/action-task

Create an action task

GET

/account

Get account details

GET

/application

List applications

POST

/application

Create an application

GET

/allocation

List allocations

POST

/allocation

Create an allocation

POST

/action-task

Create an action task

GET

/account

Get account details

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Good Grants by hand means implementing its x-api-key header auth and picking the right regional host (api.cr4ce.com or its au, ca, and eu variants) for the account, then mapping the application and allocation endpoints yourself. Through Jentic you install once, import Good Grants from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Good Grants works through top-level resource endpoints like /application and /allocation rather than a resource id in the URL path, so scope the agent to the operations it needs, such as listing applications or reading allocations. You choose the operations it may call, so ones like creating an application or an action-task are not included unless you add them.

Credential isolation

Your Good Grants API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list grant applications' or 'read allocations for a round', and Jentic returns the matching Good Grants operation with its query and body schema so the agent calls the right endpoint without browsing the reference.

FAQs

Specific to using Good Grants API through Jentic.

What authentication does the Good Grants API use?

The Good Grants API uses an x-api-key header (apiKey scheme) issued per Good Grants account. Through Jentic the key is stored encrypted in the vault and scoped to the matching regional base URL, so the raw key never enters the agent's context.

Can I create applications programmatically with the Good Grants API?

Yes. POST /application creates an application against a round, and you can attach answers, contributors, and uploaded documents through the related /document and /field endpoints. This lets you build a custom-branded portal that hands off to Good Grants for review and disbursement.

What are the rate limits for the Good Grants API?

Good Grants applies per-tenant rate limits documented at goodgrants.com/help. The OpenAPI spec does not encode exact numbers, so check the support portal before running bulk imports - list endpoints such as GET /application support pagination and should be used in batches.

How do I subscribe a webhook through Jentic?

Search Jentic for 'subscribe webhook good grants', load the schema for POST /webhook, and execute with the event type and target URL. Jentic injects the x-api-key at execution and returns the webhook ID, which the agent persists for later management.

Can I keep my data in a specific region?

Yes. Good Grants exposes regional base URLs - api.cr4ce.com (global), api.au.cr4ce.com, api.ca.cr4ce.com, api.eu.cr4ce.com, api.hk.cr4ce.com, api.ae.cr4ce.com, and api.us.cr4ce.com - and your account is provisioned against one of them. Use the matching server when configuring a client.

Does the API handle automated scoring of applications?

No. The API records reviewer scores and progresses application status, but the scoring logic itself is configured in the Good Grants UI as part of the round setup. Use the API to read scores and update application status based on them.

Can I limit what my agent is allowed to do with the Good Grants API?

Yes. Because you self-host Jentic One, your own rules decide which Good Grants operations and credentials the agent may use. The API exposes top-level resource endpoints such as /application and /allocation, so you can grant read-only operations like listing applications or reading allocations while leaving out write operations. Operations such as creating an application or an action-task stay unavailable unless you explicitly add them.

Good Grants API

Name: Good Grants API
Brand: Good Grants API
Availability: InStock

Community OpenAPI document · agent-readyProductivityForms SurveysapiKey81 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage every part of a grant or awards programme - applications, forms, rounds, scoring, payments, and webhooks - through 81 endpoints across regional Good Grants servers.

Use for: Create a new application for a grant round on behalf of an applicant, I want to update the status of an application after a review committee meeting, List every application submitted to a specific season, Allocate £50,000 of a fund to a winning application

Not supported: Does not handle bank disbursement execution, applicant identity verification, or grant-writing content generation - use for grant programme management (applications, forms, rounds, allocations, payments record-keeping, contributors, webhooks) only.

The Good Grants API exposes 81 endpoints for managing the full lifecycle of a grant or award programme, covering accounts, applications, allocations, categories, chapters, contributors, documents, fields, forms, funds, payments, rounds, seasons, users, and webhooks. It supports regional base URLs (Global, AU, CA, EU, HK, AE, US) so customers can keep data within a specific jurisdiction. Authentication is an x-api-key header, and the resource model maps directly to how grant administrators design rounds, build application forms, score submissions, and disburse funds.

Jentic One on Github View OpenAPI Document

Connect the Good Grants API to your agent

Capabilities

Start building with Good Grants API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Good Grants API