Meridian Give · Docs

Charity money you can follow, dollar by dollar.

Everything you need to give, receive or build with Meridian Give. Start with why it exists, then pick your path.

01

The problem

A donation today travels through a chain of intermediaries: the card network, the payment processor, the bank, often a fundraising platform. Each can take a cut, each can slow the money down, and the donor rarely sees where it ends up. Charities that work across borders also face banks that delay, question or refuse their transfers.

02

What a public ledger changes

On a public ledger, a donation is a transaction anyone can read: which address sent it, how much, to whom and when. No bank sits in the middle, and the record cannot be edited after the fact. The receipt is the transaction itself, readable by the donor, the charity and the tax office without asking anyone.

03

What Meridian Give adds

Each charity gets its own escrow on Arc, a contract with no owner that cannot take a fee. Donors sign up with a passkey instead of a seed phrase, with network fees sponsored. Merchants add round-up at checkout, and AI agents give through an API, ranked by what they actually did.

Pick your path

For donors

Donate in three steps

No browser extension, no seed phrase, and no fee taken by Give on the way.

  1. 1

    Pick a verified charity

    Browse the charities. Each one has its own page with its escrow, what it has received and what it has released.
  2. 2

    Sign up with a passkey, or connect a wallet

    A passkey uses Face ID, Touch ID or your device passkey. The network fee on Arc is sponsored for passkey wallets. If you already have a wallet, connect it instead.
  3. 3

    Send USDC to the escrow

    The donation is a transaction on Arc, and the transaction is your receipt: open it on the Arc explorer to see the escrow, the amount and your address.
USDC is the digital dollar issued by Circle. Meridian Give runs on Arc testnet today; an independent audit of the contracts and the front end comes before any move to mainnet.

For charities

Receive donations with your own escrow

An escrow is a contract on Arc that holds donations for one charity. Yours has no owner, no custodian and no upgrade key, and it cannot take a fee.

  1. 1

    Register

    Start from Register your NGO. The onboarding deploys your escrow on Arc through the Arcarius factory, with the address that will receive the funds.
  2. 2

    Receive

    Donations arrive in the escrow from the moment it exists, from donors, merchants and AI agents alike. Every one is a public transaction.
  3. 3

    Release

    release() sends what the escrow holds to your beneficiary address. Anyone can call it, so the money cannot be held back, and that step is public too.
Charities shown as verified on Give carry a Meridian-verified attestation in the public registry (/api/give/registry). Your due-diligence obligations as a charity stay yours; Give provides the rail and the public record.

For merchants

Round-up at checkout

Turn the change your customers would ignore into donations, settled on Arc.

Round-up with Meridian Pay

Merchants using Meridian Pay can turn on round-up in one click. A customer rounds the purchase up to the nearest dollar, and the difference goes to a charity the merchant chooses.

Nano-donations

Donations from $0.01 USDC, accumulated and settled on Arc in batches: for API calls, AI agents or any interaction small enough that each one should give a little.

For AI agents

Let an AI agent give

Four surfaces, one tool catalogue. Agents that hold an ERC‑8004 identity are ranked on the Agent leaderboard.

MCP server

Streamable HTTP, JSON responses, authenticated with an API key in the Authorization header.

Endpoint
POST https://give.themeridian.finance/api/agents/mcp
Authorization: Bearer <MCP_API_KEY>
ToolWhat it does
list_charitiesList verified charities accepting USDC donations on Arc, with optional filters by category, country, query, and verified-only.
get_charityLook up a single charity by escrow address (preferred) or by exact registry name.
donateDonate USDC to a charity escrow.
deploy_escrowDeploy a new Arcarius escrow for a beneficiary wallet.
get_protocol_statsAggregate protocol-wide stats: total donated, total released, charity count, donor count, donation count.

x402 donation endpoint

Without credentials the endpoint answers 402 Payment Required with the challenge; with the key it donates and returns the transaction. The donation amount is the price, nothing on top.

curl
curl -X POST https://give.themeridian.finance/api/agents/donate \
  -H "Authorization: Bearer <MCP_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"charity":"0x...","amount":"10","memo":"agent-of-record:my-agent"}'

Public JSON, no key

The ranking of donor agents, read from the chain and refreshed every five minutes, and the registry of verified charities. Amounts are USDC base units, six decimals.

Agent leaderboard
curl -s https://give.themeridian.finance/api/v1/agents | jq '.agents[0]'
Charity registry
curl -s https://give.themeridian.finance/api/give/registry | jq '.escrows[].name'

Contracts and network

Everything on Arc testnet

The addresses Give reads and writes, each one linked to the Arc explorer.

  • Arcarius factoryDeploys one escrow per charity.Explorer
  • USDCIssued by Circle; the native token on Arc.Explorer
  • ERC‑8004 IdentityRegistryAgent identities.Explorer
  • ERC‑8004 ReputationRegistryFeedback left on agents.Explorer
  • ERC‑8004 ValidationRegistryValidation requests and answers.Explorer
Network
Arc testnet
Chain ID
5042002
RPC
https://rpc.testnet.arc.io

Glossary

The words, plainly

The few terms this page and the rest of the site rely on.

USDC
A digital dollar issued by Circle, redeemable one for one.
Arc
The network Give runs on, where USDC is also what pays network fees.
Escrow
A contract that holds a charity’s donations until they are released to it.
release()
The call that sends an escrow’s balance to the charity. Anyone can make it.
Passkey
A sign-in tied to your device (Face ID, Touch ID), used here instead of a seed phrase.
ERC‑8004
A standard for AI agent identity, reputation and validation, recorded on chain.
x402
An HTTP pattern where a request is answered 402 Payment Required until it is paid.
MCP
Model Context Protocol, the way AI assistants call external tools.

Help

Still a question?

The FAQ answers the common ones in a minute, and a person answers the rest.

Read the FAQ