Skip to integration options
Report WatchBY MAYD-IT

FOR DEVELOPERS · AUTOMATIONS · AI AGENTS

A second look.
Built into your workflow.

Let an agent check a CSV in the browser, or have your existing workflow submit recurring reports. Choose the path that fits the job.

Read the API schemaPlain-text integration guide →

01 / ONE FILE · LOCAL CHECK

A tool for your browser agent.

Open the free checker in a browser that supports WebMCP. The page offers check_csv_locally with the same validation rules as the visible form.

{
  "csv": "client,orders\nExample agency,12\n",
  "columns": "client,orders",
  "minRows": 1,
  "maxRows": 100
}
  • No account, report token or payment required.
  • Inputs and results appear in the page so you can review them.
  • No server upload, saved history, schedule or email alert.
  • Availability depends on the browser and agent; ordinary form controls still work.

The site does not transmit the CSV to an AI provider. If your agent supplies or reads the file, that agent’s own data-handling rules also apply.

Open the free checker

02 / RECURRING REPORTS · AUTHORIZED API

Submit from a scheduled job.

Once the account holder sets up an eligible monitor and authorizes the workflow, its agent can submit CSVs with that report’s token. These requests do not need a browser session.

  1. Sign in with ChatGPT and choose a monitoring plan. A new unpaid workspace cannot run monitors.
  2. Create a report with its rules, timezone, deadline and grace period.
  3. Store its report token in the workflow’s protected credential facility.
  4. Test a passing file, a controlled failure and an identical retry before enabling the schedule.

Public monitoring requires confirmed live payment. Checkout and workspace setup are separate from this API. A report token cannot create accounts, buy plans, change rules or access the owner’s maintenance tools.

Read the submission contract

THE MACHINE CONTRACT

Keep the file and deadline together.

Save the original CSV, monitor ID, intended deadline and submission ID before sending. An agent can retry that saved submission; it must not invent a new report period after a timeout.

Disable redirects, use a timeout, and inspect the JSON result. HTTP 200 can mean the CSV failed its rules. A corrected file needs a new submission ID but keeps the deadline it corrects.

Task fit and product scope · OpenAPI 3.1 schema · Response and retry guide · Manual n8n / Make configuration

Importable n8n workflow and setup guide · Download workflow JSON. This manual workflow makes one attempt and classifies the receipt. It contains no report credentials, automatic schedule or downstream action. Configure it in an eligible workspace and read the guide’s verification note before using it.

{
  "method": "POST",
  "url": "https://reportwatch.mayd-it.com/api/ingest/{monitorId}",
  "headers": {
    "Authorization": "Bearer <report token from protected credentials>",
    "Content-Type": "text/csv; charset=utf-8",
    "Idempotency-Key": "<saved submission ID>",
    "X-Report-Deadline": "<intended scheduled deadline: Unix milliseconds>"
  },
  "body": "The original UTF-8 CSV bytes; not JSON or a file URL."
}

Useful evidence. Clear boundaries.

UTF-8 CSV, up to 1 MiB, 100 columns and 10,000 rows. A monitoring workspace allows 1,000 new checks per rolling 24 hours and 5,000 saved checks total, including failures. Identical retries do not consume a new check. A pass proves only that the submitted file met its configured rules—not source completeness, business accuracy or client delivery.

Server submissions can save metadata, open or resolve incidents and queue email alerts. Use only files and report credentials the account holder has authorized for that workflow. The local checker has separate privacy details; server processing follows the workspace privacy policy.