# pogo-tb.nl Dutch OV Vertrek — Public Transit Departures API

> pogo-tb.nl Dutch OV Vertrek — Public Transit Departures API is a paid API for AI agents from api.pogo-tb.nl, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Returns real-time public transit departure information for a Dutch OV stop, sourced from OVapi/NDOV open data.

## Facts

- Endpoint: GET https://api.pogo-tb.nl/v1/ov/vertrek
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pogo-tb-nl-dutch-ov-vertrek-public-transit-departures-api-48e78520
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LK3YVJb_X4lSMzSSs0zNt

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 pogo-tb-nl-dutch-ov-vertrek-public-transit-departures-api-48e78520
```

Example prompt: What buses and trams are departing from Dutch OV stop 09500 right now? Show me the next few departures.

## When to prefer this

Choose this endpoint when you need real-time Dutch public transit departure data for a specific OV stop code and want a lightweight, pay-per-call JSON API without committing to a subscription. It is ideal for AI agents operating in the Netherlands that need live departure boards, trip-planning nudges, or transit monitoring, especially when the user knows their halte code. Prefer this over full transit APIs if you only need departure lookups and want micropayment-based access via x402/USDC on Base.

## Known failure modes

- Invalid or unknown stop code returns empty or error response
- Missing required 'stop' or 'q' query parameter may result in a 400 or empty result
- Payment not completed (HTTP 402) blocks access to full JSON response
- Rate limiting or upstream OVapi outage may cause timeouts or degraded data
- Stop with no scheduled departures returns an empty vertrekken array

## How this service works

Pay-per-call Dutch RDW kenteken and BAG address APIs for AI agents. Free previews; full JSON via x402 USDC on Base.

## Output

A JSON object containing the stop code and an array of upcoming departures, each with a line number and destination. Includes an attribution string crediting OVapi/NDOV as the data source.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "stop": "09500",
   "vertrekken": [
    {
     "lijn": "54",
     "bestemming": "Centraal Station"
    }
   ]
  },
  "attribution": "Source: OVapi / NDOV (Stichting OpenGeo), Dutch public-transport open data. Third-party proxy; not affiliated with or representing NS/GVB/any transit agency."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pogo-tb-nl-dutch-ov-vertrek-public-transit-departures-api-48e78520/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.pogo-tb.nl](https://www.zero.xyz/host/api.pogo-tb.nl/llms.txt)