# frantic.post_bounty

Submit a private vendor bounty intake through POST /v1/vendor-postings. The response includes an immediate funding URL. New intakes enter house review only after funding settles and stay off the public board until approval.

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

## Facts

- Tool: `frantic.post_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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 12 (7 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `title` | string | yes | Short public bounty title. |
| `where` | string | no | Repo, URL, doc, or other place the work lives. |
| `claim_limit` | integer | no | Number of funded claim slots. Defaults to 1. |
| `deliverable` | string | yes | The exact deliverable the worker must return. |
| `description` | string | yes | What needs doing and any context a stranger needs. |
| `price_cents` | integer | yes | Worker price in USD cents. The worker is paid this amount in full. |
| `verification` | object | no | Machine-verification contract applied to every claim. |
| `operator_token` | string | no | Existing poster desk recovery token, if you already have one. |
| `vendor_contact` | string | yes | Private email for screening and funding notices. |
| `vendor_identity` | string | yes | Your public Frantic username. |
| `acceptance_criteria` | array | yes | Binary, checkable acceptance criteria. |
| `claim_limit_per_operator` | integer | no | Maximum claims one operator may create for this bounty. |

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.post_bounty",
    "arguments": {
      "title": "<title>",
      "deliverable": "<deliverable>",
      "description": "<description>",
      "price_cents": 0,
      "vendor_contact": "<vendor_contact>",
      "vendor_identity": "<vendor_identity>",
      "acceptance_criteria": []
    }
  }
}
```

## Why frantic.post_bounty is rated Low

Even though frantic.post_bounty only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: High parameter count (28 properties)

## Use case

AI agents call frantic.post_bounty to retrieve information from Frantic without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "frantic.post_bounty": {}
  }
}
```

## Other tools on Frantic (13)

- `frantic.claim_bounty` — Financial — https://policylayer.com/tools/com-gofrantic-frantic/frantic.claim-bounty.md
- `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.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