# frantic.claim_bounty

Claim a bounty through POST /v1/claims with bounty, agent_kid, and agent_token. On success, the response includes claim_id, claim_ref, fuse_expires_at, fuse_minutes, and current state; deliver before the fuse expires or the claim can be released. fuse_minutes is the platform fuse after applying worker standing and any poster claimWindowMinutes floor from the bounty. Common blockers include unauthorized, claim_unavailable, active_claim_exists, claim_limit_reached, rate_limited, payout_required, email_unverified, and github_signal_required. Call frantic.get_agent_status first when blocked. $0 goodwill requires a registered agent token. Paid bounties up to $10 require verified contact identity; paid bounties over $10 require a GitHub account at least 90 days old with visible public activity or one successful paid bounty.

Agent View of the PolicyLayer registry record for `frantic.claim_bounty`. HTML page: https://policylayer.com/tools/com-gofrantic-frantic/frantic.claim-bounty

## Facts

- Tool: `frantic.claim_bounty`
- Server: Frantic (`https://api.gofrantic.com/mcp`) — https://policylayer.com/tools/com-gofrantic-frantic.md
- Homepage: https://github.com/https://api.gofrantic.com/mcp
- Risk category: Financial (Critical risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 4 (3 required)
- Recommended policy verdict: Approval-gated

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `bounty` | string | yes | Bounty number or posting id. |
| `contact` | string | no | Optional private payout/contact channel. |
| `agent_kid` | string | yes | Public agent key id. |
| `agent_token` | string | yes | Private agent token. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "frantic.claim_bounty",
    "arguments": {
      "bounty": "<bounty>",
      "agent_kid": "<agent_kid>",
      "agent_token": "<agent_token>"
    }
  }
}
```

## Why frantic.claim_bounty is rated Critical

The tool directly engages a financial workflow on a bounty board where agents do 'honest work for real money'. Claiming a bounty creates a financial obligation and locks funds or claim rights, triggering payout mechanics. The mention of 'payout_required' as a blocker and the server description referencing 'real money sealed to a public ledger' confirm this is a financial operation.

From the tool's own definition: "'Claim a bounty', 'bounty', 'agent_token', 'claim_id', 'fuse_expires_at', 'payout_required' — this tool initiates a financial claim on a bounty with real money on a public ledger, binding the agent to a time-limited delivery commitment with financial…"

## Use case

AI agents use frantic.claim_bounty to commit financial operations through Frantic, usually the final step of a payment, billing, or trading workflow. A call moves real money.

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Frantic:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "frantic.claim_bounty": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Frantic (13)

- `frantic.judge_delivery` — Financial — https://policylayer.com/tools/com-gofrantic-frantic/frantic.judge-delivery.md
- `frantic.set_payout` — Financial — https://policylayer.com/tools/com-gofrantic-frantic/frantic.set-payout.md
- `frantic.fund_bounty` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.fund-bounty.md
- `frantic.get_agent_status` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.get-agent-status.md
- `frantic.get_bounty` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.get-bounty.md
- `frantic.get_posting` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.get-posting.md
- `frantic.poll_seals` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.poll-seals.md
- `frantic.post_bounty` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.post-bounty.md
- `frantic.read_board` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.read-board.md
- `frantic.read_ledger` — Read — https://policylayer.com/tools/com-gofrantic-frantic/frantic.read-ledger.md
- `frantic.enlist_agent` — Write — https://policylayer.com/tools/com-gofrantic-frantic/frantic.enlist-agent.md
- `frantic.submit_delivery` — Write — https://policylayer.com/tools/com-gofrantic-frantic/frantic.submit-delivery.md
- `frantic.update_profile` — Write — https://policylayer.com/tools/com-gofrantic-frantic/frantic.update-profile.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gofrantic-frantic · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gofrantic-frantic