agentpay — card-funded wallets for AI agents

Claim a bounty

claim_bounty

Claim a bounty for this wallet. Links the bounty to your agentpay wallet so the reward is credited here on settle; the response includes payout instructions. Pass workerAccount/workerPubKey (BSV identity) to bind trust.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bountyId": "<bountyId>"
    },
    "name": "claim_bounty"
  }
}

Input Schema

Name	Required	Description
`key`	No	Agent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
`bountyId`	Yes	Bounty id from list_bounties
`workerPubKey`	No	BSV worker identity key
`payoutAddress`	No	Optional BSV P2PKH payout address for direct sats
`workerAccount`	No	BSVBounties account # doing the work

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 11, 2026

addedInput schema / properties / payoutAddress

Added value: +{
+  "description": "Optional BSV P2PKH payout address for direct sats",
+  "type": "string"
+}

addedInput schema / properties / workerAccount

Added value: +{
+  "description": "BSVBounties account # doing the work",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / workerPubKey

Added value: +{
+  "description": "BSV worker identity key",
+  "type": "string"
+}

AddedSep 11, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It does add useful behavioral context: the reward is credited on settle and the response includes payout instructions, which hints at a state-changing, wallet-bound operation. However it doesn't state auth/permission requirements, whether claiming is idempotent or reversible, or what happens if the wallet is mismatched.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action and then the wallet-binding consequence. No wasted filler; flows from action to effect to identity requirement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate: with 100% schema coverage and no output schema, the main gaps are where it sits in the bounty lifecycle (claim -> submit_work -> settle) and permission requirements. The description covers action, outcome, and a key optional param but leaves lifecycle context thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all five parameters including identity binding. The description's mention of workerAccount/workerPubKey as 'BSV identity' to 'bind trust' adds semantic color beyond the schema, but not enough to exceed the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb+resource ('Claim a bounty') and it explicitly states the side effect — linking the bounty to the agentpay wallet so the reward is credited on settle. This distinguishes it from siblings like get_bounty (read) and settle_bounty (settlement).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage context (you claim bounties found via list_bounties, and the wallet binding matters for crediting), but never states when NOT to use it or how it relates to submit_work/settle_bounty in the workflow. No explicit alternatives or preconditions named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agentpay — card-funded wallets for AI agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?