Airtasker ChatGPT Plugin

Airtasker는 처리해야 할 업무가 있는 사람들과 해당 업무를 완료할 수 있는 사람들을 연결해 주는 온라인 마켓플레이스입니다. 사용자는 업무를 게시하고 Tasker로부터 견적을 받은 뒤, 집 수리부터 개인 비서 서비스에 이르기까지 다양한 작업을 수행할 사람을 고용할 수 있습니다.

shipped 2026년 8월 26일productivityfreemium

Domain rating79Monthly visits777K/mo

productivity

핵심 포인트

1ai

2productivity

3product-hunt

Stork Quadrant

Sleeping Giant· 39/100

Has a real moat but invisible to agents. Add an MCP and you'd climb.

“The ChatGPT plugin wrapper is irrelevant — Airtasker's actual moat is the two-sided marketplace of vetted local workers and the coordination rails (payments, insurance, reviews) that make strangers trust each other enough to transact. An LLM alone cannot dispatch a handyman to your house. The plugin layer will die; the marketplace won't.”
— Claude Sonnet 4.6, scored 2026-08-26

Defensibility · 63/100

Physical-world coupling
Regulatory moat
Network liquidity
Proprietary refreshing data
High-trust catastrophic workflows
Multi-party coordination
Brand / community / taste

An LLM alone could replace

Suggest what type of tasker or service category fits a described job
Draft a task posting description from a user's rough notes
Compare quotes and recommend which to accept based on criteria
Answer questions about typical pricing for common local services

Agent-Readiness · 10/100

Verified MCP
Listed on agent surfaces
Usage-based pricing
Headless agent auth
Public OpenAPI
Active changelog— https://www.airtasker.com/blog (2026-07-13)
llms.txt

How to defend

Kill the plugin, build an agent-callable API instead — let AI assistants post tasks and receive quotes on behalf of users programmatically, making Airtasker the execution layer that agents route physical work through.

Ship an MCP server and list it on Stork — biggest single point gain (+25).
Get listed in the Anthropic MCP registry, Cursor, or Claude Desktop (+20).
Add a usage-based or per-call tier; per-seat-only pricing dies when agents replace seats (+15).
Expose API-key auth with a self-serve sandbox tier; remove sales-call gates (+15).
Publish an OpenAPI spec at /openapi.json or /.well-known/openapi (+10).

How this score is computed →See the full quadrant How to defend