forum-labs/payfetch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYFETCH_VIA | No | Optional via= attribution slug sent on guard calls only. | |
| PAYFETCH_APPROVER | No | 1 grants approval authority. Refused with a queue-capable mode. | |
| PAYFETCH_DATA_DIR | No | Ledger, state, and config root. Default ~/.payfetch. | |
| PAYFETCH_KEY_FILE | No | Path to a mode-600 file holding a 0x-hex key. | |
| PAYFETCH_TEST_MODE | No | Any value marks receipts test:true and refuses Base mainnet quotes (Sepolia only). | |
| PAYFETCH_PRIVATE_KEY | No | 0x-hex EVM private key. | |
| PAYFETCH_CDP_API_KEY_ID | No | Coinbase CDP API key ID. | |
| PAYFETCH_CDP_ACCOUNT_NAME | No | Optional named CDP EVM account. Defaults to a stable name. | |
| PAYFETCH_CDP_WALLET_SECRET | No | Coinbase CDP wallet secret. | |
| PAYFETCH_CDP_API_KEY_SECRET | No | Coinbase CDP API key secret. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| paid_fetchA | Fetch a URL, automatically paying if it requires payment (HTTP 402, x402 protocol) — within the operator's spending policy. Free URLs are fetched normally at no cost. Use payment_quote first if you only want to know the price. Payments above the operator's approval threshold will ask the human for confirmation. Spending policy is operator-owned config; no tool can widen it. |
| payment_quoteA | Check what a paid URL costs and whether the current spending policy would allow paying it, WITHOUT paying. Returns the price, payment terms, trust-check results, and the policy decision. Spending policy is operator-owned config; no tool can widen it. |
| spend_statusA | Show today's agent spending: totals, remaining budgets overall and per host, active holds, and recent payments. Spending policy is operator-owned config; no tool can widen it. |
| list_receiptsA | Query the local payment receipt ledger (audit trail). Filter by time, host, or outcome. Spending policy is operator-owned config; no tool can widen it. |
| approve_pendingB | List or resolve payments waiting for human approval (queue mode). Approving grants a one-time re-run permission for that exact payment. It only resolves payments already queued for approval; it cannot change spending policy — no payfetch tool can widen operator-owned limits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: approving pending payments, listing receipts, fetching with payment, checking prices, and viewing spending status. No overlap in functionality.
All tool names use descriptive verbs followed by nouns in snake_case (e.g., approve_pending, list_receipts), with consistent naming patterns throughout.
5 tools is an ideal count for this server's purpose, covering the essential operations without unnecessary bloat.
Covers quoting, fetching, approving, auditing, and status checking. Minor gap: lack of a tool to cancel pending approvals or modify payments, but these might be intentionally excluded as operator-only actions.