# Dev Request Prioritizer — REST API endpoint `dev-request-prioritizer`

Prioritize development requests with the page's scoring frameworks and return them sorted by priority score, each with a value score and an effort/value quadrant (quick win, big bet, fill-in, money pit), plus a top recommendation and totals. Frameworks: "default" (weighted value ÷ √effort over Customer Impact, Revenue Impact, Strategic Value, Urgency, Risk), "rice", "ice", "wsjf", "moscow". Score each request 1-10 per dimension, keyed by dimension name; optional confidence weighting and a deadline boost (+20% within 7 days, +50% within 3, +100% overdue, capped by deadline_boost_multiplier).

- Category: productivity
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/dev-request-prioritizer/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/dev-request-prioritizer/
- Same tool on the other surface: https://findutils.com/mcp/dev-request-prioritizer/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/dev-request-prioritizer/execute \
  -H "Content-Type: application/json" \
  -d '{
    "framework": "moscow",
    "today": "2026-01-10",
    "requests": [
      {
        "title": "SSO login",
        "scores": {
          "Priority Level": 10
        },
        "effort_days": 4,
        "deadline": "2026-01-12"
      }
    ]
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/dev-request-prioritizer
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `requests` | array | yes | Requests: { title, scores (object: dimension name → 1-10), effort_days (default 1), confidence (1-100, default 50), deadline (YYYY-MM-DD), status (default "new"), tags }. |
| `framework` | string (default \| rice \| ice \| wsjf \| moscow) | no | Scoring framework. Default "default". Default: `"default"`. |
| `dimensions` | array | no | Custom dimensions: { name, weight (1-10), is_inverse }. Default: the chosen framework's preset dimensions. |
| `use_confidence_in_scoring` | boolean | no | Multiply scores by confidence/100. Default false. Default: `false`. |
| `use_deadline_boost` | boolean | no | Boost scores of requests with a near deadline. Default true. Default: `true`. |
| `deadline_boost_days` | integer | no | Days before the deadline at which the boost starts. Default 7. Default: `7`. |
| `deadline_boost_multiplier` | number | no | Maximum boost percent. Default 50 (= +50%). Default: `50`. |
| `today` | string | no | Reference date for the deadline boost, YYYY-MM-DD. Default: today (UTC). |

Example arguments (verified):

```json
{
  "framework": "moscow",
  "today": "2026-01-10",
  "requests": [
    {
      "title": "SSO login",
      "scores": {
        "Priority Level": 10
      },
      "effort_days": 4,
      "deadline": "2026-01-12"
    }
  ]
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:dev_request_prioritizer`. Full MCP reference: https://findutils.com/mcp/dev-request-prioritizer/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt