Your first resource query

A reference you can run

Waypoint Reference is a developer reference for a fictional relay API. It pairs concise guides with deterministic JSON fixtures so you can practice parsers, joins, validation, and summaries against known results.

Every station, transfer, and event is synthetic. This site serves read-only resource documents; it does not operate a relay network or accept transfer submissions. All guides and tables work without JavaScript.

Fetch the station directory

Request the resource document, then read its records array. The envelope also contains its version, field descriptions, and a JSON Schema for an individual row. Replace YOUR_HOST with this site's origin.

curl --fail --silent \
  https://YOUR_HOST/resources/datasets/waypoints.json

# In a browser on this site:
const response = await fetch('/resources/datasets/waypoints.json');
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const directory = await response.json();
console.log(directory.version, directory.records.length);
// 2026.10.3, 12

Make a small, testable query

Filter on the exact ready state, then sum capacity. Version 2026.10.3 contains seven ready stations with a combined capacity of 900 units. Standby and maintenance stations are excluded.

const ready = directory.records.filter(row => row.status === 'ready');
const capacity = ready.reduce((sum, row) => sum + row.capacity, 0);
console.log(ready.length, capacity);
// 7, 900

Search the reference

Use the existing JSON search operation to find the station fixture. Replace YOUR_HOST with this site's origin. The response contains a dataset result with slug waypoints and a URL for the same complete fixture you just inspected. Search returns resource descriptions, not matching station rows.

curl --fail-with-body --silent --show-error \
  -X POST https://YOUR_HOST/api/v1/reference/search \
  -H 'Content-Type: application/json' \
  -d '{"query":"Waypoint directory","limit":5}'

# Look for: "kind":"dataset", "slug":"waypoints"
# Its URL is /resources/datasets/waypoints.json

Choose the next step

Read API conventions for the envelope and type rules, Query recipes for joins and aggregations, or Lifecycle and ordering to reconstruct a batch from its events.

The scripted assistant can point to the reference and explain common fixture questions. Consult /privacy before sending a message, and keep credentials or confidential material out of your questions.