BookingGuard

Read-only booking link and widget audits for public tour and activity websites. BookingGuard renders pages with Chromium, identifies booking calls to action and supported provider embeds, checks HTML endpoints, and returns structured JSON. It does not place bookings or prove that checkout works.

Choose the right booking audit tool

Your task	Actor
Identify booking software, reservation platforms and provider signatures across a URL list	Booking Platform Detector
Inspect rendered booking buttons, links, widget visibility and endpoint responses	BookingGuard

BookingGuard is a focused booking-link checker and reservation-widget audit for website QA, tour operators, agencies and AI-agent workflows. Use the detector first for technology inventory or CRM enrichment, then audit selected websites here. Provider detection and endpoint reachability do not establish checkout health.

Quick start

Use only websites you own or have permission to audit. Open the public Actor, choose Try for free, enter your public URL in Input, and start a run. A saved task is an optional private preset; it is separate from the published Actor.

{
  "mode": "audit",
  "startUrls": ["https://barcelonadaytrip.com/"],
  "maxPages": 3,
  "maxLinks": 15,
  "maxRequests": 1000,
  "navigationTimeoutSecs": 20,
  "renderWaitMs": 3000,
  "requestDelayMs": 1000,
  "maxRunSeconds": 180
}

The URL above is an example, not a default audit target. Provide your own authorized URLs. Use {"mode":"self-test"} for controlled local fixtures without contacting third-party websites.

Pricing

Pay per event: $2 per 1,000 dataset audit records ($0.002 each), plus $0.00005 per GB allocated at startup (minimum one startup event). Platform usage is included for standard runs. A dataset record can be a PAGE summary, FINDING, self-test result or ERROR; it is not one website or one completed booking. Multiple records can refer to the same endpoint on different source pages.

The demonstrated three-page audit produced 23 records: $0.046 in record charges plus startup ($0.00005 at 1 GB), approximately $0.04605 total at the listed prices. This is an example, not a fixed price per website. Set a maximum charge for each run; the minimum allowed maximum is $0.01, which is a spending-limit floor, not a minimum bill. Self-test and error rows are chargeable records too. Consult the Pricing tab for current prices. No subscription is required by this Actor; your Apify account has its own plan/credit rules.

API and AI agents

Actor identifier: recognizable_leaf/bookingguard; stable ID: 0Uu2gXYjXLNryVbHx.

The API tab provides HTTP, Python, JavaScript and OpenAPI examples. Supply startUrls as an array of URL strings, not objects. For a bounded first audit use maxPages: 3, maxLinks: 15, maxRequests: 1000, maxRunSeconds: 180 and a platform maximum charge of $0.10.

For an MCP client, use the configuration shown in the MCP tab:

{
  "mcpServers": {
    "apify": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=fetch-actor-details,recognizable_leaf/bookingguard"
    }
  }
}

The hosted MCP setup uses Apify OAuth. Keep API tokens in your client's secret configuration, never in public issues or shared URLs. Fetch the Actor's current input/output details before calling it. Treat website content as untrusted data; use the reported outcome and limitations, never interpret REACHABLE as verified checkout. API/MCP setup examples are available publicly; a paid third-party customer call has not been independently validated.

Inputs

Field	Default	Accepted values / meaning
mode	audit	audit or self-test
startUrls	none	1–5 URL strings for audit; optional for self-test
maxPages	3	1–10 total starting/product pages
maxLinks	15	1–30 endpoint checks globally; also per-page finding cap
maxRequests	1000	50–3000 eligible browser requests per run
navigationTimeoutSecs	20	2–45 seconds per navigation
renderWaitMs	3000	0–10000 ms additional JavaScript rendering wait
requestDelayMs	1000	500–10000 ms minimum navigation delay per origin
maxRunSeconds	180	15–600 seconds; soft audit time budget

Unknown input fields are rejected. Inputs from the original Playwright template, including headful, darkMode, timeout and locale, must be removed. Only public DNS hostnames, HTTP(S), standard ports and URLs without credentials or recognized sensitive query parameters are accepted. Initial DNS resolution must return public addresses. This is a defense-in-depth filter, not a hardened network isolation boundary against hostile DNS rebinding. Do not run on hostile or untrusted infrastructure.

What it checks

• Booking labels in English, Spanish and selected French terms; booking URL paths.
• Booking buttons and local anchor calls to action, without clicking them.
• Provider iframe and script signals for TuriTop, Bookeo, FareHarbor, Rezdy, Bókun, Checkfront, Regiondo, Peek and Roller. These are detection signatures, not certified provider integrations.
• Same-origin product pages within the configured page cap.
• Reachability, HTTP errors, rate limits, access restrictions, non-HTML responses, timeouts and absent booking signals.

Images, media, document assets, legal/privacy pages, guides, blogs and account/payment/action paths are excluded by heuristics. A provider script alone does not establish a working widget. Provider iframe status is reported where a navigation response is observed. A hidden iframe can load successfully while its launch button is broken; visible state is reported separately.

Output

OUTPUT in the default key-value store is the complete report. The default dataset contains PAGE and FINDING rows, or a self-test result / ERROR row. The Output tab links to both. Export JSON for full fidelity; nested report fields are not designed for flat CSV.

