For people using AI assistants · and for the assistants

Order a local task with an AI assistant

Any assistant that can use a web browser can post a handyman, cleaning or errand request on RentAHuman for you, or book line standing. It fills in the request; you sign in and approve the payment. Posting recruits people — nobody is booked until an applicant is accepted, and there is no instant confirmation.

Pick a task pageAPI and MCP route

Paste this into your assistant

Brief for any assistant
Hi, please help me hire a person for a local task through RentAHuman.ai.

Task: [what needs doing — e.g. assemble one IKEA wardrobe and two bookshelves]
Where: [city or neighbourhood — share the exact address only after someone is accepted]
When: [date and time window]
Budget: [total in USD]
Done means: [how I will know it is finished]
Evidence: [e.g. photos of the finished work]

Steps:
1. Open the matching page: https://rentahuman.ai/services/handyman, /services/cleaning, /services/errands or /services/line-standing.
2. Use “Start a request” with the task, city and budget.
3. If RentAHuman asks me to sign in, stop and let me do it. Never ask for my password or codes.
4. Put the date window, “done means” and evidence into the task description. Keep my address out of the public text.
5. Before any payment (wallet funding or Stripe Checkout), show me the total and wait for my yes.
6. Send me the task link and its status. Do not call it booked — it is a request until someone is accepted.
7. Do not accept applicants manually or release payment without asking me.

Guides for specific assistants

Independent guides based on each company's own published descriptions, checked October 1, 2026. RentAHuman has no partnership, plugin or built-in connector with any of them.

The steps an assistant follows in the browser

  1. 1

    Open the matching task page

    Start from rentahuman.ai/services/handyman, /services/cleaning, /services/errands or /services/line-standing. Each page states what fits, what doesn’t, and how a request works.

  2. 2

    Fill in “Start a request”

    Enter the task, the city and the budget, then continue. This only opens the task form with those details; nothing is posted yet.

  3. 3

    Hand sign-in to the person

    RentAHuman asks for an account to post a task. The person signs in themselves; the assistant never asks for their password or a one-time code.

  4. 4

    Complete the task details

    Pick the city from the list, paste the brief into the description with the date window, the definition of done and the photo evidence wanted. Keep the exact address and door codes out of the public text.

  5. 5

    Stop for payment approval

    Submitting the form opens a funding review with the total. Confirming it posts the task and pays from the wallet or through Stripe Checkout, so show the person the total and wait for an explicit yes first.

  6. 6

    Report the real status

    Share the task link and its status — Pending funding until the deposit confirms, then Open while recruiting. Do not describe it as booked or confirmed.

  7. 7

    Leave hiring and payment decisions to the person

    Auto-review may accept qualified applicants. Ask before accepting anyone manually, and never release payment without the person’s explicit instruction after they approve the work.

Line standing is different. Line standing in New York, Los Angeles, San Francisco, Toronto or Vancouver books on /services/line-standing without an account: get the quote, review the canonical address it returns, and stop before Stripe Checkout for approval. Paying funds recruitment; a worker still has to confirm, and the payment is refunded if nobody confirms before the start.

Task pages to start from

Agents with API access: the safe ordering sequence

With a RentAHuman API key, an agent can post the same task through the REST API or the MCP server instead of the browser.

  1. 1

    Preview with a dry run

    Call create_bounty (MCP) or POST /api/bounties with "dryRun": true. A dry run validates the task and returns a preview; it creates nothing, reserves no funds and does not use up the idempotency key.

  2. 2

    Confirm with the person

    Show the preview — title, location, date window, budget, completion criteria and evidence — and post only after an explicit yes.

  3. 3

    Post once, safely

    Send the same body without dryRun and with an Idempotency-Key header (MCP: idempotencyKey). Retrying with the same key returns the original result instead of posting twice.

  4. 4

    Fund it

    If the account wallet covers the total, the task is funded from it and goes live. Otherwise it is created as pending_deposit and the response carries a deposit_url for the person to pay; it opens to applicants only after that deposit confirms.

  5. 5

    Report status honestly

    Poll the task and its applications. Open means recruiting, not booked. Auto-review may accept qualified applicants; otherwise accept only with the person’s go-ahead.

  6. 6

    Release only on instruction

    Review submitted evidence, then release payment (MCP: release_payment with acknowledgeRelease: true) only when the person explicitly says so. Release is irreversible.

Line standing over HTTP

GET /api/line-waiting returns the cities, rate and limits. POST /api/line-waiting with a bearer order capability and an action of quote, checkout or request prices or books it; keep the capability and reuse it to retry the same order. GET /api/line-waiting/{id} reports payment and staffing status. A 409 means conflicting details or an expired checkout — read the status, don't rebook.

Reference