ferry.fyi valid

Ferry FYI

Ferry FYI is an independent web and mobile app for planning Washington State Ferries trips using schedules, service bulletins, vessel positions, cameras, capacity forecasts, fares, tickets, and account alerts.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T04:53:44.400Z. Cached copy · Source on ferry.fyi

# Ferry FYI

> Ferry FYI is an independent web and mobile app for planning Washington State Ferries trips using schedules, service bulletins, vessel positions, cameras, capacity forecasts, fares, tickets, and account alerts.

This file is task-oriented documentation for readers and AI tools, not a search-ranking mechanism. Ferry information is time-sensitive planning context, not a boarding guarantee.

## Tasks

- **Plan a crossing:** Use [ferry schedules](https://ferry.fyi/) to choose departure and arrival terminals, a service date, and vehicle or passenger travel. Compare WSF wait reports with listed sailings, then check cancellations, delays, cameras and vehicle-space forecasts. Past-sailing reports are confirmed observations, not forecasts. Small timing differences may fall within the on-time tolerance. Arrival advice and departure countdowns are not measured queue waits; retain report timestamps and check the terminal named in route-wide alerts.
- **Estimate which sailing to catch:** Use the explicit form on a [Navigation page](https://ferry.fyi/seattle/bainbridge/navigation) for driving, walking, cycling, or transit. Availability depends on provider configuration. Estimates omit booth-line, parking, and reservation delays; probabilities are modeled, not measured boarding success. Never automate precise-origin requests.
- **Check conditions:** Open a route's cameras, map, or [WSF alerts](https://ferry.fyi/clinton/alerts). Public service alerts describe reported disruptions and advisories; they are separate from personal alert setup and exclude Ferry Riders Opinion Group promotions. Preserve alert severity, route scope, and source time; unavailable or pending reports are not an all-clear. Cameras show departure-terminal snapshots, not live video or measured waits; image-check times are distinct from source-image changes, and holding capacities are static references. Camera observations, vessel reports, and forecasts answer different questions; do not treat them as interchangeable.
- **Find terminal details:** Use a [terminal page](https://ferry.fyi/seattle/terminal) for its address and directions to the dock, parking, transport connections, accessibility, facilities, and route-planning links. WSF arrival guidance is general advice, not a live queue measurement; retain its source date and confirm changeable details with the operator.
- **Estimate a fare:** Compare default adult passenger and standard vehicle-with-driver one-way and round-trip rates, then calculate a custom fare. Select quantities from the route/date catalog; defaults are not personalized quotes or eligibility decisions. Free means an explicit zero fare, not unavailable pricing; a free departure does not establish a free return.
- **Manage personal travel:** [Tickets](https://ferry.fyi/tickets), favorites, and personal alerts require the holder's authorization. Unavailable ticket lookup does not invalidate a saved code; do not guess its product type or identifiers. Account sett
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=ferry.fyi · GET /v1/domain/ferry.fyi · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ferry.fyi:
1. POST https://agentwebmap.com/v1/sites/ferry.fyi/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://ferry.fyi/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/ferry.fyi/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ferry.fyi).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.