rentahuman-mcp 3.2.1 → 3.3.0

package/README.md

@@ -211,9 +211,11 @@ worker (`escrow_recipient_mismatch`).
 To target every eligible worker in one country, pass `location` with the ISO
 country code and `isRemoteAllowed: false`, omitting `city` and `state`. The
 same shape works with `update_bounty`. Platform-blocked countries are rejected.
+To open one bounty to several countries, pass `supportedCountries` instead.
 
 ```text
 location: { country: "US", isRemoteAllowed: false }
+supportedCountries: ["US", "CA", "GB", "NZ", "AU"]
 ```
 
 For ordinary accepted one-shot bounties, the worker marks the task complete by
@@ -307,6 +309,32 @@ 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.
 
+To recruit across several countries, pass `supportedCountries` with the ISO
+codes (country names are recognized too). Omit `location.country`, or keep it
+and make sure it appears in the list:
+
+```json
+{
+  "location": { "isRemoteAllowed": true },
+  "supportedCountries": ["US", "CA", "GB", "NZ", "AU"],
+  "identityRequired": true
+}
+```
+
+The list is normalized to uppercase ISO codes and deduplicated; blocked or
+unrecognized countries are rejected with a `400`. With `identityRequired`, the
+list is enforced against the applicant's verified document country. Use
+`isRemoteAllowed: true`: an on-site bounty (`isRemoteAllowed: false`) with a
+location country is gated by that country alone and accepts no other list. On
+`update_bounty`, send the full new list to change it. Omitting it leaves an
+explicit multi-country list in place, so editing `location` alone never drops
+it; legacy bounties that only mirror a country-only `location` keep deriving
+that single country from `location`. An empty array is stored as an explicit
+empty list; it never lifts a country-only or on-site country restriction
+(remove `location.country` first), and a remote city location with a country
+stays unrestricted as before. `aiManaged` bounties do not accept
+`supportedCountries`.
+
 #### Completion deadline (auto-reassign)
 
 The bounty-level `deadline` is the application cutoff. At or after that time,

package/dist/serve.js

