Dunvale
Logistics Data API

Logistics data your product can use,
without rebuilding every source.

Give your software current border waits, lane details, weather, source dates, reports, and map context. Dunvale handles source connections and data preparation so your team can focus on useful customer features.

Explore API access →Read the API docs
Generated logistics API control-room scene with source and map panels

Before you connect

See coverage, update timing, price, and source links before your software makes a request.

Connection option

Pay-as-you-go API

available

status

GET /public/x402/agents/statuspublic

request

POST /public/x402/agents/request402

payment

x402 settlement headerUSDC

response

source-linked dataJSON

starting price

$0.0059 per standard request

Ready-to-use logistics data

Use prepared border, map, historical, and report information through one documented connection.

REST + exports

Flexible ways to pay

Use account access for repeat work or pay for supported requests as you need them.

usage or plan

Easy to evaluate

Review public reports, data pages, examples, and technical guides before choosing an account plan.

public examples

Clear product guide

One public product description shows available coverage, update status, and access options.

clear coverage

Updates where you work

Use reports, feeds, snapshots, and direct data access to bring the same information into team workflows.

API + RSS

Sources stay attached

Responses keep source dates and references visible so teams can review what supports each finding.

traceable
Resource catalog

Choose the request and access path that fits.

Review purpose, price, and connection method first. Open technical safeguards only when your team is ready to implement.

GET /public/agents/resourcesGET /public/border-pulse/packagesGET /public/border-pulse/sample-payloads

Agent evidence packet

agent.evidence.retrieve

$0.0059

Compact retrieval packet for one scoped freight or Border Pulse question.

Endpoint: POST /v1/evidence/request
x402: direct endpoint
Keys: account live, transaction live
Update and use details

Responses include update times, source references, and coverage notes when available.

Use current, clearly dated values for live decisions. Keep older or planned information as background.

Open full field definitions and authentication examples in API docs.

Grounded answer packet

agent.evidence.answer

$0.0059

Answer-mode packet with cited source context for keyed agents.

Endpoint: POST /v1/evidence/request
x402: account or transaction only
Keys: account live, transaction live
Update and use details

Responses include update times, source references, and coverage notes when available.

Use current, clearly dated values for live decisions. Keep older or planned information as background.

Open full field definitions and authentication examples in API docs.

Map evidence snapshot

map.snapshot

$0.0059

Scoped map payload for source-fact-ready waits/alerts plus caveated raw-current aircraft, vessels, gauges, and source health.

Endpoint: GET /v1/map/snapshot
x402: account or transaction only
Keys: account live, transaction live
Update and use details

Responses include update times, source references, and coverage notes when available.

Use current, clearly dated values for live decisions. Keep older or planned information as background.

Open full field definitions and authentication examples in API docs.

Laredo Border Pulse

border_pulse.watch_scope.laredo

$199/month

What threatens my Laredo freight today, and what evidence backs it?

Endpoint: GET /public/border-pulse/watch-scopes
x402: not applicable
Keys: account live, transaction not applicable
Update and use details

Responses include update times, source references, and coverage notes when available.

Use current, clearly dated values for live decisions. Keep older or planned information as background.

Open full field definitions and authentication examples in API docs.

API runbooks

How systems should use Dunvale data.

Start with public reports and coverage pages, then connect through a server-side account key or supported pay-as-you-go request. Keep returned source links and timestamps with customer-facing results. Use account portal for keys, usage, and delivery settings.

API clients

  1. 1Read /llms.txt and GET /public/about first to confirm source scope and product policy.
  2. 2Keep external web research separate from Dunvale API calls and citations.
  3. 3For metered packets, call /public/x402/agents/status, then /public/x402/agents/request with the x402 settlement header.

Research tools

  1. 1Use Dunvale reports or search to find relevant border and logistics context.
  2. 2Keep returned Dunvale source links and timestamps with any customer-facing answer.
  3. 3Use /public/about and /openapi.json when your workflow needs structured coverage details.

Browser workflows

  1. 1Prefer direct API URLs over screen scraping: /public/about, /public/search, /public/chat, and /openapi.json.
  2. 2If a browser workflow is required, log in at /login and use /portal/account to inspect metered usage and keys.
  3. 3Keep credentials on your server and confirm payment or account actions before sending them.

Custom integrations

  1. 1Define Dunvale as an HTTP tool: manifest, search, chat, and /v1/evidence/request for keyed evidence.
  2. 2Start every run with a capability probe, then retrieve cited evidence before presenting findings.
  3. 3Use account keys for reusable volume and transaction keys for delegated one-run access.
Data discovery

No scraping required.

Dunvale publishes coverage, update timing, access requirements, and source links in formats software can read. Public reports and examples need no key; historical data, detailed routes, and repeat access use an account. Each response identifies what can support a finding and what should stay background context.

Technical data contract

Dunvale exposes source status, cadence, coverage, evidence policy, and endpoint structure directly to crawlers and API clients. No-key public access covers reports, feeds, product details, discovery pages, and USBorderWait links. Historical analytics, detailed routing data, and repeat product access require an account. Responses label source dates, availability, and coverage limits.

