scrape-ci-standalone
  / - here
  /api/result/:id - retrieve job result ({ pending: true } while still running)
  /api/scrape - run a scrape job
    auth - authorization for the request
    url - the URL to scrape
    rescrape - optional, ignore any cached result
    async - optional, respond immediately with { jobId } and scrape in the
            background; poll /api/result/:jobId (omit for the full result
            in the response)
  /api/update - force update scrapers; responds with
    { updated: [{ package_id, before, after }] } listing version changes
    (before is absent for newly installed packages)

  /api/admin/apikey - manage API keys
    GET /api/admin/apikey - list all API keys with usage
    POST /api/admin/apikey - create a new API key
      note - required, a note to identify the API key
      limit - optional, number of allowed scrapes per day (default: 200)
    DELETE /api/admin/apikey - revoke an API key (kept, not deleted)
      key - required, the API key to revoke
    POST /api/admin/apikey/reactivate - reactivate a revoked API key
      key - required, the API key to reactivate

  /api/admin/scrapes - list recent scrapes
    limit - optional, max results to return (default: 20, max: 100)

  /api/admin/scrapers - list installed scrapers (id, version, package release date)

  /api/admin/scraper - manage individual scraper packages
    POST /api/admin/scraper - install a package from the CommunityScrapers index
      id - required, the package id (e.g. "Altwolia")
    DELETE /api/admin/scraper - uninstall a package
      id - required, the package id

  /upload - submit a new scrape job
  /admin - manage API keys
  /scene?id=:id - view scene result

  apikey can be in any of the following locations:
    body.auth
    ?auth= in query params
    x-api-key header