Financial institutions have decades of third-party risk discipline and none of it was built for a counterparty that is an autonomous agent created last week. Assay supplies the missing control point.
Source: 2025 industry surveys of enterprise AI agent adoption.
Vendor due diligence, ongoing monitoring and concentration analysis all assume a counterparty that changes on the scale of quarters. Agents change on the scale of deployments, and a single vendor may expose dozens of them with different capabilities and different reliability.
The controls that exist govern the vendor relationship. They do not reach the individual agent making an individual decision, so the granularity of the control does not match the granularity of the risk.
Regulators increasingly ask who or what made a decision and on what basis. “A partner's agent, authenticated by API key” is an answer that invites the next question.
Assay moves the control point from the vendor to the agent and from onboarding to the interaction. Every agent carries an identity and a trust score earned from counterparty-verified outcomes, and every delegation can be gated on both.
The financial_services preset tunes the model for the sector's risk posture. Because capabilities score independently, an agent proven at reconciliation is not thereby trusted with settlement instructions.
Every decision produces a record: what was verified, what score it carried, which capabilities were confirmed, and what outcome followed. Controls testing gets a data source instead of a sample of screenshots.
Per agent and per capability, not per vendor. The control finally matches the shape of the risk.
A 0.5 bar for a read-only lookup and 0.75 for anything that moves money — set per call, not per relationship.
Every gate produces evidence of what was checked and what was relied upon. Useful well beyond the moment of the decision.
Revoke an agent and it fails verification everywhere at once, with no propagation window to explain to a regulator.
Set the threshold to match the risk of the action, not the vendor.
verified reflects the trust
threshold and account status. It does not fall to false because a claimed capability
is unproven — an unproven capability simply does not appear in
capabilities_confirmed. Gate on both fields.No single control satisfies a regulation, and we will not pretend otherwise. Assay provides identity, evidenced competence and durable decision records that support third-party risk and audit obligations. Mapping to a specific rule is your risk function's call.
Enterprise plans include an on-premises option along with custom trust models, SSO and SAML, and private namespaces.
For a verify call: the agent ID you are asking about and your key. For an attestation: a task type, an outcome, an optional counterparty ID and an optional hash you compute. No transaction data, no customer data.
Discovery lets you enumerate registered agents by capability and trust, so you can see how many independent providers actually clear your bar for a given capability rather than assuming the vendor count is the provider count.