FDC3
An open standard for interoperability between financial desktop applications — shared context objects, intents, an app directory, and a channel model, so that selecting an instrument in one application propagates to others.
Why it matters for autonomous finance
FDC3 solved, for human desktops, the problem agent protocols are now solving for machines: how independently built applications share meaning without a central owner. Its context data specification is a working financial ontology that already has industry adoption — which makes it a far better starting point for agent context modeling than inventing a schema, and almost nobody in the agent space has looked at it.
What it does not cover
Desktop-scoped and human-mediated by design. It assumes a person is the integration point between applications, and carries no authority, audit or accountability semantics. Useful as a vocabulary; not a governance standard.
No provisions for autonomous action, oversight, or accountability. Every entry in this register carries this section. A standard read past its scope is worse than no standard, because it produces confidence without coverage.
Read it
Other standards in the register
Source and provenance
- Issuing body
- FINOS (Fintech Open Source Foundation, Linux Foundation)
- Canonical source
- https://fdc3.finos.org/
- Version
- Not recorded
- Last verified
- Not recorded
- Content held
- This corpus holds no copy of the source's text; the record is a citation, and no content digest can be given.
- Third-party material
- The framework, its text, identifiers and version belong to its issuing body (FINOS (Fintech Open Source Foundation, Linux Foundation)). This corpus cites it, reproduces none of its text, and grants no rights in it.
- This corpus's work
- The summary, why-it-matters, caveat, gap statement and MARQUE mapping on this page are this corpus's own editorial work, under the terms at https://qistrust.com/license/.
No dated claim about this source is recorded in the verification register; its locator and description were not re-verified against the source for this record. The same record, field for field, is in api/provenance.json (qis-provenance-1) and in this page's structured data.