Skip to main content
Vine is in beta. Here’s what’s covered today and how detection works.

Provider coverage

105 providers across the platforms a business transacts through: booking, ordering, scheduling, and commerce (OpenTable, Mindbody, Toast, Calendly, SevenRooms, Booker, Square, and ~100 more), with the deepest coverage on the appointment, booking, and ordering verticals. Beyond the catalog, Vine returns best-effort discovery: off-catalog vendors found on a site come back in discoveredProviders (slug, name, evidence URL), so you learn what a business runs even before a dedicated adapter exists.

Accuracy

Every detection is proven, not guessed. Vine reports a provider only when the connection is backed by first-party evidence on the business’s own pages: a logo, a marketing mention, or a third-party directory listing never counts on its own. When a connection can’t be proven, Vine doesn’t report it. The result is a resolved actionUrl you can hand straight to an agent, not a probabilistic guess to double-check.

Latency

Detection runs live: Vine renders the site and follows the booking or ordering flow in real time, so a fresh detection typically completes in 1–2 minutes. That’s the trade for results that are accurate and current, resolved per URL, rather than served from a stale fingerprint database.
  • The service-side domain cache is disabled by default. When Vine explicitly enables it, eligible repeat lookups return in ~1 second, flagged "cached": true with a detectedAt timestamp. Pass ?mode=fresh to force a live scan even then.
  • If a site is too slow to finish within the deadline, Vine returns {"status": "detection_incomplete"} (retryable, and billed at the base rate only), never a hang or a 5xx.
  • Sub-30-second detection is on the near-term roadmap.

Freshness

Results are live scans by default. When the service-side cache is enabled, hits are no older than 7 days and always flagged—never months-stale fingerprints.

Rate limits & credits

Every billable response carries vine-credits-used and vine-credits-remaining headers. Need more? contact@getcourtyard.ai.

On the roadmap

  • Data extraction from detected providers: schedules, menus, availability.
  • Reverse lookup: enumerate every site running a given provider.
  • MCP server, webhooks, teams, and SLAs.