Turn Google Flights into a REST + MCP endpoint

Writ turns the Google Flights actions you already do in a browser into a callable REST endpoint your software (and your AI agents) can call.

curl -X POST https://api.usewrit.app/v1/google-flights/run \
  -H "Authorization: Bearer wt_8f2c...a91" \
  -H "Content-Type: application/json" \
  -d '{ "input": { "query": "your search term" } }'

Record the Google Flights task once (search a route and dates, then read fares) and call it as a REST endpoint and an MCP tool. No backend project, no waiting on Google Flights to ship an API.

1. 1
   Record the Google Flights task once

   Open the recorder and search a route and dates on Google Flights in a real browser. Writ captures each step, including login and 2FA, into a reusable workflow.

2. 2
   Publish it as an endpoint

   One click turns the workflow into a callable REST endpoint at /v1/google-flights/run and a matching MCP tool. Inputs become a typed schema.

3. 3
   Call it from anything

   Call Google Flights from your code, a no-code tool, or an AI agent. Run it on your own machine for free, or on metered cloud.

Read the REST API docs, see what's possible on workflows, or search for another site. Free to start. See pricing.

Google Flights has no general public API for the storefront actions most teams need. Google Flights has no public API; fares are rendered in the browser as the search completes.

Writ closes that gap. Record the Google Flights task once (or describe it to an AI session) and publish it as a REST endpoint at /v1/google-flights/run and a matching MCP tool. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

Each operation below is a real Google Flights action recorded into a workflow and exposed as a typed endpoint.

Returns structured fields such as flight fare, airline, stops, duration: typed JSON, not raw page text.

POST your inputs, get structured output. Authenticate every call with a scoped wt_ key.

curl -X POST https://api.usewrit.app/v1/google-flights/run \
  -H "Authorization: Bearer wt_8f2c...a91" \
  -H "Content-Type: application/json" \
  -d '{ "input": { "query": "your search term" } }'

import requests

r = requests.post(
    "https://api.usewrit.app/v1/google-flights/run",
    headers={"Authorization": "Bearer wt_8f2c...a91"},
    json={"input": {"query": "your search term"}},
)
print(r.json()["output"])

{
  "run_id": "run_goog_7b21",
  "status": "succeeded",
  "output": {
    "flight_fare": "...",
    "airline": "...",
    "stops": "..."
  }
}

The reason Google Flights has no usable API is the same reason it's hard to automate. Writ handles it.

Google Flights results are public; Writ renders them in real Chromium to capture fares and price-trend hints that populate dynamically.

Pick whichever fits the task. All three produce the same callable workflow.

Built on the same engine as the recorder and workflows.

Monitor Google Flights for fare drop, price-trend change, new lower option and fire this endpoint the instant something changes.

Monitors check as fast as every 10s (10s on Enterprise). A detected change becomes an automation trigger that runs your workflow in seconds. Monitor Google Flights ▸

Build a Google Flights API

Record it once, then call it from your software and your AI agents. Get started free.