GigNGo Local Services Marketplace

Search for local workers on GigNGo by service category and location. Returns public worker profiles (name, bio, skills, rates, rating, review count, service area, profile URL) sorted by rating. Use list_service_categories first if you are unsure of the service slug. State is the full state name in lowercase with hyphens (e.g. "new-york", "north-carolina"); city likewise (e.g. "los-angeles"). Returns up to `limit` workers per page.

Get the full public profile of a single GigNGo worker by their profile slug. Returns display name, bio, skills, per-skill rates, rating, review count, badges, service area, availability, and a shareable profile URL. Slugs come from search_local_workers results (the "slug" field) or from gigngo.org/worker-profile/{slug} URLs.

Check which of the 30 service categories have active workers in a US state or city, with worker counts per service. Useful before searching, or to answer "can I get X done in Y?". State is required (full name, lowercase, hyphens: "new-jersey"); city is optional — omit it for state-level availability.

Browse open consumer tasks (jobs) posted on GigNGo that workers can apply to. Each task includes title, description, `details` (the poster's Additional Details note, present on most jobs and usually the most specific part), category, budget, approximate location (coordinates are privacy-offset), when it was posted (postedAt, ageHours, ageDays, postedAgo), how many locals have applied (applicantCount, hasApplicants) and how fast the first one did (hoursToFirstApplicant), plus a link to apply. Filter by category, state, city, age or applicant count, and sort by newest, oldest, most_applicants or fewest_applicants. All filters are optional — call with no arguments for the most recent open tasks nationwide.

Find which US cities are actually converting: how many jobs each area posted, how many locals applied, what share of jobs got any reply at all, and the median hours to the first applicant. Ranked by a "heat" score that combines applicant density with response reliability, shrunk toward the platform average so a single lucky job cannot outrank a real market — read `heat` next to `confidence`. Use this to decide where supply is dense (spend more) versus where jobs go unanswered (a supply hole). Complements get_service_availability, which counts workers rather than measuring whether they respond.