Base URL https://api.tilion.dev. Every request needs Authorization: Bearer $TILION_API_KEY. Pass record: true in the /v1/fetch request:
Request
The fetch response then carries a replay_url pointing at the recording:
Response
The replay is useful for debugging a scrape that behaves differently in production than locally: you can watch exactly what the page served, including any challenge or block screen.

​
Fetching a replay

This route serves the replay that replay_url points at, and its assets. The simplest path is to request replay_url directly. Authenticate with Authorization: Bearer $TILION_API_KEY, or with a view token as a ?token=<view-token> query parameter.