FishingReportAgentBuild status
This page exists so that no claim on this site is left standing without a destination. Everything the marketing says is listed below against what actually exists today — and if it is not built, where it lands.
Live today
| What | Where | State |
|---|---|---|
| Generated fishing report — verdict, ride-out ladder, wind, tides, light, water temp | /report | Live |
| The verdict engine — go / go small / go inside / stay home | in every report | Live |
| Stored report artifacts — re-opening costs zero API calls | /reports | Live |
| Tides (NOAA CO-OPS) and sun/moon + solunar windows (USNO) | in every report | Live |
| MCP server, stdio — connect your own agent | /ai | Live |
| Attribution and safety disclaimer on every report and every tool result | everywhere | Live |
| Wave ladder | in reports | Partial — depends on a wave-capable buoy being in range |
Every claim, audited
Read this alongside Pricing. Nothing below has been quietly removed from the marketing — it is listed here with its true state.
| Claim | Where it's made | Today | Where it lands |
|---|---|---|---|
| "10 reports a day" (free) | Pricing | Not visible | The quota engine exists, but only for the MCP server. An account usage meter is the next build. |
| "Core conditions — wind, seas, water temp" | Pricing · free | Live | — |
| "Full reports with the ride-out ladder" | Pricing · Angler | Live | — |
| "Saved runs" | Pricing · Angler | Not built | Dashboard, after login exists. |
| "Morning email report" | Pricing · Angler | Not built | After accounts. Also gated on affiliate email-placement terms and CAN-SPAM compliance. |
| "API access" | Pricing · Angler | Not deployed | A hosted REST API. The endpoint shapes are on API & docs. |
| "Multiple runs & skippers" | Pricing · Captain | Not built | Dashboard team view. |
| "Client-ready report links" | Pricing · Captain | Partly live | Every stored report is already a stable, unguessable, link-only URL — see /reports. Per-report sharing controls come with accounts. |
| "Higher API allowance" | Pricing · Captain | Not built | Paid plans are defined in the quota model but nothing is wired or billable. |
| "Priority support" | Pricing · Captain | Not built | No support surface exists yet. |
| "Can I change plans? Yes — move up or down whenever you like." | Pricing FAQ | Not built | There is no billing and there are no plans to change yet. |
| Signup form (email + password) | /signup | Inert | Opens when login, sessions and the dashboard exist. Submitting it creates nothing today. |
| Login, dashboard, key generation, usage meter, logout | implied by signup + docs | Not built | The next workstream, shipped as a sequence — see below. |
What's next, and in what order
1 · Hosted API — done
Deployed and reachable at mcp.fishingreportagent.com: the MCP endpoint plus the account and key endpoints under /v1/*.
2 · Account & dashboard — done, sign-in gated
Login, sessions, dashboard, API keys, usage meter and logout are all built and browser-verified. Self-service sign-in is held closed pending a rate limiter that can actually enforce, so sign-in links are operator-issued. A signup with no login behind it was half a door; the door exists now, it is just deliberately locked.
3 · Saved runs, then delivery
Saved runs first (they feed everything else), then the morning email, which is also gated on affiliate email-placement terms.
4 · Coverage: inland, reefs, red tide, regulations
Inland is built and verified against live USGS gauges. Red tide is blocked on a licensing decision — the clean-licensed source is five years stale and the current one has no stated licence. Regulations will link out to the authority rather than promise automatic rules.
5 · Captain: team, links, billing
Multi-skipper, client-ready links and paid plans last — they need accounts and billing underneath them.
The rules we hold ourselves to
A missing value is reported as missing, with the reason. There is no sample-data fallback anywhere in the pipeline. If the sea state can't be read, the report refuses to clear the run.
One source per block, named. Single-source data is never described as multi-source or correlated.
Every promise on this site has a destination — a page that delivers it or this one, saying plainly that it's coming.