@@ -1326,6 +1326,7 @@ var agentCheckoutTools = [
 var BOUNTY_PRICE_TYPES = ["fixed", "hourly"];
 var BOUNTY_MIN_PRICE_USD = 3;
 var MAX_EXCLUDED_PARTICIPANT_SOURCE_BOUNTIES = 1e3;
+var MAX_BOUNTY_SUPPORTED_COUNTRIES = 250;
 var HUMANIZATION_FORMATS = ["text"];
 var HUMANIZATION_TRANSFORMATIONS = [
   "paraphrase",
@@ -1480,6 +1481,11 @@ var BountyLocationRequest = Schema5.Struct({
   isRemoteAllowed: Schema5.optional(Schema5.Boolean)
 });
 var BOUNTY_LOCATION_DESCRIPTION = "Worker location target. Set country to an ISO country code without city or state to target every eligible worker in that country, including when remote work is allowed. Include city (and optionally state/country) for city-level targeting. Platform-blocked countries are rejected.";
+var BountySupportedCountriesRequest = Schema5.Array(
+  Schema5.String.pipe(Schema5.minLength(1), Schema5.maxLength(100))
+).pipe(Schema5.maxItems(MAX_BOUNTY_SUPPORTED_COUNTRIES));
+var BOUNTY_SUPPORTED_COUNTRIES_CREATE_DESCRIPTION = 'Countries whose workers may see and apply, as ISO country codes (country names are also recognized), e.g. ["US", "CA", "GB", "NZ", "AU"]. Omit it to keep the location-derived policy: a country-only location restricts the bounty to that country, an on-site city location keeps its existing country gate, and other locations stay unrestricted. When location.country is set it must appear in this list, and on-site bounties (isRemoteAllowed false) with a location country accept only that one country; use isRemoteAllowed true for a remote multi-country bounty. Platform-blocked countries and unrecognized values are rejected. With identityRequired, the list is enforced against the verified document country. Not accepted on aiManaged bounties.';
+var BOUNTY_SUPPORTED_COUNTRIES_UPDATE_DESCRIPTION = 'Replace the eligible-country list with the full new list of ISO country codes (country names are also recognized), e.g. ["US", "CA", "GB", "NZ", "AU"]. Omitting it leaves an explicit multi-country list in place, so a location-only edit never drops it; legacy bounties that only mirror a country-only location keep deriving that single country from location. On-site bounties (isRemoteAllowed false) with a location country accept only that one country. An empty array is stored as an explicit empty list; it never lifts a country-only or on-site country restriction (remove location.country first), while a remote city location with a country stays unrestricted as before. When location.country is set it must appear in the list. Platform-blocked countries and unrecognized values are rejected.';
 var LIFECYCLE_MESSAGES_DESCRIPTION = "Auto-sent to the doer in the bounty conversation on lifecycle transitions. Supports {{name}}, {{bountyTitle}}, {{deadline}}, {{reason}} interpolation. Accepted/submission templates are only ever delivered to accepted applicants.";
 var LifecycleMessageTemplateSchema = Schema5.String.pipe(
   Schema5.maxLength(BOUNTY_LIFECYCLE_TEMPLATE_MAX_LENGTH)
@@ -1627,6 +1633,11 @@ var CreateBountyRequest = Schema5.Struct({
   location: Schema5.optional(BountyLocationRequest).annotations({
     description: BOUNTY_LOCATION_DESCRIPTION
   }),
+  supportedCountries: Schema5.optional(
+    BountySupportedCountriesRequest
+  ).annotations({
+    description: BOUNTY_SUPPORTED_COUNTRIES_CREATE_DESCRIPTION
+  }),
   deadline: Schema5.optional(Schema5.String).annotations({
     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."
   }),
@@ -1892,6 +1903,11 @@ var UpdateBountyRequest = Schema5.Struct({
   location: Schema5.optional(BountyLocationRequest).annotations({
     description: BOUNTY_LOCATION_DESCRIPTION
   }),
+  supportedCountries: Schema5.optional(
+    BountySupportedCountriesRequest
+  ).annotations({
+    description: BOUNTY_SUPPORTED_COUNTRIES_UPDATE_DESCRIPTION
+  }),
   status: Schema5.optional(
     Schema5.Literal("open", "in_review", "paused", "closed")
   ).annotations({
@@ -2383,7 +2399,7 @@ var CancelBountyRequest = BountyCancellationFeedbackRequest.pipe(
 );
 var createBountySpec = {
   name: "create_bounty",
-  description: `Create a one-shot task bounty for humans to apply to. Dry-run preview.fundingTotal is the total funding requirement before any existing wallet balance is applied; show that estimate to the operator before posting. Live pending_deposit responses include checkout_total, the exact hosted charge after wallet balance is applied, next to deposit_url. To target an entire country, pass location with an ISO country code and isRemoteAllowed=false while omitting city and state. Standard application bounties support application detail items via applicationDetails, including text questions, optional or required acknowledgment checkboxes, one-file uploads (allowedFileTypes: image, docx, pdf, txt, video, audio), and one required live_video field whose label is the script applicants 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. Set liveCaptureRequirement to photo or video when accepted workers must capture new camera evidence after acceptance; neither camera-only workflow is cryptographic liveness verification. 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. Blank rows are ignored; uploads are capped at 3 fields, acknowledgments at 5 fields, and live video at 1 field. Direct-review photo, video, or document collection bounties use submissionMode and matching upload settings instead of applicationDetails. lifecycleMessages can define auto-message templates for acceptance, rejection, and submission review transitions. Set completionWindowHours (any whole number of hours from 1 to 720, e.g. 36) to give confirmed workers a completion deadline: overdue seats are automatically released and reopened for other applicants (auto-reassign), workers can request extensions, and you approve/deny/grant them per worker. 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, set autoAcceptMinMicScore (1-5) to make the mic score a hard cutoff: applications below it are auto-rejected, at/above proceed toward acceptance, and unscored recordings stay pending. When omitted, the platform default 3.0 applies and lower scores only stay pending for manual review. To keep previous participants out, pass excludedParticipantSourceBountyIds with up to ${MAX_EXCLUDED_PARTICIPANT_SOURCE_BOUNTIES} ids of your OWN earlier bounties: any worker who was ever accepted on one of them cannot see or apply to the new bounty, and you can change the list later with update_bounty. AI-managed, QA, and taste run bounties, and never-funded drafts are rejected as sources. 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. Dry-run preview.fundingTotal is the total funding requirement before any existing wallet balance is applied; show that estimate to the operator before posting. Live pending_deposit responses include checkout_total, the exact hosted charge after wallet balance is applied, next to deposit_url. To target an entire country, pass location with an ISO country code and isRemoteAllowed=false while omitting city and state. To open one bounty to several countries, pass supportedCountries with the ISO codes (e.g. ["US", "CA", "GB", "NZ", "AU"]); when location.country is set it must be in that list, on-site bounties (isRemoteAllowed=false) accept only their location country, and with identityRequired the list is enforced against the verified document country. Standard application bounties support application detail items via applicationDetails, including text questions, optional or required acknowledgment checkboxes, one-file uploads (allowedFileTypes: image, docx, pdf, txt, video, audio), and one required live_video field whose label is the script applicants 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. Set liveCaptureRequirement to photo or video when accepted workers must capture new camera evidence after acceptance; neither camera-only workflow is cryptographic liveness verification. 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. Blank rows are ignored; uploads are capped at 3 fields, acknowledgments at 5 fields, and live video at 1 field. Direct-review photo, video, or document collection bounties use submissionMode and matching upload settings instead of applicationDetails. lifecycleMessages can define auto-message templates for acceptance, rejection, and submission review transitions. Set completionWindowHours (any whole number of hours from 1 to 720, e.g. 36) to give confirmed workers a completion deadline: overdue seats are automatically released and reopened for other applicants (auto-reassign), workers can request extensions, and you approve/deny/grant them per worker. 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, set autoAcceptMinMicScore (1-5) to make the mic score a hard cutoff: applications below it are auto-rejected, at/above proceed toward acceptance, and unscored recordings stay pending. When omitted, the platform default 3.0 applies and lower scores only stay pending for manual review. To keep previous participants out, pass excludedParticipantSourceBountyIds with up to ${MAX_EXCLUDED_PARTICIPANT_SOURCE_BOUNTIES} ids of your OWN earlier bounties: any worker who was ever accepted on one of them cannot see or apply to the new bounty, and you can change the list later with update_bounty. AI-managed, QA, and taste run bounties, and never-funded drafts are rejected as sources. 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.`,
   input: CreateBountyRequest
 };
 var getBountySpec = {
@@ -2424,7 +2440,7 @@ var decideExtensionSpec = {
 };
 var updateBountySpec = {
   name: "update_bounty",
-  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' stops new applications and outreach, including on a fully staffed bounty; status 'open' resumes it, and the resumed status is derived from its seats: open, partially_filled, or assigned when every seat is still filled), 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 (any whole number of hours from 1 to 720; 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 cutoff via autoAcceptMinMicScore (1-5 \u2014 applications scoring below your configured cutoff are auto-rejected, at/above proceed; null resets to the 3.0 default, below which applications only stay pending). The exclude-previous-participants list can be changed after posting: pass excludedParticipantSourceBountyIds with the full new list of up to ${MAX_EXCLUDED_PARTICIPANT_SOURCE_BOUNTIES} ids of your OWN earlier bounties (an empty array clears it); the same source rules as create_bounty apply, and a bounty can never exclude itself. 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. To change which countries may apply, pass supportedCountries with the full new list of ISO codes; omitting it leaves an explicit multi-country list in place (legacy bounties that only mirror a country-only location keep deriving that country from location), an empty array is stored as an explicit empty list but never lifts a country-only or on-site country restriction, and on-site bounties accept only their location country. 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' stops new applications and outreach, including on a fully staffed bounty; status 'open' resumes it, and the resumed status is derived from its seats: open, partially_filled, or assigned when every seat is still filled), 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 (any whole number of hours from 1 to 720; 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 cutoff via autoAcceptMinMicScore (1-5 \u2014 applications scoring below your configured cutoff are auto-rejected, at/above proceed; null resets to the 3.0 default, below which applications only stay pending). The exclude-previous-participants list can be changed after posting: pass excludedParticipantSourceBountyIds with the full new list of up to ${MAX_EXCLUDED_PARTICIPANT_SOURCE_BOUNTIES} ids of your OWN earlier bounties (an empty array clears it); the same source rules as create_bounty apply, and a bounty can never exclude itself. 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 = {
@@ -3345,6 +3361,7 @@ var handleCreateBounty = (args) => Effect9.gen(function* () {
       liveCaptureRequirement: params.liveCaptureRequirement || null,
       category: params.category || "computer-gigs",
       location: params.location || { isRemoteAllowed: true },
+      supportedCountries: params.supportedCountries ?? null,
       deadline: params.deadline || null,
       estimatedHours: params.estimatedHours,
       estimatedDurationUnit: params.estimatedDurationUnit || null,
@@ -3458,6 +3475,7 @@ var handleCreateBounty = (args) => Effect9.gen(function* () {
       skillsNeeded: params.skillsNeeded || [],
       category: params.category || "computer-gigs",
       location: params.location || { isRemoteAllowed: true },
+      ...params.supportedCountries !== void 0 ? { supportedCountries: params.supportedCountries } : {},
       deadline: params.deadline,
       estimatedHours: params.estimatedHours,
       priceType: params.priceType,

package/dist/types/index.d.ts

@@ -49,7 +49,7 @@ declare const CreateBountyRequest: Schema.Struct<{
     title: Schema.refine<string, Schema.filter<typeof Schema.String>>;
     description: Schema.refine<string, Schema.filter<typeof Schema.String>>;
     completionCriteria: Schema.refine<string, Schema.filter<typeof Schema.String>>;
-    evidenceTypes: Schema.refine<readonly ("link" | "text" | "photo" | "video")[], Schema.Array$<Schema.Literal<["text", "photo", "video", "link"]>>>;
+    evidenceTypes: Schema.refine<readonly ("text" | "link" | "photo" | "video")[], Schema.Array$<Schema.Literal<["text", "photo", "video", "link"]>>>;
     evidenceCriteria: Schema.optional<Schema.filter<typeof Schema.String>>;
     liveCaptureRequirement: Schema.optional<Schema.Literal<["photo", "video"]>>;
     requirements: Schema.optional<Schema.Array$<typeof Schema.String>>;
@@ -61,6 +61,7 @@ declare const CreateBountyRequest: Schema.Struct<{
         country: Schema.optional<Schema.filter<typeof Schema.String>>;
         isRemoteAllowed: Schema.optional<typeof Schema.Boolean>;
     }>>;
+    supportedCountries: Schema.optional<Schema.filter<Schema.Array$<Schema.filter<Schema.filter<typeof Schema.String>>>>>;
     deadline: Schema.optional<typeof Schema.String>;
     estimatedHours: Schema.refine<number, Schema.filter<typeof Schema.Number>>;
     priceType: Schema.Literal<["fixed", "hourly"]>;
@@ -145,6 +146,7 @@ declare const UpdateBountyRequest: Schema.Struct<{
         country: Schema.optional<Schema.filter<typeof Schema.String>>;
         isRemoteAllowed: Schema.optional<typeof Schema.Boolean>;
     }>>;
+    supportedCountries: Schema.optional<Schema.filter<Schema.Array$<Schema.filter<Schema.filter<typeof Schema.String>>>>>;
     status: Schema.optional<Schema.Literal<["open", "in_review", "paused", "closed"]>>;
     identityRequired: Schema.optional<typeof Schema.Boolean>;
     excludedParticipantSourceBountyIds: Schema.optional<Schema.filter<Schema.Array$<typeof Schema.String>>>;

package/package.json

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