Partner file feeds · Local checks · Hosted alerts
Run one local check after your existing SFTP, S3, or cron download. Agentsor alerts if the expected CSV or Parquet receipt misses its rolling cadence plus grace, cannot be read, is stale, violates the configured schema, or falls outside volume limits. Rows, filenames, paths, and transfer credentials stay in your environment.
Agentsor is not a file-transfer service; it runs after your existing pickup or export. Early access does not guarantee uptime, error detection, or downstream outcomes. A passing result proves only the local checks that ran.
After pickupKeep the downloader you already operate
No file uploadFiles and transfer access stay local
Contract-awareCheck more than process availability
How it works
Your existing job still collects the partner feed. The local verifier checks the completed file, and Agentsor watches for the next authenticated receipt.
Continue using your customer-owned SFTP, S3, managed-transfer, or export job. It must exit nonzero on failure and expose only a completed file to the next step.
Choose CSV or Parquet, required columns and compatible types, row and byte bounds, optional event-time freshness, and the expected cadence.
The MIT-licensed CLI reads the completed file where it landed, returns a typed result, and submits a bounded receipt authenticated to your monitor.
A rolling deadline starts at activation and advances after each accepted receipt. It catches silence only after the selected cadence and displayed fixed grace. Transition email distinguishes missed, failed, and inconclusive runs; exact reason codes remain in local CLI output.
Data boundary
The verifier is designed so rows and values stay where the job runs. The fr1_ machine-reporting token selects the server-side monitor; the hosted service stores the fixed receipt, detects a missing receipt, and suppresses an exact duplicate submission. A separate fm1_ management token can permanently close the monitor without gaining reporting or data-deletion authority. There is no customer dashboard in free early access.
Receipt 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.
Fit boundary
Agentsor combines local CSV/Parquet contract checks with rolling missed-receipt detection. It is not a replacement for every transfer, heartbeat, or data-observability tool.
Good fit
A scheduled raw CSV or Parquet file lands in your environment, rows must stay local, and you want schema, freshness, volume, and silence evidence together.
Use a heartbeat instead
If command exit status and a missed ping fully describe success, keep your existing cron, transfer monitor, Healthchecks, Cronitor, or equivalent.
Use a data platform instead
Use dbt, Soda, or a supported warehouse-observability platform for value/anomaly tests, managed lineage, dashboards, long history, or 24/7 SLA support. Agentsor does not provide those today.
Initial contract checks
Define the evidence your partner feed must satisfy. Unknown or unobservable evidence is marked inconclusive instead of being presented as success.
Detect silence after the selected interval plus its displayed fixed grace. This is not a wall-clock partner SLA or scheduled time-of-day check.
Parse CSV structure or Parquet metadata locally and fail closed on malformed or unsupported input.
Compare the locally observed CSV or Parquet fields and compatible types with the explicit contract you configured.
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 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 on Linux or macOS is required; Windows is not supported in this release. Version 0.2.5 requires the input path passed to check or report to directly name the completed regular CSV or Parquet file; final-component symbolic links are not supported. After format validation passes, the local check reports one as file_unreadable. If the producer stages a temporary file, create it in the final path's directory, close it completely, and publish the final name with a same-filesystem atomic rename; do not use a cross-filesystem move or switch a symlink. Finalize and successfully test the contract before creating a monitor. The reporter must resolve agentsor.ai and connect directly over HTTPS to port 443; it ignores ambient proxy variables, so confirm egress before confirming activation. The first accepted hosted report pins the monitor to that contract fingerprint; later contract changes are rejected, and free early access has no self-serve contract reset.
python3 --version
mkdir -p ~/.local/share/agentsor-file
install -d -m 700 ~/.config/agentsor
python3 -m venv ~/.local/share/agentsor-file/venv
~/.local/share/agentsor-file/venv/bin/python -m pip install agentsor-file==0.2.5
~/.local/share/agentsor-file/venv/bin/agentsor-file init \
--format csv \
--contract "$HOME/.config/agentsor/partner-feed.toml" \
--fingerprint-key-file "$HOME/.config/agentsor/partner-feed.key"
${EDITOR:-vi} "$HOME/.config/agentsor/partner-feed.toml"
~/.local/share/agentsor-file/venv/bin/agentsor-file check \
"YOUR_ABSOLUTE_DOWNLOADED_FEED.csv" \
--contract "$HOME/.config/agentsor/partner-feed.toml" \
--fingerprint-key-file "$HOME/.config/agentsor/partner-feed.key"Free now · one planned paid offer
No checkout, automatic trial, renewal, or charge is currently available. The Pro price below is a validation target, not a purchasable plan.
Available now · free early access
Each verified request creates one monitor tied to one operational-email recipient. Submitted redacted run receipts have seven-day retention, and a separately issued management token permits permanent self-service monitor closure.
Planned · not available
File Contracts Pro is planned at $29 USD per month for up to 10 monitored feeds. The planned bundle includes 30-day redacted run history, two alert recipients, and self-serve ingest-token rotation, monitor pause, and monitor deletion. It would be month to month and cancellable before the next renewal. It does not currently include a customer dashboard or paid support SLA. No checkout, paid entitlement, or charge is available today.
Current boundary
After activating a free monitor, you may make one non-binding Pro early-access request. It creates no order, trial, charge, subscription, or marketing permission.
Create a free monitor
After the local check succeeds with the contract you intend to keep, use a business email you control. Give the feed monitor a non-sensitive label and select its expected cadence. We send one expiring verification link. Opening it only loads a confirmation page; selecting Activate monitor creates the monitor, separately shows its fr1_ machine-reporting token and fm1_ management token once, and starts the selected cadence-plus-grace deadline. The management token can permanently close the monitor but does not delete account data.
Before confirming activation, verify that the reporting host can resolve agentsor.ai and connect directly to https://agentsor.ai:443. The reporter ignores ambient proxy variables.
Do not enter a customer name, filename, storage path, hostname, personal data, credential, or confidential project identifier.