Skip to content

FousThe Compliance Engine

Track your Compliance Engine reports through an API

Read your Open/Rejected Reports, Reports Ready for Payment and Deficiency Tracking in The Compliance Engine with one API call each. A workflow can check for rejected reports every morning and review the day's reports before they are charged around midnight.

Works with your own The Compliance Engine account. Fous is an independent product.

What you can build on TCE

  • Get open and rejected reports

    Build this

    Reads the Open/Rejected Reports list with Progress and Status set to ALL, including the AHJ's reason for each rejected report.

    Takes
    Progress (optional: In Process or Rejected)
    Returns
    Report number, premises, AHJ, system, service date, progress, rejection reason
  • Check Reports Ready for Payment

    Build this

    Reads the Reports Ready for Payment folder: the reports submitted to AHJs that wait for processing around midnight Central time.

    Takes
    Nothing
    Returns
    Report number, premises, AHJ, system, submitted date, new premises awaiting AHJ review
  • Get open deficiencies

    Build this

    Reads Deficiency Tracking for an AHJ or premises: each premises, its systems with open deficiencies and every deficiency as it was reported.

    Takes
    AHJ, premises name or address (optional)
    Returns
    Premises, address, AHJ, system type, deficiency, status
  • Mark a repaired deficiency as compliant

    Build this

    In Deficiency Tracking, sets a deficiency your company reported from Open to Compliant with the repair date, attaches proof and saves it for the AHJ to approve.

    Takes
    Premises, system type, deficiency, repair date, proof file
    Returns
    Premises, system type, deficiency, status, repair date

Automate TCE with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Rejected reports, every morning

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    Get the open and rejected reports from the Open/Rejected Reports list.
    Step 2
    Keep the reports in Rejected progress that were not there on the last run.
    Step 3
    Email you each one with its premises, AHJ, system and the AHJ's rejection reason.
  • Reports Ready for Payment, before midnight

    Build this
    Starts
    Every weekday at 17:00 Central time
    Step 1
    Read the Reports Ready for Payment folder.
    Step 2
    Keep reports submitted before today, premises marked ** and reports that look like duplicates.
    Step 3
    Stop when there are none, otherwise email you the list before the midnight charge.
  • New open deficiencies per AHJ, every week

    Build this
    Starts
    Every Monday at 8:00
    Step 1
    For each AHJ you name, get the open deficiencies from Deficiency Tracking.
    Step 2
    Keep the deficiencies that were not there on the last run.
    Step 3
    Post premises, address, system type and deficiency to your webhook, such as your service CRM.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get open and rejected reports” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "tce-pwa.thecomplianceengine.com/get_open_rejected_reports",
    "input": {
      "progress": "Rejected"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "reports": [
      {
        "report_number": "RN-4418207",
        "premises": "Northwind Distribution Center",
        "ahj": "Acme County Fire District",
        "system": "Fire Sprinkler",
        "service_date": "2026-11-03",
        "progress": "Rejected",
        "rejection_reason": "Attached report is for a different address. Please attach the inspection for this premises."
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

TCE’s own options

BRYCER documents no public API for The Compliance Engine. Its own ways to get reports in are TCE's screens and Compliance Sync, a $5-per-report service where BRYCER's staff enter the reports you email or send from BuildingReports. Reading your reports, payments and deficiencies back out is done on TCE's screens.

OptionWhat it coversWhat it takes
Compliance Sync by emailEach branch gets its own email address for completed reports. BRYCER's staff enter inspection, deficiency and repair reports into TCE.$5 per report submitted. Most reports are entered within 2 to 3 business days, guaranteed within 5.
Compliance Sync software integrationSends reports to Compliance Sync straight from your field inspection software. BuildingReports is the first supported integration.BuildingReports, and $5 per report submitted.
TCE by handEnter Report, Open/Rejected Reports, Ready for Payment, Deficiency Tracking and the AHJs list with each AHJ's fees.A company account with users per person. The AHJ's submittal fee per report, charged to your company's credit card.

Read on November 12, 2026: BRYCER launches Compliance Sync, How to Submit Inspection/Service Reports to the AHJ, How to Find AHJ Information.

Signing in to TCE

TCE signs you in with a username, which is your email address, and a password. A company's users are Company Users or Company Administrators, and administrators can also view financial information. With Fous you sign in once through TCE's own sign-in with your own user: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Reports are charged around midnight
Reports submitted during the day wait in Reports Ready for Payment and are processed around midnight Central time. A duplicate still in that folder at midnight is charged as well.
Old reports in Ready for Payment mean a hold
A report from an earlier day still in the folder may mean your company's credit card is not valid, or that its premises, marked **, has not been reviewed by the AHJ yet.
Each AHJ sets its own fee
The submittal fee per report and the systems an AHJ tracks are under the AHJs tab, which lists the AHJs in the service area set in My Service Provider.
Deficiencies go out exactly as typed
Deficiencies appear as entered on the report to the Fire Marshal and on the notice to the premises. Only the company that reported them can mark them Compliant; others submit a repair report.

More in Government: US courts, records, permits and licensing

Other industries: ApplyOnline, E-Verify, COMMBUYS, LaTAP, EAMS (Washington ESD), Würth Online-Shop.

Frequently asked questions

No public API is documented. BRYCER offers Compliance Sync, where its staff enter the reports you email for $5 per report, with BuildingReports as the first software integration. Everything else, including rejected reports and open deficiencies, is read on TCE's own screens.

It depends on the AHJ. Each AHJ's submittal fee per report is shown under the AHJs tab, next to the systems it tracks, and it is charged to your company's credit card when the day's reports are processed around midnight Central time.

The AHJ gives a reason. Open the Open/Rejected Reports icon, find the report with Rejected in the Progress column and hover over the word Rejected to read it. Correct the report with Edit and submit it to the AHJ again.

Yes, from some. Through Compliance Sync, BRYCER accepts reports from BuildingReports, its first supported integration, at $5 per report. Inspect Point also describes an integration that sends its reports to TCE once a building is linked to its TCE premises.

No. Fous is an independent product. You use it with your own TCE user, and a method reads and does only what that user can.

Put The Compliance Engine behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nexteFileILeFileTexasFlorida Courts E-Filing PortalApplyOnlineHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of The Compliance Engine (BRYCER). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.