Two useful tools
- Assess vendor readiness: review up to 100 requirement rows against a stated date and due-soon window. Separate missing evidence, expired evidence, overdue tasks and human review.
- Draft vendor follow-up: prepare grouped requests for missing or updated evidence and separate internal-review actions. The result is a draft for you to review; it does not send messages.
A work-blocking result reflects only the operational policy you explicitly supply. The connection does not determine legal compliance, interpret insurance coverage or approve vendors.
Try the sample workflow
This example uses synthetic aliases and status rows. The buttons call the same hosted MCP endpoint available to AI clients. No private workspace record is read or changed.
Sample assessment date: October 14, 2026 · 30-day window
V-001 has an expired certificate-status row, a missing W-9 status and a license awaiting review. V-002 has an optional agreement missing. No work-blocking policy is supplied.
View synthetic input rows
{
"redacted_data": true,
"asOf": "2026-10-14",
"dueSoonDays": 30,
"required_missing_blocks_work": false,
"requirements": [
{
"rowId": "R-001",
"vendorAlias": "V-001",
"propertyAlias": "P-001",
"category": "coi",
"required": true,
"state": "manager_approved",
"expiryDate": "2026-10-01",
"dueDate": "2026-10-10"
},
{
"rowId": "R-002",
"vendorAlias": "V-001",
"propertyAlias": "P-001",
"category": "w9_status",
"required": true,
"state": "missing",
"dueDate": "2026-10-20"
},
{
"rowId": "R-003",
"vendorAlias": "V-001",
"propertyAlias": "P-002",
"category": "license",
"required": true,
"state": "review",
"expiryDate": "2027-03-01"
},
{
"rowId": "R-004",
"vendorAlias": "V-002",
"propertyAlias": "P-001",
"category": "agreement",
"required": false,
"state": "missing"
}
]
}Connect to run the synthetic example.
Connect your AI client
If your client and workspace permit remote MCP connections, add this HTTPS Streamable HTTP endpoint:
https://vendorconsole.aidiscoverygroup.com/api/mcpNo API key, subscription or private-pilot invitation is required. Client connection steps vary. This endpoint supports MCP 2026-07-28 discovery and compatible legacy clients. Public OpenAI directory publication depends on provider review; a working endpoint alone does not establish a directory listing.
Prepare safe inputs
Replace vendor and property names with aliases such as V-001 and P-001. Supply row identifiers, document categories, required or optional flags, review states, and any known expiration or task due dates. Choose the assessment date and due-soon window explicitly. Do not put sensitive information into an alias.
The connection accepts metadata only. It does not accept real documents, names, addresses, contact details, tax or bank identifiers, policy numbers, passwords or other restricted information. A W-9 can appear only as an on-file status, never as a form or tax identifier.
Understand the boundaries
Your client sends the supplied arguments to our server, which processes them for the response without intentionally storing them in the application. Your client may retain the conversation, and hosting providers may retain technical logs. Read the privacy notice for controls and retention limits.
This free workflow does not read your private workspace, upload documents, store a vendor register, send reminders, charge money or certify vendors. The invitation-only private metadata workspace is a separate experience.
For a connection or output fault, contact support with the client name, tool name and error text. Keep real vendor data and credentials out of the message.