Skip to main content

Pledge

Search nonprofits, run fundraisers and record donations through your Pledge partner account.

Connect it with: API key, MCP. Pledge's own documentation: https://developer.pledge.to/guides/getting-started/.

What agents can do​

Connect Pledge so the agents working your tasks can reach it. With it connected, they can:

  • Search Pledge's nonprofit database by name, EIN, cause or country to find the right beneficiary.
  • Create or update a fundraiser for a campaign or event and return its hosted donation page.
  • List donations for a fundraiser or date range to report on totals, donors and fees.
  • Register or remove the webhook endpoints that tell your app a donation completed.

Before you start​

  • A Pledge partner account (create one at https://www.pledge.to); a sandbox account at https://staging.pledge.to is separate and has its own key.
  • For donations created through the API: a payment method on file in the Impact Hub, which Pledge bills in batches.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Pledge​

Jaah connects to Pledge with an API key, not with a sign-in button.

Connect with an API key​

Find each value first:

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Pledge card.
  2. Name the secret and choose who can use it.
  3. Fill in API key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Pledge with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Pledge's API once (GET https://api.pledge.to/v1/webhooks) with the stored values, and shows whether Pledge accepted it, or which value Pledge refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: api_key.

Tell the agent in your task description which secret to use, for example “use the Pledge secret org/pledge”.

Pledge also runs an MCP server, which gives agents ready-made Pledge tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:

  1. Open the project and its MCP tab.
  2. Select Link, pick the Pledge secret, and confirm.
  3. New tasks on the project start with the Pledge tools. Tasks already running keep the tools they started with.

Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Pledge once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Pledge's side too, revoke or delete the key at Pledge.

Limitations​

  • Jaah tests and serves the production key only: a sandbox key is rejected by api.pledge.to, so keep sandbox work in your own app until Pledge offers a sandbox address here.
  • There is no one-click Connect Pledge: Pledge offers apps no OAuth sign-in, only a partner API key sent as a Bearer token (https://developer.pledge.to/guides/getting-started/), so the API key is the only way in.
  • Creating a donation through the API bills your payment method on file. Agents only do it when a task says so.
  • Agents can do only what the connected Pledge account allows.

Troubleshooting​

Test says Pledge rejected the API key (401)

The key is mistyped, was regenerated, or is a sandbox key. Copy the production key again from the Impact Hub's Pledge APIs section and select Replace.

Agents cannot find the Pledge tools

Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with.

Creating a donation fails with 422

The organization UUID is not eligible to receive donations. Have the agent search the nonprofit again and use the UUID Pledge returns.

Still stuck? Select Test and read the result: it names the value Pledge refused and the status it answered.

FAQ​

Does Test create anything in Pledge?

No. It lists your account's webhook endpoints and discards the answer.

How do the MCP tools get my key?

Each Pledge tool takes the API key as an argument. The agent reads it from this secret when it calls the tool, so the key never sits in the agent's configuration.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Pledge account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.