exascale.build
api ↗Connect

Docs → API reference

Space Satellite Filings (FCC satellite licensing docket) API v1

Generated from core.contract.describe_space_satellite_filings_v1() and checked fixture-backed examples. Do not hand-edit the example JSON files.

Capability

What It Can Answer

Represented Facts

Data Point Contract

Does not answer:

REST Surface

MCP Surface

Local MCP Setup

Some MCP clients launch servers from the user's home directory or ignore a configured cwd. Use uv run --directory so the server always starts from the repository project.

{
  "command": "uv",
  "args": [
    "run",
    "--directory",
    "/absolute/path/to/OSINT",
    "python",
    "-m",
    "core.mcp_server"
  ]
}

Leave EXASCALE_PARQUET_BASE / EXASCALE_RAW_BASE unset: the one server hosts every data point's tools, and with no override it resolves each block's promoted snapshots and raw archive from the repository layout. Setting either env var points ALL tools at one directory — a per-block path breaks every other block's tools. They exist only for single-source sandboxes and tests.

Request Schema

Filters:

Input field semantics:

Field Answer Label Source Field Semantics Definition Counting Definition
report_period_source event-period provenance report_period_source pd064_event_period_provenance 'date_filed' for every filing whose date_filed cell parses; 'file_number' on the one observed source-typo row (a year-4017 date_filed), where the event period comes from the FCC's receipt-date stamp embedded in the file number itself (PD-064). Served on DETAIL records. A provenance label, not a number — it qualifies report_period; never aggregated.
applicant_state applicant address state applicant_state fcc_ibfs_address_state_verbatim The APPLICANT's mailing address state as the FCC recorded it — never the satellite's location (satellites are not in states). The canonical state anchor carries the USPS-validated value; blanks (the FCC's shape for foreign applicants) are null. An address label, not a number; group by state for the validated anchor.
description FCC filing description description fcc_ibfs_filing_description_verbatim The FCC's own plain-English description of the filing, verbatim (e.g. the mission or request text the applicant filed). Served on DETAIL records. Free text, never aggregated.

Group by:

Date range parameters:

Controls:

Ranking (how order_by / top_n / order join — order_by ranks groups by a metric, never a group_by dimension; top_n needs both a group_by and an order_by):

{
  "no_ranking": "Omit order_by and top_n to return all groups in group-key order.",
  "order": {
    "default": "desc",
    "valid_values": [
      "desc",
      "asc"
    ]
  },
  "order_by": {
    "accepts": "one of output.metrics",
    "note": "Ranks the groups by a metric (a measure). Not a group_by dimension \u2014 rows already come back grouped by each group_by field.",
    "requires": [
      "group_by"
    ],
    "valid_values": [
      "source_record_count"
    ]
  },
  "top_n": {
    "note": "Keeps the top N groups by order_by; the rest fold into one (other) remainder (additive metrics sum into it, non-additive ones are nulled) so the result still reconciles to summary.totals.",
    "requires": [
      "group_by",
      "order_by"
    ],
    "type": "positive integer"
  }
}

Output Schema

Aggregate metrics:

Metric groups:

{
  "records": [
    "source_record_count"
  ]
}

Response summary fields:

Accepted fact policy:

Metric metadata:

Metric Category Unit Aggregation Additive Across Groups Authoritative Total Definition
source_record_count records count count source records true summary.totals.source_record_count Count of FCC space-station (SAT) docket filings in the current result scope. A filing is an authorization EVENT — never a satellite count (one NGSO grant can cover thousands of satellites).

Rollup rules:

Detail record fields returned when include_records is true:

Row-level citation fields:

Aggregate citation fields:

Codebooks

Field Coverage Codes Examples Note
app_type_code every SAT application type the FCC defines 12 LOA = Launch and Operating Authority, STA = Special Temporary Authority, MOD = Modification, AMD = Amendment, T/C = Transfer of Control Verbatim FCC codes; the served app_type_text is the FCC's own decode from the same capture vintage. LOA (Launch and Operating Authority) is a new satellite system's operating application; STA is temporary authority; MOD modifies a grant.
status_code the FCC's full filing-status vocabulary 8 ATPN = Action Taken Public Notice, A/C = Action Complete, AFPN = Accepted for Filing Public Notice, UNBLK = Unblocked, FPRVD = Filed - payment received Verbatim FCC codes; the served status_text is the FCC's own decode from the same capture vintage. The dominant terminal statuses on the SAT docket are A/C (Action Complete) and ATPN (Action Taken Public Notice); AFPN (Accepted for Filing Public Notice) marks a filing in process.

The complete machine-readable codebooks are included in capability-schema.json.

Checked Examples

Agent question Request params Checked output
What is one operator's FCC satellite filing mix (new systems, modifications, temporary authorities)? {"applicant_name": "Space Exploration Holdings, LLC", "group_by": ["app_type_code"]} satellite-filings-by-applicant.json
Who filed the most FCC space-station applications since 2020? {"group_by": ["applicant_name"], "order_by": "source_record_count", "report_period_from": "2020-01-01", "top_n": 10} most-active-satellite-filers.json
Show a specific FCC satellite filing with its full record and citation. {"file_number": "SATLOA2025061800149", "include_records": true, "limit": 1} satellite-filings-detail-with-citation.json
Verify the raw workbook row behind a returned citation citations[ref].verify (aggregate) or records[0].citation (detail) source-row-evidence.json
Dogfood the tool sequence as an agent list -> describe -> query -> evidence agent-dogfood-transcript.json

The checked schema output is capability-schema.json.

Agent Workflow

  1. Call list_capabilities_v1 and select space.satellite_filings.
  2. Call describe_space_satellite_filings_v1 to inspect valid filters, groupings, metrics, and citation fields.
  3. Call query_space_satellite_filings_v1 with bounded JSON params.
  4. If the answer needs proof, pass a returned row-level citation object to get_source_evidence_v1.
  5. Answer with the resolved as_of and relevant citations. Present returned metrics as authoritative for their declared source, snapshot, grain, and aggregation.
Generated from the tested API contract. Compare with the live capability map ↗