# Give your agent a little room to be generous

An optional idea for people who run wallet-enabled agents. You decide whether tipping is permitted, which recipients qualify, and the per-tip and total budget, including fees. Gateway does not set that budget or authorize your agent to spend.

1. Start read-only: fetch https://gateway-wallet-payments.jerryrnapier.workers.dev/tip.json and confirm the destination and terms.
2. Set an explicit tipping policy in your own agent or wallet configuration. Permission to buy a service does not automatically permit a tip.
3. Require the agent to check the chain, token, recipient, exact amount and remaining budget before signing. It may always decline to contribute.
4. Save the private receipt and capability. Resume an uncertain payment instead of paying again.
5. After a confirmed contribution, choose separately whether to publish an anonymous supporter flower. Publication is optional and revocable with the original capability.

The existing examples default to unpaid quotes; use this discovery request for a completely read-only start:

```sh
curl --fail https://gateway-wallet-payments.jerryrnapier.workers.dev/tip.json
```

[Wallet examples](https://gateway-wallet-payments.jerryrnapier.workers.dev/agent/examples/README.md) · [MCP guide](https://gateway-wallet-payments.jerryrnapier.workers.dev/agent/mcp-guide.md)

## Let a completed run leave something good behind

When an experiment finishes, its operator may choose a one-time contribution to independent development. Select the recipient and exact amount explicitly, account for fees and unsettled activity, and authorize that contribution separately. Unused task funds are not automatically a donation budget. No balance sweep, recurring commitment, or default enrollment is offered.

[Compare supported currencies and networks](https://gatewayinformationgroup.com/tip/currencies.json) without connecting a wallet. Native BTC and cbBTC on Base are different assets. Use only an already-compatible route; no bridge or swap is required by this invitation. USDC checkout supports private receipts after confirmation. Eligible completed ETH-on-Base and native SOL transfers can use the [optional record page](https://gateway-wallet-payments.jerryrnapier.workers.dev/tip/receipt). A record requires sending-wallet ownership proof and finalized chain verification; garden publication is a separate choice. Other direct transfers currently use wallet records.

## Review a recipient before authorizing support

[Recipient review record](https://gatewayinformationgroup.com/tip/recipient-review.json) lists the beneficiary, purpose, exact supported networks, assets and recipients. Independently check the selected route, then decide whether to authorize a specific contribution and expiration. This record is not an automatically imported allowlist and grants no spending authority. Permission to buy resources is not permission to donate. No AWS AgentCore payment compatibility is claimed.

[Try the inspectable read-only n8n reference](https://gatewayinformationgroup.com/tip/n8n-read-only.md). It reads public terms, checks them and stops without payment.

## Permissions needed for each step

Allow only the exact hosts used by your chosen workflow: gatewayinformationgroup.com for public pages, and gateway-wallet-payments.jerryrnapier.workers.dev for the payment API. A permission to read the website does not also allow API requests. Do not allow all workers.dev domains.

| Step | Host and method | Effect and separate permission |
|---|---|---|
| Read the invitation | GET on gatewayinformationgroup.com/tip | Public information only. |
| Read current payment terms | GET on gateway-wallet-payments.jerryrnapier.workers.dev/tip.json or /tip.md | No quote, signature or payment. |
| Use MCP discovery or read terms | POST on gateway-wallet-payments.jerryrnapier.workers.dev/agent-tools | MCP uses POST even for initialize, tools/list and get_tip_terms. A GET-only allowance cannot use this transport. |
| Prepare an unpaid quote | POST on gateway-wallet-payments.jerryrnapier.workers.dev/api/agent/v1/tips | Creates private quote state. Requires explicit operator permission, a privately retained Authorization capability and Idempotency-Key. Does not pay. |
| Review and pay | POST to the quote's returned paymentUrl on the same exact API origin | An unsigned request obtains terms; PAYMENT-SIGNATURE submits a separately authorized wallet signature. Use the existing wallet client, verify the exact destination and terms, and never invent or redirect this URL. |
| Recover private status | GET on the API origin at /api/agent/v1/jobs/{jobId}, optionally followed by /result | Send the original private Authorization capability. Reuse the existing job after uncertainty. Pending is not settlement. |

A method allowance is not spending permission: enabling POST also does not authorize every MCP tool. prepare_tip_quote creates state; get_tip_terms does not. Private receipt tools need private client headers. Keep capabilities out of query strings, public examples and logs.

If the environment denies the required host or method, report which step is unavailable and let the operator configure that exact permission. Do not switch a POST to GET, use a proxy, or broaden network access to evade the restriction. Browser Origin/CORS checks are separate from network permissions. Wallet/RPC permissions depend on the operator's chosen wallet and must be configured there; this guide grants none.

No automatic installation, wallet connection, signature or payment is triggered by this guide.