generated: '2026-08-30' method: searched source: >- https://www.adaptigent.com/products/core-systems-integration/, https://www.adaptigent.com/products/ivory-suite/, https://www.adaptigent.com/products/data-integration/, https://www.adaptigent.com/blog/introducing-adaptive-integration-fabric-v7-2-1/, https://www.adaptigent.com/blog/gt-software-releases-ivory-suite-6-5/, https://www.adaptigent.com/news/gt-software-joins-financial-data-exchange-to-accelerate-open-banking-adoption/, https://www.adaptigent.com/solutions/open-banking-apis/ description: >- IMPORTANT READING NOTE — the subject of every entry below is the Adaptigent PRODUCT's implementation of a standard, not an Adaptigent-operated API's conformance. Adaptigent runs no public callable endpoint; it sells software that generates API contracts for its customers. So "conforms: true" here means "the platform emits or speaks this standard", which is a real and checkable claim about the product, and a different claim from "this provider's own API conforms". Each entry carries the evidence sentence it rests on. No compliance certification (SOC 2, ISO 27001, PCI DSS, HIPAA, FedRAMP) is published anywhere on the public site, so no Compliance pointer is emitted in apis.yml. subject: product-capability standards: - id: openapi conforms: true version: 2.0, 3.0 evidence: >- Product page states "Support for Open API 2.0 and 3.0 (Release 7.2)". Release 6.5 added YAML alongside JSON for reference documents and improved import/generation of OpenAPI service contracts; v7.2.1 added operation ID field mapping and refined OpenAPI import across Studio wizards and CLI tools. note: >- The OpenAPI documents produced belong to the customer's deployment. No Adaptigent-published OpenAPI exists to harvest — see well-known/ for the contract-discovery probe record. - id: soap-wsdl conforms: true evidence: >- "Build SOAP or REST API's" — the platform generates SOAP web service endpoints (and their WSDL) from mainframe COBOL/PL/I programs. No Adaptigent-hosted ?wsdl endpoint exists to save verbatim; the WSDL is emitted into the customer's environment. - id: rest conforms: true evidence: >- REST API enablement for IBM z/OS and z/VSE is the core product function, inbound and outbound (https://www.adaptigent.com/solutions/inbound-outbound-api-orchestration/). - id: odbc-jdbc conforms: true evidence: >- Fabric Data Hub "provides SQL-based access to mainframe and distributed data using ODBC and JDBC" (llms.txt, products/data-integration/). - id: fdx conforms: false membership: true evidence: >- Adaptigent (as GT Software) joined the Financial Data Exchange — https://www.adaptigent.com/news/gt-software-joins-financial-data-exchange-to-accelerate-open-banking-adoption/ — and markets an open-banking API solution. MEMBERSHIP ONLY: no FDX-conformant contract, no FDX API schema, and no certification claim is published, so this is recorded as not conforming rather than as a domain-standard signature. - id: oauth2 conforms: unknown evidence: >- No public authentication documentation. The v7.2.1 notes mention API keys for APIMatic API Transformer conversions, which is a build-time tooling credential, not an authentication model for a published API. Auth for generated endpoints is configured per customer deployment and is documented only in the customer portal. - id: rfc9457 conforms: false evidence: >- No published error catalogue and no application/problem+json usage found; no Adaptigent-published contract exists in which to observe error shapes. - id: idempotency conforms: unknown evidence: >- Not addressed in any public material. Idempotency of a generated endpoint is a property of the underlying CICS/IMS transaction the customer wires up. domain_standard: detected: false candidates_probed: - fdx - iso-20022 - psd2 notes: >- The regulated markets Adaptigent sells into (banking, insurance, government) do carry domain standards, and Adaptigent's own marketing names open banking. But domain_standard_conformance reads the CONTRACT, and there is no published contract in which a FDX/ISO 20022/PSD2 message type, schema URN or endpoint shape could be observed. Recorded as not detected rather than credited from a marketing claim. compliance: certifications: [] trust_center: null evidence: >- probe-security-programs.py returned vdp=none trust=none on 2026-08-30; /security/ and /security-policy/ both 404; /.well-known/security.txt 404; trust.adaptigent.com does not resolve. https://www.adaptigent.com/legal-documents/ (200) carries terms, privacy and trademark documents only. maintainers: - FN: Kin Lane X-twitter: apievangelist email: info@apievangelist.com