Turn USPS Tracking into a REST + MCP endpoint

Writ turns the USPS Tracking 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/usps/run \
  -H "Authorization: Bearer wt_8f2c...a91" \
  -H "Content-Type: application/json" \
  -d '{ "input": { "query": "your search term" } }'

Record the USPS Tracking task once (look up a tracking number, then read the latest scan) and call it as a REST endpoint and an MCP tool. No backend project, no waiting on USPS Tracking to ship an API.

1. 1
   Record the USPS Tracking task once

   Open the recorder and look up a tracking number on USPS Tracking 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/usps/run and a matching MCP tool. Inputs become a typed schema.

3. 3
   Call it from anything

   Call USPS Tracking 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.

USPS Tracking has an API, but USPS has a Web Tools API requiring registration; for ad-hoc tracking the public page returns the same status.

Writ closes that gap. Record the USPS Tracking task once (or describe it to an AI session) and publish it as a REST endpoint at /v1/usps/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 USPS Tracking action recorded into a workflow and exposed as a typed endpoint.

Returns structured fields such as tracking status, last scan, expected delivery, location: 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/usps/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/usps/run",
    headers={"Authorization": "Bearer wt_8f2c...a91"},
    json={"input": {"query": "your search term"}},
)
print(r.json()["output"])

{
  "run_id": "run_usps_7b21",
  "status": "succeeded",
  "output": {
    "tracking_status": "...",
    "last_scan": "...",
    "expected_delivery": "..."
  }
}

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

USPS tracking pages are public; Writ renders them in real Chromium to capture the latest scan and status.

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

Built on the same engine as the recorder and workflows.

Monitor USPS Tracking for status change, out for delivery, delivery exception 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 USPS Tracking ▸

Build a USPS Tracking API

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