Browse the NCES EDGE Open Data catalog at data-nces.opendata.arcgis.com to identify the target feature layer (e.g., Post-Secondary Schools); each layer exposes a REST endpoint documented on the Use APIs page.
Construct a query against the ArcGIS Feature Service REST endpoint using the /query path with parameters: where=1=1, outFields=*, f=json, and resultOffset/resultRecordCount for pagination (max records per page is layer-dependent, often 1000 or 2000).
Parse the features array from the JSON response; each feature contains attributes (school name, NCES ID, address, locale code) and geometry (latitude/longitude).
Use the NCES school ID (NCESSCH field) as the join key to link EDGE geographic data with IPEDS finance or enrollment tables downloaded separately.
Filter spatially by passing a geometry parameter or use the where clause with state FIPS codes (e.g., STABR='CA') to limit results to a region.
Cache results locally; EDGE data is updated on a periodic schedule tied to NCES survey cycles, not in real time.
Known gotchas
The EDGE API uses ArcGIS REST conventions, not a bespoke NCES API; pagination requires manual offset incrementation because there is no cursor or link header.
Not all NCES datasets are exposed via the EDGE API; IPEDS finance and outcomes data must still be downloaded as bulk CSV from nces.ed.gov/ipeds, then joined to EDGE geographic records.
Locale codes and other classification fields are updated on a multi-year cycle and may lag real-world changes; document the vintage year of the dataset in your pipeline.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp