Finance
Supplier Requirements Verifier
Supplier Requirements Verifier
Start with Requirement document + offers or catalog URLs. Uploaded files describe a snapshot. Supply new files for new private facts; prior cases remain available for comparison. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkEvidence reports
FactoriesStart with your sources
IdleIllustrative runReading watched pages
Material: rate, price, or term changes above 2%, supplier outages, new regulation
StripeRead only
NotionFinance digests
Related solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Supplier Requirements Verifier
Pick an example, connect your tools, and review the first run.
Set up the Supplier Requirements Verifier agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Compare requirements with available specifications, investigate ambiguity, and maintain a verified gap matrix as offers or catalogs change.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `supplier-requirements-verifier` is listed, instantiate it with `--path.slug supplier-requirements-verifier` and start the run; otherwise create a project from this template at /new?template=supplier-requirements-verifier&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.