rentahuman-mcp 2.1.0 → 2.3.0

package/README.md

@@ -160,7 +160,7 @@ These tools sign payments locally; the private key never leaves your machine, an
 - **get_escrow**: Inspect a specific escrow, including status, amounts, fees, parties, and audit history.
 - **list_escrows**: List escrows you created as the poster. Filter by `applicationId`, `bountyId`, optional `humanId`, or status.
 - **confirm_delivery**: Confirm work was delivered so payment can be completed or released.
-- **release_payment**: Release completed escrow funds to the worker after explicit user payment direction. This accepts the completed work; a separate evidence review is optional. Accepts optional `applicationId` binding check.
+- **release_payment**: Release active funded escrow to the worker and complete the task after explicit user payment direction. A prior worker completion or evidence review is not required. Accepts optional `applicationId` binding check.
 - **cancel_escrow**: Cancel an unfunded or funded escrow and refund the payer.
 - **open_dispute**: Freeze an eligible escrow for admin review.
 - **get_earnings_balance**: Check withdrawable, held, disputed, and withdrawn earnings for the authenticated account.
@@ -223,8 +223,8 @@ submission, and inspects every uploaded file before calling
 agent cannot inspect a file, it must report that limitation instead of deciding.
 Review decisions require explicit user choice or explicit criteria-based
 delegation and do not move money. Conversely, an explicit `release_payment` or
-`pay_enterprise_bounty` instruction accepts completed work without requiring a
-separate evidence approval. Platform admins cannot authorize payment.
+`pay_enterprise_bounty` instruction can pay before completion or evidence
+approval. Platform admins cannot authorize payment.
 
 ### Human-written text
 
@@ -277,6 +277,50 @@ Only workers whose profile country matches can apply or receive automatic
 outreach. The country gate still applies when remote work is allowed. Include a
 `city` for city-level targeting instead.
 
