Local verification · Hosted deadlines and alerts
Agentsor File Contracts checks CSV and Parquet files where they already live, then reports a small result envelope. Catch a missing delivery, unreadable file, stale event time, row-count breach, or schema change without sending us the file.
Early-access product. No customer result, uptime, error-detection, or downstream business outcome is guaranteed. A passing result proves only the checks that your local verifier actually performed.
LocalFiles are checked in your environment
ExplicitYou define what passing means
QuietAlerts fire on meaningful transitions
How it works
The verifier runs beside your existing export or import. Agentsor watches for the next authenticated receipt and alerts when the configured contract or schedule fails.
Choose CSV or Parquet, required columns and compatible types, row and byte bounds, optional event-time freshness, and the expected run cadence.
The MIT-licensed CLI reads the file in your environment and returns passed, failed, or inconclusive with typed check codes.
An ingest token selects the server-side monitor and authenticates a bounded JSON envelope containing the result, timestamps, observed row/byte counts, fixed check codes, and project-keyed contract/schema/output fingerprints.
The hosted deadline catches a missing run. Typed transition email distinguishes a missed deadline, failed run, or inconclusive run; exact check and reason details remain in local CLI output.
Data boundary
The verifier is designed so rows and values stay where the job runs. The bearer token selects the server-side monitor; the hosted service stores the fixed receipt, detects a missing receipt, and suppresses an exact duplicate submission. There is no customer dashboard in free early access.
Read the full early-access privacy noticeReceipt may contain
Envelope version, run identifier, start and finish time, overall status, file format, observed row/byte counts, fixed check and reason codes, and project-keyed contract/schema/output HMAC-SHA256 fingerprints.
Receipt must not contain
Rows, cell values, samples, filenames, filesystem paths, query text/results, bucket names, hostnames, storage credentials, personal data, customer records, or arbitrary notes.
Initial contract checks
Each check is explicit and independently visible. Unknown or unobservable evidence is marked inconclusive instead of being presented as success.
Detect an expected receipt that never arrives or arrives after its configured grace window.
Parse CSV structure or Parquet metadata locally and fail closed on malformed or unsupported input.
Compare required columns and compatible types, with a stable fingerprint to expose unreviewed change.
Evaluate configured event-time freshness plus row and byte bounds without transmitting record contents.
The server accepts an exact replay of one retained run identifier and envelope without creating a second run. Each new CLI invocation creates a new run identifier.
Retain redacted receipts for seven days and send typed email when an incident opens or resolves. There is no customer-visible history screen.
Local quickstart
The MIT-licensed CLI source runs without an account for local checks. It creates a private project fingerprint key, an editable TOML contract, and one fixed JSON result. No file, path, column name, or value is sent.
Python 3.11 or newer is required. Review the generated contract before relying on a result.
python -m pip install agentsor-file
agentsor-file init \
--format parquet \
--contract file-contract.toml \
--fingerprint-key-file .agentsor-file.key
agentsor-file check YOUR_FILE.parquet \
--contract file-contract.toml \
--fingerprint-key-file .agentsor-file.keyFree early-access boundary
No paid plan, checkout, automatic trial, renewal, or charge is currently available. Pricing and limits will be published only after billing, cancellation, and entitlement enforcement are implemented and verified.
Available in source
Each verified request creates one monitor tied to one operational-email recipient. Submitted redacted run receipts have seven-day retention.
Not available
There is no customer-visible receipt history, self-serve account console, paid entitlement, or multi-recipient alerting in this early-access release.
Manual support
Token revocation, alert-stop, closure, and data-rights requests are handled manually after authority is verified. In-place token rotation is not available.
Create a free monitor
Use a business email you control. Give the monitor a non-sensitive label and select the expected cadence. We send one expiring verification link; the raw ingest token is shown once after verification.
Do not enter a customer name, filename, storage path, hostname, personal data, credential, or confidential project identifier.