generated: '2026-09-25'
method: derived
generator: derive-data-model.py
source:
- openapi/ibanforge-account-api-openapi.yml
- openapi/ibanforge-api-keys-api-openapi.yml
- openapi/ibanforge-bic-api-openapi.yml
- openapi/ibanforge-compliance-api-openapi.yml
- openapi/ibanforge-credits-api-openapi.yml
- openapi/ibanforge-free-api-openapi.yml
- openapi/ibanforge-iban-api-openapi.yml
- openapi/ibanforge-mcp-api-openapi.yml
- openapi/ibanforge-swiss-clearing-api-openapi.yml
notation: has_one = property $ref; has_many = array of $ref; belongs_to = <entity>_id field
summary:
  entities: 13
  entities_in_spec: 13
  relationships: 3
entities:
- name: AccountKey
  fields: 11
- name: AccountOverview
  fields: 7
- name: ApiError
  fields: 2
- name: BICLookupResult
  fields: 26
- name: BicComplianceResponse
  fields: 10
  description: 'The answer to POST /v1/iban/compliance with a `bic`: the bank screened directly, without an IBAN.
    `found` says whether our directory names the institution, independently of the screen: found false wit'
- name: ChClearingResult
  fields: 14
- name: ComplianceResult
  fields: 6
- name: HealthResponse
  fields: 8
- name: IBANFormatResult
  fields: 9
- name: IBANValidationResult
  fields: 26
- name: PaymentReferenceResult
  fields: 10
- name: ReferenceCheckBlock
  fields: 12
  description: 'Served inside POST /v1/iban/validate when a `reference` was supplied. Carries TWO independent verdicts:
    `valid` (the reference checksum) and `pairing` (whether it may legally travel with this account)'
- name: StatsOverview
  fields: 7
relationships:
- from: AccountOverview
  to: AccountKey
  type: has_many
  via: keys
- from: IBANValidationResult
  to: ReferenceCheckBlock
  type: has_one
  via: reference_check
- from: BicComplianceResponse
  to: ComplianceResult
  type: has_one
  via: compliance