Turn Nike into a REST + MCP endpoint
Writ turns the Nike 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/nike/run \
-H "Authorization: Bearer wt_8f2c...a91" \
-H "Content-Type: application/json" \
-d '{ "input": { "query": "your search term" } }' No Nike API yet? Build one in minutes
Record the Nike task once (search a keyword, then open a product) and call it as a REST endpoint and an MCP tool. No backend project, no waiting on Nike to ship an API.
- 1Record the Nike task once
Open the recorder and search a keyword on Nike in a real browser. Writ captures each step, including login and 2FA, into a reusable workflow.
- 2Publish it as an endpoint
One click turns the workflow into a callable REST endpoint at /v1/nike/run and a matching MCP tool. Inputs become a typed schema.
- 3Call it from anything
Call Nike 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.
Nike doesn't give you the endpoint you need
Nike has no general public API for the storefront actions most teams need. Nike has no general public API for product availability, drop launches, or size stock.
Writ closes that gap. Record the Nike task once (or describe it to an AI session) and publish it as a REST endpoint at /v1/nike/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.
What you can call on Nike
Each operation below is a real Nike action recorded into a workflow and exposed as a typed endpoint.
Returns structured fields such as product price, size availability, launch time, rating: typed JSON, not raw page text.
A real Nike endpoint, authorized with a wt_ key
POST your inputs, get structured output. Authenticate every call with a scoped wt_ key.
curl -X POST https://api.usewrit.app/v1/nike/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/nike/run",
headers={"Authorization": "Bearer wt_8f2c...a91"},
json={"input": {"query": "your search term"}},
)
print(r.json()["output"]) {
"run_id": "run_nike_7b21",
"status": "succeeded",
"output": {
"product_price": "...",
"size_availability": "...",
"launch_time": "..."
}
} Also an MCP tool. The same workflow is exposed as an MCP tool your AI agent can call. See Nike MCP tools, or browse all MCP clients.
Login, 2FA, and dynamic pages on Nike
The reason Nike has no usable API is the same reason it's hard to automate. Writ handles it.
Nike product pages are public; Writ renders them in real Chromium to capture size availability and drop timing that load dynamically.
Three ways to build your Nike endpoint
Pick whichever fits the task. All three produce the same callable workflow.
Built on the same engine as the recorder and workflows.
Trigger your Nike endpoint on a change
Monitor Nike for drop launch, restock, size back in stock 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 Nike ▸
Free on your own machine, or on cloud
Local / BYO agent
No compute charge. The agent runs on your hardware, so it can reach Nike 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.
Other ways to work with Nike
Nike API questions
Does Nike have an API?
Is there a ready-made Nike API I can use?
Is it allowed to automate Nike this way?
Does this work with Nike login and 2FA?
Can I run it on my own machine?
Build a Nike API
Record it once, then call it from your software and your AI agents. Get started free.