Tensorust Clearinghouse · for the people who have to defend every claim

If a claim you filed or approved is wrong, you answer for it. Check it against the records first, free.

This is for the claims operations lead who will run Upper C-band intake, the compliance manager who builds a carrier's rip-and-replace claims, and the billing manager who files E-Rate invoices. The engine checks each claim against the records the program pays from (FCC lists and orders, the FAA Aircraft Registry, USAC data) and gives a pass, review or fail per rule with the reason. Run your own claims through it today. If it catches something, the kit below has the paragraph and the one-page case to take to whoever owns the budget.

Take it to your boss

• Rip-and-replace Recovery Program. For recipients with unclaimed reimbursement: every unclaimed dollar proven line by line in the format the program reads, the deadline calendar and weekly status until the claim closes. 2% of what comes back, $100,000 floor credited against it, capped at $2,000,000.
• Compliance Audit, $25,000. Your whole claims file pre-checked against every rule, with a findings memo per claim, before you file.
• Program license. A 60-day production pilot on the operator's own intake for $75,000, credited in full to year one; then $500,000 a year for one module or $950,000 for both.

Want a readiness checklist for your applications or your program? Request it and it comes back by email.

The program, from the records

Counts are computed live from the files the engine validates against: the FCC's corrected incumbent list (DA 26-1126) and an FAA Aircraft Registry snapshot (Nov 5, 2026). Part 121 status and the transport category are our flags from the registry, not FAA determinations.

What the records already show

Before a single claim arrives, joining the incumbent list to the FCC's own licensing and ownership files and the FAA registry to its deregistration history shows where a list-only check pays the wrong party or pays twice.

Built 2026-11-06 from the FCC lists (DA 26-1126, DA 25-960, DA 20-1424), ICFS licensee FRNs, LMS Form 323 ownership reports (50%+ entity voting or equity), the Tensorust ontology's screening flags and the FAA MASTER and DEREG files. Program-wide numbers: /api/clearinghouse/integrity.

The operating platform

• Intake. Single claims, batches of 2,000, or a pre-check of a whole file (up to 60,000 rows, nothing recorded) through the console or the API. Bank details are hashed on arrival; only a fingerprint and the last 4 digits are kept.
• Validation. 23 rules against the list, the FAA registry and the joins above, each with a plain reason and the record compared.
• Review. Reviewers approve, deny or hold. Approving a claim in review needs a written reason; a rejected claim cannot be approved.
• Payment ledger. Approved claims go into payment runs that re-validate every claim against the current records and stop at the fund caps. A run produces the instruction file for the disbursing bank and is marked paid with the bank's reference.
• Audit trail. Every intake, decision, run and payment is a hash-chained event; claim records carry a digest, so any edit to the ledger shows up on verification.
• Reporting. A program report for the Bureau (/clearinghouse/report, JSON and CSV): intake, decisions, payments, caps, failure and review reasons, by state, audit status.
• Access. Lock a workspace to require keys by role: admin, reviewer, payer, intake, auditor.
• Agents. MCP tools clearinghouse_validate (free, up to 100 claims a call), clearinghouse_precheck, clearinghouse_record and clearinghouse_program at shop.tensorust.com/api/mcp.

Why a claims engine

• The list is the gate. A lump sum is owed for a call sign, a site and a set of antennas on the list. A claim that names the wrong site, the wrong quantity or a registrant that is not on file should stop before payment, with the reason written down.
• Duplicates are the expensive error. 169 addresses appear under more than one Site ID for the same call sign. The engine flags them and refuses a second claim on an antenna already in the ledger.
• The owner of record is not always the operator. 6,109 turbine aircraft are registered to trust companies. For the second deadline the rebate goes to the registered owner, so an operator claim on those aircraft needs a trustee certification.
• Every decision is exportable. Each claim keeps its input, the list record it was compared against, and a pass, warn or fail for every rule. The ledger exports to CSV for audit.

The rules

A claim with any fail is rejected, any warn goes to review, all pass is accepted. Lump sum amounts: single-feed $13,722, multi-feed $21,502, small multi-beam $45,777, large multi-beam $55,985, gateway $27,305, temporary fixed $14,938, plus $53,604 per MVPD site (preliminary, DA 26-1049). Rebates per radio altimeter: helicopter $40,000, non-transport airplane $50,000, large transport and Part 121 $80,000 to upgrade or $120,000 to replace (proposed, DA 26-1076).

Try it with your proposal team or your agents

The validation engine is a free API. Send one claim or up to 100 at a time, lump sums and altimeter rebates mixed, and get back the verdict, the amount and every rule hit with its reason and the record it was compared to. No key, no account, nothing stored. Run your own test claims through it while you write the proposal, or point an agent at it.

curl -s https://shop.tensorust.com/api/clearinghouse/check \
  -H "content-type: application/json" \
  -d '{
 "claims": [
  {
   "kind": "lumpsum",
   "claimant_name": "Gray Television Licensee, LLC",
   "call_sign": "E190043",
   "site_id": "1",
   "antennas": "4.5M=1|RX2=1|RX3=1|RX4=1",
   "antenna_type": "multi",
   "mvpd_site": "no"
  },
  {
   "kind": "altimeter",
   "claimant_name": "ANDURIL INDUSTRIES INC",
   "n_number": "N435JW",
   "radio_altimeters": 1,
   "retrofit_type": "replacement",
   "trustee_certification": "no"
  }
 ]
}'

• REST. POST /api/clearinghouse/check with one claim or {"claims": [...]}. GET the same URL for the field list, all 24 rules and a ready-made example built from real list and registry records. Add ?all=1 to see the passing rules too.
• MCP. Add https://shop.tensorust.com/api/mcp as a remote server in Claude, ChatGPT or your IDE and ask: “Validate these five lump sum elections and tell me which would be rejected and why.” The tool is clearinghouse_validate. Setup.
• Limits. 30 calls a minute and 2,000 claims an hour per IP. Duplicate rules compare the claims in one call with each other; to check against claims filed earlier, use a Console workspace, which also pre-checks files of 60,000 rows.

Use it

• Single claims. Enter a lump sum election or a rebate claim and see every rule result at once.
• Batches. Upload a CSV of up to 2,000 claims; every row is validated, including duplicates within the file, and recorded.
• Your own ledger. Each visitor gets a private workspace that persists; share its link with your team. An API serves the same functions: POST /api/clearinghouse/check (free, nothing stored), POST /api/clearinghouse/validate, POST /api/clearinghouse/batch, GET /api/clearinghouse/ledger, GET /api/clearinghouse/export.
• Licensing. For the Clearinghouse operator, the payors and claims administrators: the engine, the ledger and the data joins, deployed under your controls. Most programs start with the claims lead running the free API, then the 60-day pilot. mattbusel@tensorust.com

Readiness checklist for your claims

Tell us which applications, FRNs or program you file or decide claims for. A checklist with each deadline in the chain and the rules your claims will be checked against comes back by email, free.

Built on the FCC incumbent list (DA 26-1126, Oct 15, 2026), preliminary Cost Catalog (DA 26-1049), proposed rebate amounts (DA 26-1076) and the FAA Aircraft Registry. Tensorust LLC is not affiliated with the FCC, FAA or the Upper C-band Clearinghouse.