Build with Dunvale cited logistics data.

The fastest path is the public API and discovery files: no authentication, ideal for evaluating Dunvale source coverage, API-readable metadata, and pricing readiness.

curl https://api.dunvale.com/health
curl https://api.dunvale.com/public/snapshot
curl 'https://api.dunvale.com/public/reports?type=morning_briefing&limit=5'

For programmatic access to published wait rows, source status, evidence retrieval, exports, entitled report surfaces, and private delivery, use a scoped API key. Standard agent evidence and map packets are priced at $0.0059 when metered access is enabled. Check sourceClaimAudit before source-level currentness or quality claims; raw-current, non-live, stale, no-row, planned, future, parser-policy-missing, parser-lagged, degraded-run, and embedding-backlog rows stay context-only unless returned packet evidence proves exact claim use.

curl https://api.dunvale.com/v1/border/laredo_world_trade/current \
  -H "Authorization: Bearer dnv_live_..."

Authenticated endpoints require a bearer token in the Authorization header. Keys are stored securely, scoped to a tier and account, and rotated by request.

Authorization: Bearer dnv_live_abc123...

Public endpoints under /public/* need no auth and are rate-limited per IP. The /health and /public/about endpoints are intentionally unrestricted so monitoring tools and AI agents can introspect the service freely.

Dunvale supports long-lived account keys for customers and partner systems, plus transaction-scoped keys for metered one-off API sessions, exports, and machine settlement flows. Both use the same bearer header, so clients do not need separate integration code.

# account key
Authorization: Bearer dnv_live_partner_...

# transaction-scoped key
Authorization: Bearer dnv_txn_one-shot-map_...

Rate limit headers are returned on every response: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset.

Dunvale separates public discovery from metered operational access. Public pages and free feeds are built for evaluation, search, and AI discovery. Metered access starts with evidence transactions and expands into account scopes, private RSS, authenticated API access, structured data delivery, webhooks, historical licensing, and custom agent access.

Public endpoints power the website and the email/RSS distribution. They're free to call, CORS-enabled for dunvale.com and any subdomain, and require no authentication.

The authenticated /v1 namespace is the primary integration surface for autonomous agents, TMS systems, customer portals, alerting pipelines, and private copilots.

Example response:

{
  "portId": "laredo_world_trade",
  "updatedAt": "2026-04-12T10:15:40Z",
  "lanes": [
    {
      "laneType": "commercial_fast",
      "waitMinutes": 25,
      "lanesOpen": 6,
      "capturedAt": "2026-04-12T10:15:00Z",
      "source": "cbp_bwt"
    },
    {
      "laneType": "commercial_standard",
      "waitMinutes": 90,
      "lanesOpen": 4,
      "capturedAt": "2026-04-12T10:15:00Z",
      "source": "cbp_bwt"
    }
  ]
}

The /v1/map namespace powers the interactive /map surface for agent snapshots and account-scoped exceptions. It combines source-fact-ready border waits, road events, NWS alerts, and weather context with raw-current aircraft, river-gauge, and vessel map context, plus NEXRAD radar, cloud formations, rail, sea chart overlays, and GPS interference on one WebGL canvas. Every signal is addressable via these three endpoints so agents and dashboards can consume the same state the frontend renders without treating raw map rows as claim-bearing evidence.

Snapshot example:

curl https://api.dunvale.com/v1/map/snapshot \
  -H "Authorization: Bearer YOUR_API_KEY" | jq '{
  generatedAt,
  viewport,
  ports:    (.ports | length),
  aircraft: (.aircraft | length),
  vessels:  .stats.vesselCount,
  vesselClusters: (.vesselClusters | length),
  roadEvents: .stats.trafficEventCount,
  roadClusters: (.trafficEventClusters | length),
  alerts:   (.alerts | length),
  gauges:   (.gauges | length)
}'
# =>
# {
#   "generatedAt": "2026-04-13T18:42:00Z",
#   "viewport": { "bbox": null, "zoom": null, "denseLayerMode": "clustered" },
#   "ports":    82,
#   "aircraft": 312,
#   "vessels":  2070,
#   "vesselClusters": 118,
#   "roadEvents": 1629,
#   "roadClusters": 94,
#   "alerts":   17,
#   "gauges":   15
# }

Viewport-filtered dense layer example:

curl "https://api.dunvale.com/v1/map/snapshot?bbox=-123,37,-121,39&zoom=9" \
  -H "Authorization: Bearer YOUR_API_KEY" | jq '{
  mode: .viewport.denseLayerMode,
  vessels: (.vessels | length),
  roadEvents: (.trafficEvents | length)
}'

Port drilldown example:

curl https://api.dunvale.com/v1/map/port/laredo_world_trade/detail \
  -H "Authorization: Bearer YOUR_API_KEY"
# =>
# {
#   "portId": "laredo_world_trade",
#   "sparkline":   [ { "hour": "...", "avgWait": 42, "sampleCount": 8 }, ... ],
#   "anomalies":   [ { "laneType": "commercial", "severity": "elevated", "zscore": 2.1, ... } ],
#   "predictions": [ { "horizonHours": 2, "predictedWait": 55, "confidenceLow": 40, "confidenceHigh": 70, ... } ],
#   "alerts":      [ { "alertId": "...", "event": "Wind Advisory", "severity": "Moderate", ... } ]
# }

Ask the AI assistant:

curl -X POST https://api.dunvale.com/v1/map/ask \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "question": "Which crossings have the worst waits right now, and is weather a factor?",
    "context": { "counts": { "ports": 82, "alerts": 17 }, "topEvents": [...] }
  }'
# => { "answer": "Three southwest crossings are currently elevated..." }

Dunvale publishes an aggregate reports feed, a daily briefings feed, and one RSS feed per report type. Free reports stay public; entitled subscribers can use feed tokens to unlock report types and scopes.

https://api.dunvale.com/public/reports/feed.xml
https://api.dunvale.com/public/briefings/feed.xml
https://api.dunvale.com/public/feeds
https://api.dunvale.com/public/reports/morning_briefing/feed.xml
https://api.dunvale.com/public/reports/macro_weekly/feed.xml
https://api.dunvale.com/public/reports/sector_report/feed.xml
https://api.dunvale.com/public/reports/regional/feed.xml

# entitled subscriber example
https://api.dunvale.com/public/reports/feed.xml?token=dnv_feed_...

Every report page on dunvale.com embeds schema.org/Article JSON-LD with linked Dataset and DataFeed nodes. Search engines and AI crawlers can map a Dunvale report to its underlying data lineage without scraping. The /public/about endpoint exposes the same product manifest in machine-readable form.

Dunvale exposes tool-shaped REST resources, manifests, OpenAPI, RSS, JSON-LD, account-generated keys, demo-key policy discovery, and transaction-key flows for agent workflows today. x402 should become the low-friction settlement rail for standard $0.0059 metered resources. Models should query cited reports, published border wait context, and source status rather than scrape UI text. See the agents page for the full integration story.