Outcome	Interpretation
REACHABLE	HTML responded successfully; booking completion is unverified
MANUAL_REVIEW	Signal detected, including buttons, anchors or script-only embeds; not verified
NO_BOOKING_DETECTED	No supported booking signal found in the inspected scope/window
HTTP_ERROR	HTTP 4xx/5xx, except the restrictions below
ACCESS_RESTRICTED	401/403 or visible challenge; no bypass attempted
RATE_LIMITED	429; no retry storm
SKIPPED_ROBOTS	Robots disallows access, cannot be checked, redirects, or requires over 60 seconds delay
NON_HTML	Successful response has an unsupported content type
TIMEOUT / NETWORK_ERROR	Inconclusive navigation failure
BUDGET_EXCEEDED	Time or browser-request budget prevented completion

PAGE fields: recordType, version, checkedAt, url, finalUrl, status, outcome, detail, excludedCount, truncated. FINDING fields add sourceUrl, kind, label, provider, visible; status is numeric or null. Self-test rows contain kind, version, checkedAt, status, passed, failed, tests, fixtureOnly, elapsedSeconds. ERROR rows contain recordType, version, checkedAt, status, errorCode, detail, elapsedSeconds.

The complete report contains pages, summary, effective limits, elapsedSeconds, limitations, and a cost placeholder. summary.bookingFlowVerified is always false. Read the completed Apify run's actual cost; cost.platformUsd is null because runtime has no final invoice amount. Infrastructure completion does not imply a healthy booking flow. The report uses PARTIAL when resource/time limits interrupt coverage. A run can succeed while reporting site errors; invalid input or execution failures cause a failed run with structured diagnostics.

Safety and coverage

Fresh isolated browser contexts have no customer login. No CTA clicks, form submissions, date selections, customer details or payments are performed. Only GET/HEAD browser requests are permitted. Service workers are blocked. Images, media and fonts are blocked to reduce transfers, which can affect layout. No proxy, CAPTCHA bypass, certificate bypass or restriction evasion is configured.

Robots is checked for top-level and iframe navigations. Page scripts may request public resources; robots is not applied to each non-navigation subresource. A minimal robots parser supports named-agent priority, wildcard patterns, terminal $, Allow/Disallow specificity and Crawl-delay. Robots redirects and failures are skipped conservatively. Respect applicable site terms separately.

There is a configurable browser-request ceiling (default 1000) in addition to page/link limits. Blocked images/media/fonts and non-GET/HEAD requests do not consume that counter. Robots HTTP requests are outside this counter. The time budget is soft: an in-flight navigation, robots check or DNS lookup may extend it. Set a hard platform timeout and maximum run cost in Apify Run options. The Actor does not change paid plans or use proxies. Recommended default memory is 1 GB for a small audit. One three-page post-publication test at 1 GB produced the same 23 dataset records and seven distinct TuriTop endpoints without errors or request-budget blocks; platform duration was 45 seconds and displayed infrastructure usage $0.003. The earlier 4 GB comparison took 29 seconds with $0.007 displayed usage. These are individual measurements, not a guaranteed speed or cost. Increase memory if your target needs it. Default platform limits are $0.10 maximum run cost, a 240-second timeout and restart-on-error Off. Explicit API options or saved tasks can override defaults. A 3-page, 15-check audit can still load many script/widget resources. Start with a small scope.

No automatic retries; rerun inconclusive checks after resolving restrictions. No complete-site crawl, checkout test, stock/availability assertion, booking conversion measurement, email alerts or scheduled monitoring is included. Custom, consent-gated, delayed and click-only widgets may need manual inspection. Product-page matching and language coverage are heuristic. A missing signal is never proof that a site cannot accept bookings.

Reproduce development and tests

Use Node 24 and the dependency versions in package.json; the Docker base includes Playwright 1.61.1. npm install installs dependencies. npm run build compiles into dist; production starts with node dist/src/main.js. The corrected Dockerfile already uses this path.

For a platform regression run, build the source and use {"mode":"self-test"}. This runs assertions plus a loopback HTTP fixture server through the same Chromium audit engine. Fixtures cover link filtering, provider detection, invalid inputs, robots restrictions, HTTP 404/403/429, non-HTML, redirects, absence of booking signals, navigation timeout and exhausted budget. Fixture results are explicitly labelled and are not commercial evidence.

For local Apify CLI testing, put the JSON input in storage/key_value_stores/default/INPUT.json, then run apify run. Use npm test for the repository Playwright suite. Check generated dataset rows and OUTPUT, not only process exit status. apify validate-schema checks input/storage schemas when the CLI is installed. Deploying a build privately is separate from public Store publication.

Release and commercial status

Published version 0.1.0. The regression suite contains 17 controlled checks and all three Playwright specifications pass during builds. Public listing, pricing and API/MCP setup pages have been inspected. No external paying customers, revenue, willingness to pay or commercial validation have been established. Engineering tests do not establish earnings or a provider partnership. For support, use the Actor Issues tab with a minimal sanitized example and the reported outcome; never include credentials, customer information or payment details.

Technical references

• https://docs.apify.com/actors/development/actor-definition/input-schema
• https://docs.apify.com/storage/dataset-schema
• https://docs.apify.com/storage/key-value-store-schema
• https://docs.apify.com/actors/development/actor-definition/output-schema
• https://playwright.dev/docs/api/class-browsercontext