+#### Completion deadline (auto-reassign)
+
+The bounty-level `deadline` is the application cutoff. At or after that time,
+the listing leaves discovery and rejects new applications and direct uploads;
+it does not create a per-worker completion timer. Use `completionWindowHours`
+for accepted work:
+
+`create_bounty` and `update_bounty` accept `completionWindowHours` (number,
+1-720; `update_bounty` also accepts `null` to disable). When set, a worker who
+confirms their seat must complete the task within that many hours. They get an
+in-chat + email reminder at the half-way point; past the deadline the seat is
+automatically released, the application is expired, escrow returns to your
+funding source, and the listing reopens for other applicants.
+
+Workers may request more time. Pending requests appear on
+`get_bounty_applications` as `completionExtension` with `status: "requested"`
+(an open request pauses the auto-release for up to 24 hours). Answer with the
+`decide_extension_request` tool: `action: "approve"` grants the requested
+hours, `"deny"` resumes the original deadline, and `"grant"` with `hours`
+extends proactively — with or without an open request. For AI-managed bounties
+`completionWindowHours` overrides the default 6-hour managed work window;
+managed seats handle blockers through their own issue-report flow instead of
+extension requests.
+
+#### Automatic applicant review (autoAccept)
+
+`create_bounty` and `update_bounty` accept `autoAccept` (boolean, default
+true). When on, every new application is reviewed automatically: deterministic
+checks always run (account standing, country eligibility, payout viability,
+your blocklist), and an AI review runs only when the application contains
+free-text screening answers that need judgment. Qualified applicants are
+accepted (the standard worker-confirmation window still applies unless
+`skipAcceptanceConfirmation` is set), clear mismatches are rejected with a
+reason, and uncertain cases stay pending for your manual review via
+`get_bounty_applications` + `accept_application`. Pass `autoAccept: false` to
+review and accept every application yourself. Ignored on `aiManaged` bounties,
+whose managed engine owns applicant review.
+
+On `micCheckRequired` bounties the deterministic gate scores the applicant's
+mic recording: auto-accept requires an overall DNSMOS score of at least
+`autoAcceptMinMicScore` (1-5, default 3.0 — the platform's pass boundary).
+Set it at creation or change it later via `update_bounty` (`null` resets to
+the default). Below the floor, applications wait for your manual review.
+
 #### Microphone quality requirement
 
 `create_bounty` and `update_bounty` accept `micCheckRequired` (boolean, default

package/dist/serve.js

@@ -877,7 +877,11 @@ Well-specified bounties attract better applicants and avoid disputes. Always set
 5. **Price** \u2014 fixed USD by default. Anchor to real-world freelancer rates for
    the effort, location, urgency, and skill level. Underpriced bounties get
    low-quality applicants.
-6. **Deadline** \u2014 always set one; it must be in the future.
+6. **Application cutoff** (\`deadline\`) \u2014 always set one; it must be in the
+   future. At the cutoff the listing leaves discovery and stops accepting new
+   applications or direct uploads. If accepted workers also need a time limit,
+   set \`completionWindowHours\`; that clock starts when each worker confirms
+   their seat.
 
 **Application screening (\`applicationDetails\`)** \u2014 standard application
 bounties support pre-acceptance screening items: text questions, acknowledgment
@@ -1011,8 +1015,8 @@ when the user explicitly chooses approve/reject/redo or explicitly delegates
 criteria-based decisions. If a file cannot be inspected, disclose that limit
 instead of deciding. \`release_payment\` and \`pay_enterprise_bounty\` are
 separate irreversible financial actions and must only follow explicit user
-payment direction; that direction accepts completed work without a separate
-evidence-approval call.
+payment direction. Worker completion and evidence approval are not prerequisites
+for that explicit payment.
 
 ## Support
 
@@ -1598,7 +1602,7 @@ var CreateBountyRequest = Schema5.Struct({
     description: BOUNTY_LOCATION_DESCRIPTION
   }),
   deadline: Schema5.optional(Schema5.String).annotations({
-    description: "Deadline for task completion (ISO 8601 format)"
+    description: "Application cutoff (ISO 8601 format). At or after this time, the listing is removed from discovery and no new applications or direct uploads are accepted. Use completionWindowHours for a post-acceptance completion deadline."
   }),
   estimatedHours: Schema5.Number.pipe(
     Schema5.finite(),
@@ -1640,9 +1644,29 @@ var CreateBountyRequest = Schema5.Struct({
   autoExpireGhosts: Schema5.optional(Schema5.Boolean).annotations({
     description: "When true (and responseWindowHours is set), a ghosting worker\u2019s seat is automatically released at the deadline: their application is expired, the seat is freed, and the listing reopens for other applicants."
   }),
+  completionWindowHours: Schema5.optional(
+    Schema5.Number.pipe(
+      Schema5.int(),
+      Schema5.greaterThanOrEqualTo(1),
+      Schema5.lessThanOrEqualTo(720)
+    )
+  ).annotations({
+    description: "Auto-reassign completion deadline: hours a worker has to complete the task after confirming their seat (1-720). Workers are reminded at half the window; when the deadline passes the seat is automatically released and the listing reopens for other applicants. Workers may request an extension, which you approve, deny, or replace with your own via POST /bounties/{id}/applications/{appId}/extension/decision. For AI-managed bounties this overrides the default 6-hour work window. Omit for no completion deadline."
+  }),
   keepApplicantsOnFill: Schema5.optional(Schema5.Boolean).annotations({
     description: "When true, pending applicants are kept (not auto-rejected) once all seats fill, so you can reuse the applicant pool after reopening or adding seats. Default false."
   }),
+  autoAccept: Schema5.optional(Schema5.Boolean).annotations({
+    description: "Automatically review applicants as they apply. Deterministic checks (account standing, country eligibility, payout viability, your blocklist) always run; an AI review runs only when the application contains free-text screening answers that need judgment. Qualified applicants are accepted (the standard worker-confirmation window still applies unless skipAcceptanceConfirmation is set), clear mismatches are rejected with a reason, and uncertain cases stay pending for your manual review. Default true; pass false to review and accept every application yourself. Ignored for aiManaged bounties, whose managed engine owns applicant review."
+  }),
+  autoAcceptMinMicScore: Schema5.optional(
+    Schema5.Number.pipe(
+      Schema5.greaterThanOrEqualTo(1),
+      Schema5.lessThanOrEqualTo(5)
+    )
+  ).annotations({
+    description: "Minimum overall DNSMOS speech-quality score (1-5) an applicant\u2019s mic-check recording must reach for auto-accept on micCheckRequired bounties. Below the floor the application stays pending for your manual review (never auto-rejected). Default 3.0 \u2014 the platform\u2019s pass boundary. Only meaningful with micCheckRequired: true and autoAccept on."
+  }),
   identityRequired: Schema5.optional(Schema5.Boolean).annotations({
     description: "Require applicants to pass an identity check (government ID) before applying. Verified once per account and reused across bounties. Default false."
   }),
@@ -1816,7 +1840,7 @@ var UpdateBountyRequest = Schema5.Struct({
     description: "New estimated duration in hours (min 5 minutes = 0.083)"
   }),
   deadline: Schema5.optional(Schema5.String).annotations({
-    description: "New deadline (ISO 8601 format, or null to remove)"
+    description: "New application cutoff (ISO 8601 format). At or after this time, no new applications or direct uploads are accepted. This does not retime accepted workers; use completionWindowHours for future confirmed seats."
   }),
   requirements: Schema5.optional(Schema5.Array(Schema5.String)).annotations({
     description: "New requirements list"
@@ -1854,6 +1878,17 @@ var UpdateBountyRequest = Schema5.Struct({
   autoExpireGhosts: Schema5.optional(Schema5.Boolean).annotations({
     description: "When true (with responseWindowHours set), ghosting workers\u2019 seats are auto-released at the deadline and the listing reopens."
   }),
+  completionWindowHours: Schema5.optional(
+    Schema5.NullOr(
+      Schema5.Number.pipe(
+        Schema5.int(),
+        Schema5.greaterThanOrEqualTo(1),
+        Schema5.lessThanOrEqualTo(720)
+      )
+    )
+  ).annotations({
+    description: "Auto-reassign completion deadline in hours (1-720), or null to disable. Only affects seats confirmed after the edit \u2014 live per-worker deadlines are not re-timed."
+  }),
   spotsAvailable: Schema5.optional(
     Schema5.Number.pipe(
       Schema5.int(),
@@ -1861,11 +1896,27 @@ var UpdateBountyRequest = Schema5.Struct({
       Schema5.lessThanOrEqualTo(500)
     )
   ).annotations({
-    description: "Increase the number of seats (humans needed). Cannot be set below spots already filled. Raising it on a funded bounty may require an additional escrow authorization."
+    description: "Change the number of seats (humans needed). Cannot be set below spots already filled. On a wallet-funded bounty the pool is resized in place: extra seats are debited from the poster wallet, freed seats are refunded to it."
+  }),
+  walletImpactAcknowledged: Schema5.optional(Schema5.Boolean).annotations({
+    description: "Acknowledges the wallet impact of a wallet-funded bounty edit. Any edit that debits the poster wallet (adding seats via spotsAvailable, or raising the price) is first refused with error_code wallet_impact_confirmation_required and the exact amount; retry the same request with this set to true to apply the charge. Admins editing a bounty they do not own must also pass it for any edit that debits or credits the poster wallet."
   }),
   keepApplicantsOnFill: Schema5.optional(Schema5.Boolean).annotations({
     description: "When true, pending applicants are kept (not auto-rejected) once all seats fill, so you can draw from the same pool after reopening or adding seats. Default false."
   }),
+  autoAccept: Schema5.optional(Schema5.Boolean).annotations({
+    description: "Turn automatic applicant review on or off. When on, deterministic checks always run and an AI review runs only for free-text screening answers; qualified applicants are accepted, clear mismatches rejected, uncertain cases left pending. Applications received while off stay pending; toggling on affects future applications only. Ignored on aiManaged bounties."
+  }),
+  autoAcceptMinMicScore: Schema5.optional(
+    Schema5.NullOr(
+      Schema5.Number.pipe(
+        Schema5.greaterThanOrEqualTo(1),
+        Schema5.lessThanOrEqualTo(5)
+      )
+    )
+  ).annotations({
+    description: "Change the minimum overall DNSMOS mic score (1-5) for auto-accept on micCheckRequired bounties, or pass null to reset to the platform default (3.0). Affects future applications only."
+  }),
   completionCriteria: Schema5.optional(
     Schema5.String.pipe(Schema5.minLength(10), Schema5.maxLength(2e3))
   ).annotations({
@@ -2072,6 +2123,24 @@ var ExpireApplicationRequest = Schema5.Struct({
     description: "Optional human-readable reason shown to the released worker (e.g. why the seat was reclaimed). Defaults to a generic no-activity explanation."
   })
 });
+var DecideExtensionRequest = Schema5.Struct({
+  bountyId: Schema5.String.annotations({ description: "The bounty ID" }),
+  applicationId: Schema5.String.annotations({
+    description: "The accepted application whose completion deadline to decide"
+  }),
+  action: Schema5.Literal("approve", "deny", "grant").annotations({
+    description: "'approve' grants the worker's open extension request, 'deny' declines it (the original deadline resumes), 'grant' extends by `hours` whether or not a request is open."
+  }),
+  hours: Schema5.optional(
+    Schema5.Number.pipe(
+      Schema5.int(),
+      Schema5.greaterThanOrEqualTo(1),
+      Schema5.lessThanOrEqualTo(720)
+    )
+  ).annotations({
+    description: "Extension length in hours. Required for 'grant'; for 'approve' it is only the fallback when the request did not name an hour count."
+  })
+});
 var GetBountyRequest = Schema5.Struct({
   bountyId: Schema5.String.annotations({
     description: "The unique ID of the bounty"
@@ -2096,7 +2165,6 @@ import { Schema as Schema7 } from "effect";
 
 // ../contracts/src/validation/qa-assignment-contract.ts
 import { Either, Schema as Schema6 } from "effect";
-var QA_ASSIGNMENT_CONTRACT_VERSION = 1;
 var QaAssignmentEligibilitySchema = Schema6.Struct({
   id: Schema6.String,
   label: Schema6.String,
@@ -2115,7 +2183,7 @@ var QaAssignmentCriterionSchema = Schema6.Struct({
   origin: Schema6.optional(Schema6.Literal("owner"))
 });
 var QaAssignmentContractSchema = Schema6.Struct({
-  version: Schema6.Literal(QA_ASSIGNMENT_CONTRACT_VERSION),
+  version: Schema6.Literal(1, 2),
   eligibility: Schema6.Array(QaAssignmentEligibilitySchema),
   task: Schema6.Struct({
     targetUrl: Schema6.String,
@@ -2124,7 +2192,9 @@ var QaAssignmentContractSchema = Schema6.Struct({
   }),
   submission: Schema6.Struct({
     evidenceMode: Schema6.Literal("photo", "video", "document"),
-    criteria: Schema6.Array(QaAssignmentCriterionSchema)
+    criteria: Schema6.Array(QaAssignmentCriterionSchema),
+    /** When 'required', every origin:'owner' criterion must be bound to video evidence at submission time. */
+    checklistEvidence: Schema6.optional(Schema6.Literal("required"))
   })
 });
 
@@ -2223,6 +2293,9 @@ var BountyPublicResponse = Schema7.Struct({
   fundingMethod: Schema7.optional(Schema7.String),
   identityRequired: Schema7.optional(Schema7.Boolean),
   micCheckRequired: Schema7.optional(Schema7.Boolean),
+  completionWindowHours: Schema7.optional(Schema7.Number),
+  autoAccept: Schema7.optional(Schema7.Boolean),
+  autoAcceptMinMicScore: Schema7.optional(Schema7.Number),
   requiredQualificationIds: Schema7.optional(Schema7.Array(Schema7.String)),
   supportedCountries: Schema7.optional(Schema7.Array(Schema7.String)),
   intakeClosedCountries: Schema7.optional(Schema7.Array(Schema7.String)),
@@ -2310,9 +2383,14 @@ var expireApplicationSpec = {
   description: "Release a previously accepted seat when the worker has ghosted (no message or submission after being accepted). Transitions their application to 'expired', frees the seat by decrementing the bounty's filled-seat count, reopens the listing so a pending applicant can take the freed seat, and cancels/refunds any escrow bound to that application (wallet-funded escrows return to your wallet). The released worker is notified. Owner only; only works on 'accepted' applications.",
   input: ExpireApplicationRequest
 };
+var decideExtensionSpec = {
+  name: "decide_extension_request",
+  description: "Answer a worker's completion-deadline extension request on one of your bounties, or proactively extend a worker's deadline. Only meaningful when the bounty sets completionWindowHours. 'approve' grants the worker's requested hours, 'deny' declines (the original deadline resumes and the overdue seat will auto-release), 'grant' extends by `hours` with or without an open request. Pending requests appear on applications from get_bounty_applications as completionExtension with status 'requested'; an open request pauses the auto-release for up to 24 hours. Owner only.",
+  input: DecideExtensionRequest
+};
 var updateBountySpec = {
   name: "update_bounty",
-  description: "Update ordinary one-shot bounty details. You can modify the title, description, price, deadline, location, requiredLinks, applicationDetails, lifecycleMessages, liveCaptureRequirement, reactivate hidden inactive bounties, and more. To target an entire country, pass location with an ISO country code and isRemoteAllowed=false while omitting city and state. Live capture and required-link requirements can only be changed before applications are received. applicationDetails may be changed after applications are received; existing applications keep their original answers, while future applications use the latest fields. applicationDetails are application detail items for standard application bounties only; blank rows are ignored, uploads are capped at 3 fields, acknowledgments at 5 fields, and camera-only live_video at 1 required field. lifecycleMessages can define auto-message templates for acceptance, rejection, and submission review transitions. Admin-only ongoing bounty settings are intentionally not exposed through MCP. You can also pause/unpause a bounty (status 'paused'/'open'), close an unassigned bounty and return its unused funding (status 'closed'), increase seats via spotsAvailable, and keep pending applicants on fill via keepApplicantsOnFill. Use cancel_bounty for cancellation and refund handling. Work completion and payment are system-managed from escrow and payout evidence; status 'completed' and 'paid' cannot be set directly.",
+  description: "Update ordinary one-shot bounty details. You can modify the title, description, price, application-cutoff deadline, location, requiredLinks, applicationDetails, lifecycleMessages, liveCaptureRequirement, reactivate hidden inactive bounties, and more. The deadline stops new applications and direct uploads; completionWindowHours controls post-acceptance completion timing. To target an entire country, pass location with an ISO country code and isRemoteAllowed=false while omitting city and state. Live capture and required-link requirements can only be changed before applications are received. applicationDetails may be changed after applications are received; existing applications keep their original answers, while future applications use the latest fields. applicationDetails are application detail items for standard application bounties only; blank rows are ignored, uploads are capped at 3 fields, acknowledgments at 5 fields, and camera-only live_video at 1 required field. lifecycleMessages can define auto-message templates for acceptance, rejection, and submission review transitions. Admin-only ongoing bounty settings are intentionally not exposed through MCP. You can also pause/unpause a bounty (status 'paused'/'open'), close an unassigned bounty and return its unused funding (status 'closed'), increase seats via spotsAvailable, keep pending applicants on fill via keepApplicantsOnFill, and change the auto-reassign completion deadline via completionWindowHours (null disables; only affects seats confirmed after the edit), and toggle automatic applicant review via autoAccept (applications received while off stay pending; toggling on affects future applications only; ignored on aiManaged bounties) or adjust its mic-quality floor via autoAcceptMinMicScore (1-5, null resets to the 3.0 default). Use cancel_bounty for cancellation and refund handling. Work completion and payment are system-managed from escrow and payout evidence; status 'completed' and 'paid' cannot be set directly.",
   input: UpdateBountyRequest
 };
 var cancelBountySpec = {
@@ -2332,7 +2410,7 @@ var boostBountyOutreachSpec = {
 };
 var payEnterpriseBountySpec = {
   name: "pay_enterprise_bounty",
-  description: "Pay a completed legacy enterprise bounty (older bounties created under the retired enterprise deferred-billing tier) from the owner wallet. New bounties are always escrow-funded; use release_payment for them. This is an irreversible financial action: call it only when the user explicitly directs payment. Explicit payment accepts the completed work and does not require a separate evidence-approval decision. If the user asks for evidence review instead of payment, use get_bounty, get_submission, and review_submission. The amount, worker, and wallet are loaded from stored records. Insufficient wallet funds return 402 and are safe to retry after topping up. Owner or bounty-owning agent only; platform admins cannot pay.",
+  description: "Pay an accepted worker on a legacy enterprise bounty (older bounties created under the retired enterprise deferred-billing tier) from the owner wallet. New bounties are always escrow-funded; use release_payment for them. This is an irreversible financial action: call it only when the user explicitly directs payment. Worker completion and evidence review are not prerequisites for explicit owner payment. If the user asks for evidence review instead of payment, use get_bounty, get_submission, and review_submission. The amount, worker, and wallet are loaded from stored records. Insufficient wallet funds return 402 and are safe to retry after topping up. Owner or bounty-owning agent only; platform admins cannot pay.",
   input: PayEnterpriseBountyRequest,
   annotations: {
     title: "Pay enterprise bounty",
@@ -3150,6 +3228,12 @@ function toMcpTool(spec, run) {
 }
 
 // src/tools/handlers/bounties.ts
+var MOCK_HIRING_STATUSES = /* @__PURE__ */ new Set([
+  "open",
+  "pending_funding",
+  "partially_filled"
+]);
+var mockHiringSpotsRemaining = (bounty) => MOCK_HIRING_STATUSES.has(bounty.status) ? Math.max(0, (bounty.spotsAvailable || 1) - (bounty.spotsFilled || 0)) : 0;
 var handleCreateBounty = (args) => Effect9.gen(function* () {
   const params = yield* decode(CreateBountyRequest)(args);
   const identity2 = yield* Identity;
@@ -3184,10 +3268,15 @@ var handleCreateBounty = (args) => Effect9.gen(function* () {
       currency,
       spotsAvailable,
       ...params.aiManaged !== void 0 ? { aiManaged: params.aiManaged } : {},
+      // Default-on unless explicitly disabled; aiManaged bounties never
+      // store the flag (the managed engine owns applicant review).
+      ...params.aiManaged ? {} : { autoAccept: params.autoAccept !== false },
+      ...params.autoAcceptMinMicScore !== void 0 && !params.aiManaged ? { autoAcceptMinMicScore: params.autoAcceptMinMicScore } : {},
       requirements: params.requirements || [],
       skillsNeeded: params.skillsNeeded || [],
       identityRequired: params.identityRequired || false,
       keepApplicantsOnFill: params.keepApplicantsOnFill || false,
+      completionWindowHours: params.completionWindowHours ?? null,
       requiredLinks: params.requiredLinks || [],
       applicationDetails: screeningFields,
       submissionMode: params.submissionMode || "application",
@@ -3234,6 +3323,8 @@ var handleCreateBounty = (args) => Effect9.gen(function* () {
       price: params.price,
       currency: params.currency || "USD",
       ...params.aiManaged !== void 0 ? { aiManaged: params.aiManaged } : {},
+      ...params.aiManaged ? {} : { autoAccept: params.autoAccept !== false },
+      ...params.autoAcceptMinMicScore !== void 0 && !params.aiManaged ? { autoAcceptMinMicScore: params.autoAcceptMinMicScore } : {},
       status: "open",
       applicationCount: 0,
       viewCount: 0,
@@ -3241,6 +3332,7 @@ var handleCreateBounty = (args) => Effect9.gen(function* () {
       micCheckRequired: params.micCheckRequired || false,
       liveCaptureRequirement: params.liveCaptureRequirement,
       keepApplicantsOnFill: params.keepApplicantsOnFill || false,
+      ...params.completionWindowHours !== void 0 ? { completionWindowHours: params.completionWindowHours } : {},
       requiredLinks: params.requiredLinks || [],
       applicationDetails: screeningFields,
       submissionMode: params.submissionMode || "application",
@@ -3329,7 +3421,7 @@ var handleListBounties = (args) => Effect9.gen(function* () {
     }
     const bountiesWithComputed = bounties2.map((b) => ({
       ...b,
-      spotsRemaining: (b.spotsAvailable || 1) - (b.spotsFilled || 0)
+      spotsRemaining: mockHiringSpotsRemaining(b)
     }));
     return ok({
       success: true,
@@ -3370,7 +3462,7 @@ var getBountyTool = toMcpTool(
         success: true,
         bounty: {
           ...bounty,
-          spotsRemaining: (bounty.spotsAvailable || 1) - (bounty.spotsFilled || 0)
+          spotsRemaining: mockHiringSpotsRemaining(bounty)
         },
         mode: "mock"
       });
@@ -3656,6 +3748,36 @@ var expireApplicationTool = toMcpTool(
     return ok(result);
   })
 );
+var decideExtensionTool = toMcpTool(
+  decideExtensionSpec,
+  (params) => Effect9.gen(function* () {
+    const identity2 = yield* Identity;
+    const api = yield* ApiClient;
+    const rateLimit = yield* RateLimit;
+    const config = yield* McpConfig;
+    yield* rateLimit.check("decide_extension_request");
+    if (config.mockMode) {
+      return ok({
+        success: true,
+        action: params.action,
+        message: params.action === "deny" ? "Extension declined (mock)." : "Deadline extended (mock).",
+        mode: "mock"
+      });
+    }
+    const verification = yield* identity2.createVerification(
+      `extension_decision:${params.bountyId}:${params.applicationId}`
+    );
+    const result = yield* api.post(
+      `/bounties/${params.bountyId}/applications/${params.applicationId}/extension/decision`,
+      {
+        action: params.action,
+        ...params.hours !== void 0 ? { hours: params.hours } : {},
+        ...verification
+      }
+    );
+    return ok(result);
+  })
+);
 var getBountyOutreachStatusTool = toMcpTool(
   getBountyOutreachStatusSpec,
   (params) => Effect9.gen(function* () {
@@ -3709,7 +3831,7 @@ var payEnterpriseBountyTool = toMcpTool(
 var bountyTools = [
   {
     name: "create_bounty",
-    description: "Create a one-shot task bounty for humans to apply to. To target an entire country, pass location with an ISO country code and isRemoteAllowed=false while omitting city and state. **IMPORTANT: Always call with dryRun=true first** to preview the bounty. Dry-run `preview.fundingTotal` is the total funding requirement before any existing wallet balance is applied. Show that estimate to the operator before posting. Show the preview to the user and ask 'Here's your bounty \u2014 would you like to edit anything before posting?' Only call again with dryRun=false (or omitted) after the user confirms. **You MUST help the user define completionCriteria and evidenceTypes** \u2014 ask what 'done' looks like and what proof they need (text/data, photos, video, or links). For specialized standard-application tasks, configure applicationDetails so applicants provide application details before review. Blank rows are ignored; application upload fields are one file each and capped at 3 total; acknowledgment checkboxes are capped at 5 total and can be optional or required; and one required live_video field may contain a script applicants must record with the in-browser camera. For appearance-based bounties where the worker appears on camera or their presence is part of the deliverable (sign holding, UGC, sponsored posts, on-camera video, promo/GTM appearances), always include one required live_video field with a label asking the applicant to explain in two sentences why they are a good fit \u2014 this gates applications on a live self-recorded video so the poster sees each applicant before accepting. Do not ask for passwords, OTP/2FA codes, API keys, private keys, seed phrases, government IDs, bank/card details, exact home addresses, dates of birth, or other sensitive personal information. For direct-review collection bounties, use submissionMode='photo_upload', 'video_upload', or 'document_upload' with matching submission settings instead of applicationDetails. lifecycleMessages can define auto-message templates for acceptance, rejection, and submission review transitions. You can require applicants to provide specific links (LinkedIn, GitHub, resume, etc.) using the requiredLinks parameter. Requires RENTAHUMAN_API_KEY from the account owner. Standard accounts use available wallet balance first; if the wallet cannot cover the bounty, the response includes deposit_url and checkout_total (the hosted charge after wallet balance is applied) and the account owner must complete checkout before the bounty is visible. Supports multi-person bounties by setting spotsAvailable > 1. Ongoing data-collection programs are managed separately and cannot be created through this tool. Pass optional `idempotencyKey` to make this safe to retry (a replayed key returns the original result instead of duplicating). BETA: pass aiManaged: true to have the platform fully manage the bounty \u2014 automated recruiting, vetting, submission review, payment release, and a final report. Fixed price USD only, 1-50 spots. Poll the bounty's managed run or subscribe to run.report_ready for the finished work.",
+    description: "Create a one-shot task bounty for humans to apply to. To target an entire country, pass location with an ISO country code and isRemoteAllowed=false while omitting city and state. **IMPORTANT: Always call with dryRun=true first** to preview the bounty. Dry-run `preview.fundingTotal` is the total funding requirement before any existing wallet balance is applied. Show that estimate to the operator before posting. Show the preview to the user and ask 'Here's your bounty \u2014 would you like to edit anything before posting?' Only call again with dryRun=false (or omitted) after the user confirms. **You MUST help the user define completionCriteria and evidenceTypes** \u2014 ask what 'done' looks like and what proof they need (text/data, photos, video, or links). For specialized standard-application tasks, configure applicationDetails so applicants provide application details before review. Blank rows are ignored; application upload fields are one file each and capped at 3 total; acknowledgment checkboxes are capped at 5 total and can be optional or required; and one required live_video field may contain a script applicants must record with the in-browser camera. For appearance-based bounties where the worker appears on camera or their presence is part of the deliverable (sign holding, UGC, sponsored posts, on-camera video, promo/GTM appearances), always include one required live_video field with a label asking the applicant to explain in two sentences why they are a good fit \u2014 this gates applications on a live self-recorded video so the poster sees each applicant before accepting. Do not ask for passwords, OTP/2FA codes, API keys, private keys, seed phrases, government IDs, bank/card details, exact home addresses, dates of birth, or other sensitive personal information. For direct-review collection bounties, use submissionMode='photo_upload', 'video_upload', or 'document_upload' with matching submission settings instead of applicationDetails. lifecycleMessages can define auto-message templates for acceptance, rejection, and submission review transitions. You can require applicants to provide specific links (LinkedIn, GitHub, resume, etc.) using the requiredLinks parameter. Requires RENTAHUMAN_API_KEY from the account owner. Standard accounts use available wallet balance first; if the wallet cannot cover the bounty, the response includes deposit_url and checkout_total (the hosted charge after wallet balance is applied) and the account owner must complete checkout before the bounty is visible. Supports multi-person bounties by setting spotsAvailable > 1. Set completionWindowHours (1-720) to give confirmed workers a completion deadline: overdue seats auto-release and reopen for other applicants; workers may request extensions you answer with decide_extension_request. Ongoing data-collection programs are managed separately and cannot be created through this tool. Pass optional `idempotencyKey` to make this safe to retry (a replayed key returns the original result instead of duplicating). Applicants are auto-reviewed by default (autoAccept, default true): deterministic checks always run and an AI review runs only for free-text screening answers \u2014 qualified applicants are accepted, clear mismatches rejected with a reason, uncertain cases left pending for manual review; pass autoAccept: false to review and accept every application yourself; on micCheckRequired bounties, tune the mic-quality floor with autoAcceptMinMicScore (1-5, default 3.0). BETA: pass aiManaged: true to have the platform fully manage the bounty \u2014 automated recruiting, vetting, submission review, payment release, and a final report. Fixed price USD only, 1-50 spots. Poll the bounty's managed run or subscribe to run.report_ready for the finished work.",
     inputSchema: toInputSchema(CreateBountyRequest),
     handler: handleCreateBounty
   },
@@ -3727,6 +3849,7 @@ var bountyTools = [
   acceptApplicationTool,
   rejectApplicationTool,
   expireApplicationTool,
+  decideExtensionTool,
   getBountyOutreachStatusTool,
   boostBountyOutreachTool,
   payEnterpriseBountyTool
@@ -4528,7 +4651,7 @@ var escrowTools = [
   },
   {
     name: "confirm_delivery",
-    description: "Confirm that a worker has satisfactorily completed the task. Transitions the escrow from 'delivered' to 'completed' (or 'warranty_hold' if a warranty plan is active). After confirming, use release_payment to send funds to the worker. Requires RENTAHUMAN_API_KEY to be set.",
+    description: "Confirm that a worker has satisfactorily completed the task. Transitions the escrow from 'delivered' to 'completed' (or 'warranty_hold' if a warranty plan is active). This is separate from release_payment, which the owner may explicitly direct earlier. Requires RENTAHUMAN_API_KEY to be set.",
     inputSchema: toInputSchema(ConfirmDeliveryRequest),
     handler: (args) => Effect12.gen(function* () {
       yield* requireApiKey;
@@ -4544,7 +4667,7 @@ var escrowTools = [
   },
   {
     name: "release_payment",
-    description: "Release escrowed funds to the worker. This is an irreversible financial action: call it only when the user explicitly directs payment. The task must be completed first, but explicit payment accepts the completed work and does not require a separate review_submission approval. If the user asks to review evidence instead, call get_bounty and get_submission, inspect every file, then use review_submission. Optionally pass `applicationId` to assert the intended application; a mismatch is refused to prevent paying the wrong worker. Requires RENTAHUMAN_API_KEY.",
+    description: "Release an active funded escrow to the worker and complete the task. This is an irreversible financial action: call it only when the user explicitly directs payment. A prior worker completion or review_submission approval is not required. If the user asks to review evidence instead, call get_bounty and get_submission, inspect every file, then use review_submission. Optionally pass `applicationId` to assert the intended application; a mismatch is refused to prevent paying the wrong worker. Requires RENTAHUMAN_API_KEY.",
     inputSchema: toInputSchema(ReleasePaymentRequest),
     annotations: {
       title: "Release payment",

package/dist/types/index.d.ts

@@ -70,7 +70,10 @@ declare const CreateBountyRequest: Schema.Struct<{
     spotsAvailable: Schema.optional<Schema.filter<Schema.filter<typeof Schema.Number>>>;
     responseWindowHours: Schema.optional<Schema.filter<Schema.filter<typeof Schema.Number>>>;
     autoExpireGhosts: Schema.optional<typeof Schema.Boolean>;
+    completionWindowHours: Schema.optional<Schema.filter<Schema.filter<Schema.filter<typeof Schema.Number>>>>;
     keepApplicantsOnFill: Schema.optional<typeof Schema.Boolean>;
+    autoAccept: Schema.optional<typeof Schema.Boolean>;
+    autoAcceptMinMicScore: Schema.optional<Schema.filter<Schema.filter<typeof Schema.Number>>>;
     identityRequired: Schema.optional<typeof Schema.Boolean>;
     micCheckRequired: Schema.optional<typeof Schema.Boolean>;
     aiManaged: Schema.optional<Schema.Literal<[true]>>;
@@ -145,8 +148,12 @@ declare const UpdateBountyRequest: Schema.Struct<{
     micCheckRequired: Schema.optional<typeof Schema.Boolean>;
     responseWindowHours: Schema.optional<Schema.filter<Schema.filter<typeof Schema.Number>>>;
     autoExpireGhosts: Schema.optional<typeof Schema.Boolean>;
+    completionWindowHours: Schema.optional<Schema.NullOr<Schema.filter<Schema.filter<Schema.filter<typeof Schema.Number>>>>>;
     spotsAvailable: Schema.optional<Schema.filter<Schema.filter<Schema.filter<typeof Schema.Number>>>>;
+    walletImpactAcknowledged: Schema.optional<typeof Schema.Boolean>;
     keepApplicantsOnFill: Schema.optional<typeof Schema.Boolean>;
+    autoAccept: Schema.optional<typeof Schema.Boolean>;
+    autoAcceptMinMicScore: Schema.optional<Schema.NullOr<Schema.filter<Schema.filter<typeof Schema.Number>>>>;
     completionCriteria: Schema.optional<Schema.filter<Schema.filter<typeof Schema.String>>>;
     evidenceTypes: Schema.optional<Schema.filter<Schema.Array$<Schema.Literal<["text", "photo", "video", "link"]>>>>;
     evidenceCriteria: Schema.optional<Schema.filter<typeof Schema.String>>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rentahuman-mcp",
-  "version": "2.1.0",
+  "version": "2.3.0",
   "description": "MCP server for AI agents to browse and book humans on rentahuman.ai",
   "keywords": [
     "ai",