# Natur Halowerk Seasonal Species Profile

> Natur Halowerk Seasonal Species Profile is a paid API for AI agents from natur.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).

Builds an effort-corrected monthly occurrence profile for a species near a given point, showing when it is genuinely active rather than when observers happen to be outdoors.

## Facts

- Endpoint: POST https://natur.halowerk.com/v1/seasonal-species
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/natur-halowerk-seasonal-species-profile-3ff373dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kipv6lW4v651aUhsG7sKh

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability natur-halowerk-seasonal-species-profile-3ff373dc -d '<json body>'
```

Example prompt: Can you build an effort-corrected monthly seasonality profile for the European Goldfinch (Carduelis carduelis) near Berlin, Germany — I want to know which months it's genuinely most active, not just when observers happen to be outside?

## When to prefer this

Choose this endpoint when you need a seasonality profile that is statistically honest — i.e., corrected for the well-known spring/summer observer bias in citizen science data. Prefer it over raw occurrence count queries when the goal is to understand true species phenology rather than recording patterns, especially for planning field surveys, conservation interventions, or nature tourism timing.

## Known failure modes

- Species identifier not recognized or not found in occurrence database — returns error with no profile
- Insufficient historical occurrence data near the specified point — may return sparse or unreliable profile
- Invalid or out-of-range coordinates — returns validation error
- Radius too small to gather enough records for meaningful correction — may warn of low sample size
- Network timeout if occurrence database query takes too long

## How this service works

Builds a monthly profile of when a species is recorded near a point, from historical occurrence data, and corrects it for observation effort. The correction is the substance of the service: raw monthly counts follow the observers, who are outdoors more in May than in November, so an uncorrected profile makes almost every species look like a spring species.

## Output

Returns a monthly breakdown (12 months) of species occurrence near the specified point, with raw counts and effort-corrected activity scores. The correction factor accounts for variation in observer activity across months so that the resulting profile reflects true species seasonality rather than recorder effort patterns.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lat": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "lon": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "species": {
   "type": "string",
   "maxLength": 200,
   "minLength": 2
  },
  "radius_km": {
   "type": "number",
   "default": 100,
   "maximum": 500,
   "minimum": 5
  },
  "years_back": {
   "type": "integer",
   "default": 30,
   "maximum": 100,
   "minimum": 3
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/natur-halowerk-seasonal-species-profile-3ff373dc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from natur.halowerk.com](https://www.zero.xyz/host/natur.halowerk.com/llms.txt)