Live

Available now with update times, source links, and coverage notes attached.

Scheduled

Collection is being prepared. Current customer updates are not available yet.

Planned

Future coverage. Contact Dunvale when this information matters to your product.

Open stable endpoint catalog (12)
/public/about

Machine-readable product, domain, source, status, and capability manifest.

/public/agents/resources

Priced resource catalog with freshness, evidence, x402, and account-key status.

/public/x402/agents/status

Direct USDC x402 readiness, network, and configured resource metering.

/public/border-pulse/packages

Commercial coverage options for Laredo, Detroit/Windsor, Otay Mesa, and planned crossings.

/public/border-pulse/buyer-packets/laredo

Laredo service detail with sample payload, policy-watch, and market context.

/public/border-pulse/watch-scopes

Commercial Border Pulse scope catalog for companies and API clients.

/public/border-pulse/sample-payloads

Reviewed Laredo sample replay plus San Ysidro, Otay Mesa, and Texas custom-review request shapes.

/openapi.json

Public API schema for report, search, chat, manifest, snapshot, and anomaly endpoints.

/llms.txt

Compact crawler summary on both the site and API domains.

JSON-LD

Report pages expose schema.org metadata for search and answer engines.

Metered packet transactions

x402 evidence requests and transaction-key flows for metered API access.

/public/snapshot

Latest posted border waits and selected logistics updates with timestamps and source labels.

API Quickstart

Connect systems through x402 or authenticated product surfaces.

Start with OpenAPI, RSS, JSON-LD, pay-as-you-go requests, and account keys. Standard data and map requests are $0.0059; account-generated transaction keys use authenticated /v1 endpoints. Commercial Border Pulse pages describe listed and custom coverage.

Direct x402 evidence request

GET https://api.dunvale.com/public/x402/agents/status

POST https://api.dunvale.com/public/x402/agents/request
# If the settlement header is missing, the API returns 402 with x402 requirements.
# Retry with the x402 settlement header for the 0.0059 USDC resource.

Authenticated API

{
  "base_url": "https://api.dunvale.com",
  "headers": {
    "Authorization": "Bearer dnv_live_..."
  },
  "resources": [
    "/v1/border/:portId/current",
    "/v1/evidence/request",
    "/v1/agents/request",
    "/v1/sources",
    "/v1/trade/policy/search",
    "/v1/map/snapshot"
  ]
}

Check pay-as-you-go availability before sending a metered request:

x402 status

GET https://api.dunvale.com/public/x402/agents/status
GET https://api.dunvale.com/public/billing/x402/status
# Returns availability and payment fields before a client attempts metered access.
Resource Patterns

Public and authenticated resources for entitled clients.

Each resource returns structured JSON with explicit field names, units, timestamps, and evidence context so downstream products can cite what they used.

GET /public/about

Product, source, status, and capability manifest for planning API use

public
GET /public/snapshot

Latest posted border waits and selected logistics updates with timestamps and source labels

public
POST /public/x402/agents/request

Pay-as-you-go data request for one focused logistics question

x402
POST /v1/evidence/request

Source-linked data retrieval through an account or one-time transaction key

bearer or transaction
GET /v1/border-analytics/waits/raw

Detailed historical wait rows for licensed customer use

bearer
GET /v1/border-analytics/waits/border-times-export

Historical wait export for approved connected products

bearer
GET /v1/sources

Update status, source dates, coverage limits, and data-use warnings

bearer
GET /public/reports

List public or entitled logistics reports by type and scope

public or token
GET /public/report-assets

Select reusable illustrative visuals by report type, region, border, crossing, family, or tag

public
GET /public/reports/:type/:date

Fetch report content, snippets, and structured metadata

public or token
GET /v1/map/snapshot

Map data with layer timestamps, availability, and source labels

bearer
The premise

Border logistics needs clean source facts.

A logistics manager needs a direct answer: “Which priority border lanes have current wait, weather, and source freshness evidence?”

The useful inputs are current wait rows, lane context, account scope, source freshness, and policy or weather evidence that is actually present. Scraping multiple pages for every review is brittle.

Dunvale returns structured resources instead. The REST response returns the data, current value, source timestamp, and links to supporting reports or related source context when available.

The public site stays focused on logistics facts. Historical analytics, raw rows, and routing context stay behind scoped access where source policy and usage records are clear.

Sample data request

> user: Which priority border lanes have current wait, weather, and source freshness evidence?
> client calls: GET /v1/sources
> client calls: POST /v1/evidence/request
> client calls: GET /public/reports?type=morning_briefing&limit=1
> packet summary: Sample only: returned packet says whether reviewed sample-scope evidence is claim-bearing, includes source timestamp, source health, evidence IDs, and any report context. If no packet row proves causality, answer stays at contextual overlap and cites replay evidence instead of a hard-coded wait value.

Build something with us.

We're working with logistics platforms, brokers, carriers, and trade-data teams. If you're building anything that touches North American trade, the cross-border corridor, or operational reporting — talk to us.

[email protected]API docs