Quickstart
BOOST renders each target in a real headless browser through a rotating proxy. Every session records the HTTP status, latency, fingerprint and a verdict; page content is scored for the ad markers you configured, and response bodies are not stored.
- 1Create an account and open /dashboard.
- 2Add your hostname under /dashboard/domains and publish the verification token.
- 3Queue a job with a session count inside your limit.
- 4Watch results land in /dashboard/tests; open any row for the full diagnostic.
Target authorization
Two mechanisms gate every job. Verified domains are checked first; the attestation is the fallback for one-off staging checks.
Domain verification
Add the hostname in the dashboard, then publish the generated token at a well-known path:
Press Verify. The server fetches the file over HTTPS and compares the token. Subdomains of a verified host are covered.
Attestation
When no verified domain matches, the job form requires an explicit checkbox confirming you own or are authorized to test the target. The attestation is stored with your IP and the job id.
Creating a job
A job is a target plus a session count. Sessions are independent browser contexts issued by the worker with bounded concurrency, each with its own fingerprint and proxy from proxies.txt.
The response returns the job id and status. Poll GET /api/v1/jobs/<id> or read GET /api/v1/results?job_id=<id>.
Proxy diagnostics
Jobs rotate through data/proxies.txt by default; the file is hot-reloaded when it changes. You can also add pinned profiles with scheme, host, port and optional credentials. A check fetches a neutral sink through the proxy and reports the exit IP and latency.
Credentials are stored server-side only and never rendered back into the page.
API reference
| Method | Path | Purpose |
|---|---|---|
| GET | /api/v1/health | Liveness, queue depth, pause state |
| GET | /api/v1/me | Resolve the key owner |
| POST | /api/v1/jobs | Queue a job |
| GET | /api/v1/jobs | List recent jobs |
| GET | /api/v1/jobs/{id} | Job status and result counts |
| GET | /api/v1/results | Paginated results, filterable |
| GET | /api/v1/metrics | Counts, pass rate, p95, 14-day series |
Keys are created in /dashboard/api. The plaintext appears once; only a SHA-256 hash is stored. Requests are limited per key and every job is written to the audit log.
Pass reasons
ad-marker and iframe-src mean ad markup rendered in the page. ad-tag-served means the ad network delivered a .js loader. ad-link-served means a smartlink reached the network handoff; the final hop is often an API endpoint with no visible markup. The reason is stored on every result row.
Error categories
| Category | Verdict | Meaning |
|---|---|---|
| ok | PASS | 2xx response, no blocking interstitial |
| challenge | BLOCKED | Challenge page detected in the body |
| http_block | BLOCKED | 403, 429 or 503 from the target |
| timeout | FAIL | Navigation exceeded LOAD_TIMEOUT_MS |
| proxy | FAIL | Proxy refused, tunnel failed or DNS died at the proxy |
| tls | FAIL | Certificate validation failed |
| connection | FAIL | Refused, reset or unreachable host |
Ad QA
/dashboard/adqa audits one authorised page in real browsers and reports what the ad stack actually did. Each session rotates a proxy and a device profile (desktop and mobile):
- Tag fire — ad-host requests: count, status, resource type and first-arrival time.
- Creative render — every iframe and ad container with rendered width, height and position.
- Viewability — pixels visible ≥50% for ≥1000 ms, sampled at 200 ms.
- Broken tags — tag-fired-no-creative, failed ad requests, HTTP errors.
- Geo — exit IP and country per session, so delivery gaps are visible.
Ad link pool
Adsterra direct links and smartlinks live in a per-account rotation pool at /dashboard/ads. A job in mode=ads picks links by weight instead of targeting one URL, and every hit passes a rate-limit guard:
- AD_MIN_INTERVAL_MS / AD_JITTER_MS — global spacing between session starts plus random jitter.
- AD_LINK_COOLDOWN — seconds a link rests after a hit (per-link override on the pool page).
- AD_PROXY_COOLDOWN — one exit IP is not reused against the same link inside this window.
- AD_BURN_SECONDS — a proxy that drew 429/403/challenge is skipped for this long.
- AD_BACKOFF_BASE / AD_BACKOFF_MAX — doubling bench time for repeat blocks on one link.
- AD_REFERRERS — comma-separated referrer URLs, one picked per hit.
Limits
- MAX_SESSIONS_PER_JOB — hard ceiling per job (default 250).
- DAILY_SESSION_QUOTA — per-account sessions per day (default 20,000).
- CONCURRENCY_PER_WORKER — parallel browser sessions per worker (default 4).
- LOAD_TIMEOUT_MS — navigation timeout per session (default 35,000 ms).
- SETTLE_AFTER_LOAD — seconds to wait after DOM ready (default 12).
- REQUEST_TIMEOUT_SECONDS — timeout for proxy health checks (default 20).
- API keys — 120 requests per minute per key; job creation 30 per minute per account.