Add source-dated USDA P&S counterparty evidence to your livestock workflow.
Built for livestock marketplaces, auction platforms, procurement and vendor-onboarding systems, feedlot or operations software, compliance teams, and automation. Start with the existing paid API or batch interface; no custom integration is required to test the workflow.
Run a check — $0.05API & MCP detailsWhere it can fit
Integration shape
Input: business name plus optional U.S. state or Canadian province. Batch input supports up to 1,000 counterparties.
Output: match status, match basis, legal/trade names, region resolution, supported bonded-record evidence, published coverage when available, suspension evidence, snapshot version, and USDA source dates.
Pricing: $0.05 per completed verification through the current Apify execution path.
Source health:
Why this is different from a generic lookup
- Source dates remain visible instead of presenting every USDA list as equally current.
- Multiple plausible matches are surfaced instead of silently choosing a fuzzy best guess.
- Required-source failures are designed to fail closed rather than return a false clean result.
- The service returns evidence for downstream review rather than inventing a proprietary risk score.
No-cost evaluation sample
Before asking your team to integrate anything, send up to 10 business-counterparty names and, when known, the U.S. state or Canadian province for each. No account credentials, payment information, or private customer data are needed.
The evaluation uses the same production verification logic and returns the same evidence structure: match_status, bonded-record match counts, current suspension matches, unresolved suspension-name matches, matched legal or trade names, match basis, region resolution, bond coverage when published, snapshot version, USDA source dates, and the standard limitation statement.
Evaluate it before integrating
Run a small single or batch test first. If the evidence fits your workflow, the same service can be called programmatically without changing the underlying verification logic.
Run an onboarding checkIntegration questions: livestock-counterparty-guard@agentmail.to