Agencies and research bodies

Request data access

Government agencies and research bodies get scoped, read-only, audited access to the shared layers through an MCP server (for AI assistants and agents) or plain REST. Ask for the bays, products, aggregation level and date range you need; an administrator approves the request and issues an API key whose scope is exactly what was approved.

What is shared

Bay-level signals per day (thermal, bloom, runoff, growing conditions), or per site when approved.
Dated bay events: HAB closures and exceedances, marine heatwaves, storms (wave or gale episodes at the bay reference cell).
Model skill against ground-truth stations and the bloom back-test.
Model, satellite and station time series, each with its source, product, scale, lead time and licence.

What is never shared

Operator records: loggers, harvest and mortality logs, notes, photos, briefs.
Personal data of growers or their accounts.
Anything outside the bays, products, aggregation and dates an administrator approved.

Every call is logged and keys can be revoked at any time.

Checking your session…

Connect a client

MCP endpoint https://coastal-intelligence.triskelionaisystems.com/api/mcp (streamable HTTP), key in the Authorization: Bearer header. For clients that read an mcpServers file (Claude Code and most others), with the key in AGENCY_KEY:

{
  "mcpServers": {
    "coastal-intelligence": {
      "type": "http",
      "url": "https://coastal-intelligence.triskelionaisystems.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${AGENCY_KEY}"
      }
    }
  }
}

The same tools answer as REST under /agency/ (bays, sites, signals, events, skill, timeseries, backtest, datasets). Full guide: Agency data access.