src ▸ task opened 0

Automate Uber Eats

Turn the repetitive Uber Eats work you do by hand (search a store, read a menu) into a workflow Writ runs for you, on your own account, on a schedule or on demand.

Automate Uber Eats See how it works
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Uber Eats workflow
  1. 1
    search a store
  2. 2
    read a menu
  3. 3
    check item price
  4. 4
    place an order on your own account

✓ Recorded once, then run for you

gap ▸ done by hand 01
01
why

Stop doing Uber Eats by hand

The Uber Eats tasks you repeat (search a store, read a menu, check item price) are exactly the kind of work a computer should do. But Uber Eats has no general public API, and the flow runs behind a login and dynamic pages. Uber Eats' APIs are merchant- and delivery-partner-facing; there is no general API for browsing menus and prices.

Writ closes that gap. Record the Uber Eats task once (or describe it to an AI session) and Writ runs it for you in a real browser, on your own account. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

ops ▸ actions mapped 02
02
automate

Uber Eats tasks Writ can run for you

Each of these is a real Uber Eats action, captured into a workflow and run on your own account.

{ }search a store
{ }read a menu
{ }check item price
{ }place an order on your own account

Workflows extract structured fields such as menu item, item price, store availability, delivery fee along the way: typed data you can route anywhere.

build ▸ three routes 03
03
build

Three ways to build your Uber Eats automation

Pick whichever fits the task. All three produce the same workflow Writ can run for you.

✦Record itDo the Uber Eats task once in a real browser (search a store, then read a menu) and the recorder captures every step into a reusable workflow.
✦Describe it to AITell an AI session your goal on Uber Eats in plain language; it drives the live page and builds the workflow for you, no recording needed.
✦Discover itLet API discovery watch Uber Eats's own network calls as you browse, then turn the underlying requests into a fast, headless workflow.

Built on the same engine as the recorder and workflows, with 30+ step types.

auth ▸ logged-in web 04
04
the hard web

Login, 2FA, and dynamic pages on Uber Eats

The reason Uber Eats is tedious to automate is the same reason most tools can't. Writ handles it.

Writ signs into your own Uber Eats account through a Persona to read menus and prices inside that authenticated session.

PersonasTOTP & mailbox OTP AI navigationReal Chromium rendering
when ▸ it runs 05
05
when it runs

Run the Uber Eats automation on your terms

On a schedule, on demand, or the instant something changes. You choose the trigger.

✦On a scheduleRun the Uber Eats task every hour, every morning, or any cadence. No one has to remember to do it.
✦On demandTrigger a single run from the dashboard, a webhook, your code, or an AI agent, whenever you need it.
✦On a changeWatch Uber Eats for price change or store opens and fire the automation the instant it happens.
  1. 1
    Build the Uber Eats workflow once

    Record the task, describe it to AI, or discover it from the network. Writ captures each step, including login and 2FA, into a workflow you can edit.

  2. 2
    Run it on your terms

    Run it on demand, on a schedule, or fire it from a Monitor when Uber Eats changes. It runs on your own Uber Eats account, in a real browser.

  3. 3
    Call it from anything

    The same workflow is a REST endpoint at /v1/ubereats/run and an MCP tool, so your code, a no-code tool, or an AI agent can trigger the Uber Eats automation too.

watch ▸ changes tracked 06
06
watch

Trigger the Uber Eats automation on a change

Monitor Uber Eats for price change, store opens, new promo and run your workflow the moment it happens.

Monitors check as fast as every 10s (10s on Enterprise). A detected change becomes a trigger that runs your Uber Eats automation in seconds. Monitor Uber Eats ▸

venue ▸ local or cloud 07
07
run it

Free on your own machine, or on cloud

Local / BYO agent

No compute charge. The agent runs on your hardware, so it can reach Uber Eats even from an intranet or VPN-only network, and your AI keys never leave your machine.

Writ cloud

Metered by running time at $0.12 per browser-hour, drawn from your plan’s included usage. No infrastructure to manage.

call ▸ endpoint too 08
08
callable

The same Uber Eats automation is an API and an MCP tool

Automating Uber Eats for yourself and calling it from software are the same workflow. Once you have it, publish it as a REST endpoint at/v1/ubereats/run and a matching MCP tool, so your code or an AI agent can trigger the Uber Eats task too.

Uber Eats API Uber Eats MCP tools
also ▸ same workflow 09
09
other ways

Other ways to work with Uber Eats

Uber Eats APICall Uber Eats as a REST endpoint from your own software.Website to API Uber Eats MCP toolsExpose Uber Eats as MCP tools your agent can call.For AI agents Monitor Uber EatsWatch Uber Eats and act the instant it changes.Change detection Track Uber Eats pricesWatch Uber Eats prices and act on a drop.Price WorkflowsHow recorded workflows run, with login, 2FA, and 30+ step types.Product
faq ▸ questions answered 10
10
faq

Automating Uber Eats: questions

How do I automate Uber Eats?
Record the Uber Eats task once in the recorder (search a store, read a menu, check item price) or describe your goal to an AI session. Writ turns it into a workflow it can run for you on a schedule or on demand, on your own Uber Eats account. It usually takes minutes, not a backend project.
Is it allowed to automate Uber Eats this way?
Use Writ on your own Uber Eats account, within Terms of Service. Authorized automation of your own ordering. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Does Uber Eats automation work behind login and 2FA?
Writ signs into your own Uber Eats account through a Persona to read menus and prices inside that authenticated session. Writ handles TOTP and mailbox-OTP two-factor through Personas, so the automation runs inside your own authenticated Uber Eats session.
Can I run the Uber Eats automation without writing code?
Yes. Recording and AI sessions need no code at all. If you do want to trigger it from software, the same workflow is a REST endpoint and an MCP tool, but that is optional.
Where does it run, and what does it cost?
Run it on your own machine with a local or BYO agent for no compute charge, useful when Uber Eats is only reachable from your network or VPN. Or run it on metered cloud at $0.12 per browser-hour, drawn from your plan’s included usage. Start free.
rec ▸ ready ●

Automate Uber Eats in minutes

Record it once, then let Writ run it for you: on a schedule, on demand, or on a change. Get started free.

Get started