exascale.build
api ↗Connect

Docs → API reference

Space Satellite Notices (FCC weekly satellite public notices) API v1

Generated from core.contract.describe_space_satellite_notices_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
date_filed date filed (as printed) date_filed fcc_notice_printed_date_filed The "Date filed" this notice prints for the filing. The same filing can print a different date in different notices (e.g. an acceptance notice and a later action notice); each listing keeps its own. A date, not a number; filter with date_filed_from / date_filed_to.
action_date date of action (as printed) action_date fcc_notice_printed_action_date On an Actions Taken notice, the date printed for "Date of Action". Null when the notice prints none; the notice states that its release date is then the effective date. Always null on Accepted for Filing notices. A date, not a number; filter with action_date_from / action_date_to.
applicant applicant (as printed) applicant fcc_notice_printed_applicant The applicant or licensee name exactly as this notice prints it (a name wrapped across two lines is rejoined). The printed name can differ over time: filing SAT-MOD-20240508-00096 is Maxar License Inc. in the IBFS docket and Vantor License Inc. in 2026 notices. Null when the notice prints no name. Matched case-insensitively. A label, not a number; group by applicant for per-operator counts.
informative listed as informative informative fcc_notice_informative_section True when the notice lists the filing under its INFORMATIVE: heading rather than as an action or acceptance of that week. A flag; filter informative=false to exclude informative listings.
entry_text entry text (as printed) entry_text fcc_notice_entry_text_verbatim Every line the notice prints for this filing, verbatim (page footers removed), including the FCC's description of the request or action and any columns the notice does not label. 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 filing listings in the FCC Space Bureau's weekly satellite public notices in the current result scope. A filing listed in several notices counts once per listing — never a count of distinct filings or 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

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

Checked Examples

Agent question Request params Checked output
What actions did the FCC take on satellite filings since the ICFS cutover? {"group_by": ["action"], "notice_kind": "Actions Taken"} satellite-notice-actions-by-type.json
Which of one operator's satellite filings has the FCC listed in its weekly notices since mid-2025? {"applicant": "Space Exploration Holdings, LLC", "include_records": true, "limit": 5} satellite-notices-by-applicant.json
Show one satellite application from an FCC Accepted for Filing notice with its citation. {"file_number": "SAT-RPL-20260727-00312", "include_records": true, "limit": 1} satellite-notice-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_notices.
  2. Call describe_space_satellite_notices_v1 to inspect valid filters, groupings, metrics, and citation fields.
  3. Call query_space_satellite_notices_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 ↗