Release notes & support

Release notes & support

Dated entries taken from the release ledgers, newest first. Each entry names its evidence class; owner-funded tests are not sales and not independent benchmarks.

Release notes

Quality release — current public builds and examples synced

  • Hiring 2.0.20, Contact 0.2.4, SaaS Pricing 0.2.3, Retail Availability 0.2.4, Customer Proof 0.2.3, Partner Programs 0.2.3, Integration Evidence 0.2.4.
  • Each public service passed one source-backed positive and one unsafe-input owner-funded cloud check; unsafe requests recorded zero result events.
  • The API/MCP pins, dated unmodified reports, schemas, page copy and machine-readable documentation use the same catalog. Original historical examples remain archived.
  • Prices and public/private status unchanged; no new paid call was made for this website update.

Limit: Narrow release smoke tests, not broad coverage, an independent MCP purchase, confirmed customer revenue or profitability.

Owner-funded cloud tests Source record: ledgers/portfolio-quality-sync-2026-10-08.json

Documentation release — Hiring 2.0.19, Contact 0.2.3

  • Hiring Signals default build 2.0.18 → 2.0.19 (build 9jwwlfWj8z5WuvYsu).
  • Contact & Booking default build 0.2.2 → 0.2.3 (build Fj1hxkmJ1SVXtS37g).
  • README and examples only; runtime unchanged.
  • One owner-funded validation run each: Hiring iccSKN2vi1E4Emrv7, Contact Mb74YMiSOv2ehkyeL.

Limit: Two narrow positive smoke tests; not a coverage benchmark and not independent purchases.

Owner-funded cloud tests Source record: ledgers/documentation-release-2026-10-08-REPORT.txt

Public docs repo updated

  • Seven-service question/output/price/limit table in the README.
  • Dated full examples (unmodified owner-funded release-test reports).
  • Capped API and MCP templates with same-run recovery.
  • Commits 69656cf2, abab4de8, 4476d158.

Limit: No new cloud run or build. Capped MCP templates were checked offline; no live MCP purchase was performed.

Documentation only Source record: ledgers/agent-polish-round2-2026-10-08-REPORT.txt GitHub skills repo

Reliability release — Hiring 2.0.18, Contact 0.2.2

  • Hiring 2.0.17 → 2.0.18: job detail/feed identity, malformed listing and date handling, duplicate evidence, exclusion of non-job posts.
  • Contact 0.2.1 → 0.2.2: booking-intent checks, exclusion of provider/legal/docs/login routes, phone extension handling, strict mailto recipients.
  • Six owner-funded bounded cloud tests passed (Hiring: Ashby company VERIFIED, Greenhouse company PARTIAL, unsafe input INVALID_INPUT with 0 events; Contact: two VERIFIED, unsafe input INVALID_INPUT with 0 events).

Limit: Release tests, not a broad precision benchmark and not sales.

Owner-funded cloud tests Source record: ledgers/customer-readiness-2026-10-08-REPORT.txt

Five Actors published publicly

  • SaaS Pricing 0.2.2, Retail Availability 0.2.3, Customer Proof 0.2.2, Partner Programs 0.2.2, Integration Evidence 0.2.3.
  • 18/18 bounded cloud contract checks passed across nine release candidates, two each, including the four that remain private (owner-funded).
  • Four other validated services remain private (see “Validated but private” below).

Limit: Small smoke samples, not coverage or precision benchmarks and not proof of customer demand.

Owner-funded cloud tests Source record: ledgers/publication-approved-2026-10-08-REPORT.txt

Default builds verified — Hiring 2.0.17, Contact 0.2.1

  • Hiring Signals 2.0.17 default build verified.
  • Contact & Booking 0.2.1 default build verified.

Limit: Superseded by the 2026-10-08 releases above.

Read-only metadata check Source record: ledgers/service-catalog-2026-10-05.json

Owner-funded cloud examples recorded for all services

  • Unmodified report objects from owner-funded cloud checks, archived with original inputs and timestamps.
  • Superseded by the 2026-10-08 recorded examples; the 4 October archive remains unchanged in the docs repo.

Owner-funded cloud tests Source record: github-repo/README.md

Hiring cloud validation cohort (24 companies) recorded

  • Owner-funded cohort of 24 companies on build CTATHD9BRo5auMxMb.
  • Results are summarized on the Evidence page as a small sample, not a precision benchmark.

Owner-funded cloud tests Source record: ledgers/hiring-service-metadata-2026-09-30.json Evidence & methodology

Community catalog submissions

Pull requests to the community skills catalog — submitted; acceptance not verified. A submission is not a listing.

Current state — Last checked

From a read-only, anonymous Apify API metadata check. This is a dated snapshot, not live status: there is no continuous monitoring. Recheck the Apify Store page before purchase.

Seven public Actors, last checked 2026-10-08T12:16:53.713706+00:00
ServiceDefault buildPrice per eligible reportPublic
Hiring Signals company-recent-job-openings 2.0.20 $0.03 Yes (anonymous metadata read)
Contact & Booking verified-contact-booking-signals 0.2.4 $0.01 Yes (anonymous metadata read)
SaaS Pricing verified-saas-pricing 0.2.3 $0.02 Yes (anonymous metadata read)
Retail Availability verified-retail-availability 0.2.4 $0.01 Yes (anonymous metadata read)
Customer Proof verified-customer-proof 0.2.3 $0.02 Yes (anonymous metadata read)
Partner Programs verified-partner-programs 0.2.3 $0.02 Yes (anonymous metadata read)
Integration Evidence verified-integration-evidence 0.2.4 $0.02 Yes (anonymous metadata read)

Validated but private (not callable)

Other validated services are currently private and not callable; they are not listed in this catalog. They have no public prices, schemas, examples or instructions on this site.

  • qualified-b2b-lead-finder — validated, private, not callable
  • claim-verification — validated, private, not callable
  • verified-company-updates — validated, private, not callable
  • verified-developer-api-docs — validated, private, not callable

Support

Report a problem

Open an issue on GitHub issues, or use the issue tab of the Actor’s Apify Store page. Include:

  • the run ID,
  • the build number used,
  • the exact input JSON,
  • what you expected and what the report said (status, error_code).

Never include an Apify token — not in issues, screenshots, logs or URLs.

Published by Boatify Rentals LLC; maintainer Majd Hijazin. We own the paid Actors and can receive eligible usage revenue. A click, copy or install is not revenue.