Providers

Every vendor with committed integration evidence, what it serves, and the shape of the integration.

A vendor is on this list because an artifact on disk resolves: a repository carrying its name, a committed flow file naming it, or a position in a committed ordering. A vendor named only in a narrative document has no page.

What puts a vendor on this list

Each integration is four independently versioned artifacts. A connection configuration carries the transport, one per vendor endpoint, with a test per status code the endpoint can return. A language configuration carries the bidirectional field mapping. An orchestration flow composes the two, per product API and per vendor. A setup service handles credentials, with two endpoints: one to store a lender's own credentials for that vendor, one to describe the schema those credentials must satisfy.

Adding a vendor changes none of them at the product layer. The product flow resolves its partner list at run time, so a new vendor arrives by publishing a configuration bundle rather than by editing the product's API.

A vendor coverage miss is a normal result, not an alarm. An employment lookup against an employer a vendor does not cover returns a completed response carrying a code, which is what allows the next vendor in the ordering to be tried without paging anyone.