Airport operational status and runway configurations

Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.

Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.

{
  "schema": "sourcefinch/source@1",
  "name": "Airport operational status and runway configurations",
  "url": "https://nasstatus.faa.gov/api/airport-events",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "$[*]",
    "fields": {
      "latitude": "latitude",
      "longitude": "longitude",
      "airport_code": "airportId",
      "airport_name": "airportLongName",
      "arrival_rate": "airportConfig.arrivalRate",
      "ground_stop_id": "groundStop.id",
      "arrival_runways": "airportConfig.arrivalRunwayConfig",
      "ground_delay_id": "groundDelay.id",
      "departure_runways": "airportConfig.departureRunwayConfig",
      "configuration_timestamp": "airportConfig.sourceTimeStamp"
    },
    "required": [
      "airport_code"
    ],
    "types": {
      "airport_code": "string",
      "airport_name": "string",
      "arrival_rate": "number",
      "arrival_runways": "string",
      "configuration_timestamp": "string",
      "departure_runways": "string",
      "ground_delay_id": "string",
      "ground_stop_id": "string",
      "latitude": "number",
      "longitude": "number"
    }
  },
  "schedule": "daily",
  "key_field": "airport_code"
}

The request body used by the API, CLI and SDK examples.

{
  "name": "Airport operational status and runway configurations",
  "url": "https://nasstatus.faa.gov/api/airport-events",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "$[*]",
    "fields": {
      "latitude": "latitude",
      "longitude": "longitude",
      "airport_code": "airportId",
      "airport_name": "airportLongName",
      "arrival_rate": "airportConfig.arrivalRate",
      "ground_stop_id": "groundStop.id",
      "arrival_runways": "airportConfig.arrivalRunwayConfig",
      "ground_delay_id": "groundDelay.id",
      "departure_runways": "airportConfig.departureRunwayConfig",
      "configuration_timestamp": "airportConfig.sourceTimeStamp"
    },
    "required": [
      "airport_code"
    ],
    "types": {
      "latitude": "number",
      "longitude": "number",
      "airport_code": "string",
      "airport_name": "string",
      "arrival_rate": "number",
      "ground_stop_id": "string",
      "arrival_runways": "string",
      "ground_delay_id": "string",
      "departure_runways": "string",
      "configuration_timestamp": "string"
    }
  },
  "key_field": "airport_code",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "faa-airport-status",
    "version_id": "58f08233-4791-4580-9d32-eccc5cbd8b44"
  }
}

Create an API key under Console → API keys. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/faa-airport-status -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get faa-airport-status --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

The SDK is not on npm yet; see /docs/sdk.

import { SourceFinch } from "@sourcefinch/sdk";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("faa-airport-status");
const source = await sf.sources.create({
  catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Airport operational status and runway configurations: get_catalog_source faa-airport-status,
then create_source with its create_source_args (dry run first), then run_source."