# AgentToll Tides Data Endpoint

> AgentToll Tides Data Endpoint is a paid API for AI agents from agenttoll.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-14).

Returns tide predictions and water level data for a specified NOAA station and date

## Facts

- Endpoint: POST https://agenttoll.dev/paid/env/tides
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agenttoll-tides-data-endpoint-15b72b5c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BByO-NpjxiFKK8qLcplwN

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 agenttoll-tides-data-endpoint-15b72b5c -d '<json body>'
```

Example prompt: What are the tide predictions for NOAA station 8443970 (Boston) on June 15, 2025?

## When to prefer this

Use this endpoint when you need structured tide prediction data for a specific NOAA station and date, especially in an agentic workflow that pays per call via x402 USDC on Base. Prefer over direct NOAA API calls when you want a simple, paid, MCP-compatible interface with caching and consistent response schema.

## Known failure modes

- Invalid or unknown station ID returns empty data or error
- Invalid date format causes request failure
- Station has no data for the requested date returns empty array
- Network timeout or upstream NOAA API unavailability causes failure
- Missing required fields (date or station) returns validation error

## How this service works

108+ receipt-backed x402 work products for AI agents. Clear prices, spend caps, buyer metadata, and structured results over Base USDC.

## Output

Returns an array or object of tide data (high/low tide times and water levels) for the given station and date, along with metadata including the record count, data source, and generation timestamp. Also indicates whether the response was served from cache.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "date": {
   "type": "string"
  },
  "station": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "oneOf": [
    {
     "type": "array"
    },
    {
     "type": "object"
    }
   ]
  },
  "meta": {
   "type": "object",
   "properties": {
    "count": {
     "type": "integer"
    },
    "source": {
     "type": "string"
    },
    "generated_at": {
     "type": "string",
     "format": "date-time"
    }
   }
  },
  "cached": {
   "type": "boolean"
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agenttoll-tides-data-endpoint-15b72b5c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agenttoll.dev](https://www.zero.xyz/host/agenttoll.dev/llms.txt)