# NOAA Essential Fish Habitat Screener Example

**Use case:** 

Worked NOAA EFH screen: 152 rows across 6 coastal sites with species, life stage, council, HAPC overlap and Magnuson-Stevens 305(b)(2) flags.

## Input

```json
{
  "assets": [
    {
      "lat": 28.5,
      "lon": -91,
      "label": "Gulf of Mexico - offshore Louisiana"
    },
    {
      "lat": 29.25,
      "lon": -94.8,
      "label": "Galveston TX - nearshore"
    },
    {
      "lat": 36.95,
      "lon": -76,
      "label": "Chesapeake Bay mouth VA"
    },
    {
      "lat": 42.35,
      "lon": -70.7,
      "label": "Massachusetts Bay"
    },
    {
      "lat": 33.7,
      "lon": -118.25,
      "label": "San Pedro Bay CA"
    },
    {
      "lat": 39.7392,
      "lon": -104.9903,
      "label": "Denver CO (inland control)"
    }
  ],
  "radiusMiles": 0,
  "maxAssets": 500,
  "contextRadiusMiles": 25,
  "includeHapc": true
}
```

## Output

```json
{
  "asset_label": {
    "label": "Asset label",
    "format": "string"
  },
  "in_efh": {
    "label": "In Essential Fish Habitat",
    "format": "boolean"
  },
  "efh_site_name": {
    "label": "EFH designation name",
    "format": "string"
  },
  "life_stage": {
    "label": "Life stage",
    "format": "string"
  },
  "fmc_name": {
    "label": "Fishery-management council",
    "format": "string"
  },
  "hapc_overlap": {
    "label": "HAPC overlap",
    "format": "boolean"
  },
  "hapc_site_names": {
    "label": "HAPC site names",
    "format": "string"
  },
  "coastal_context": {
    "label": "Coastal context",
    "format": "string"
  },
  "nmfs_efh_consultation_likely": {
    "label": "EFH consultation likely",
    "format": "boolean"
  },
  "partial_result": {
    "label": "Partial result",
    "format": "boolean"
  },
  "checked_at": {
    "label": "Checked at",
    "format": "string"
  }
}
```

## About this Actor

This example demonstrates how to use [NOAA Essential Fish Habitat Screener — EFH Consultation Check](https://apify.com/malonestar/noaa-efh-consultation-screener.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/malonestar/noaa-efh-consultation-screener.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/malonestar/noaa-efh-consultation-screener.md

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).