Mearef · Schema

SettlementDateAnswer

The settlement-date computation with its full evidence trail. Nothing here is asserted without a stated basis: the convention says whether it was cited from an instrument or supplied by the caller, and every skipped day names the calendar and reason that skipped it.

CompanyDataGovernmentMiddle East

Properties

Name Type Description
status string
confidence_label string Derived from source type, verification age, stale. Rules: /label-rules
coverage_label string ready=complete, partial=limited, gap=no number. Rules: /label-rules
label_basis object Inputs and rule ids behind both labels
settlement_date string
settlement_weekday string
question object The question as understood: trade date and weekday, business-day count applied, calendars intersected, market/instrument when supplied
convention_applied object The T+n actually used and where it came from: 'cited_convention' (with the instrument, authority and whether it is compelled by law) or 'caller_supplied'. When both were given and differ, the cited cy
trail array Per-day walk from trade date to settlement: each candidate day, whether it counted, and - when skipped - which calendar blocked it and why (weekend rule or a named public holiday)
calendars array Each calendar's basis (national statutory - NOT a CSD or venue calendar), weekend rule, covered period and official source, plus any known divergence worth flagging
caveats array Always worth reading: the specific limits of this answer
View JSON Schema on GitHub

JSON Schema

mearef-dev-settlement-date-answer-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/mearef-dev/json-schema/mearef-dev-settlement-date-answer-schema.json",
  "title": "SettlementDateAnswer",
  "description": "The settlement-date computation with its full evidence trail. Nothing here is asserted without a stated basis: the convention says whether it was cited from an instrument or supplied by the caller, and every skipped day names the calendar and reason that skipped it.",
  "x-generated": "2026-11-18",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/mearef-dev-openapi.json#/components/schemas/SettlementDateAnswer",
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "ok"
      ]
    },
    "confidence_label": {
      "type": "string",
      "enum": [
        "high",
        "medium",
        "low"
      ],
      "description": "Derived from source type, verification age, stale. Rules: /label-rules"
    },
    "coverage_label": {
      "type": "string",
      "enum": [
        "ready",
        "partial",
        "gap"
      ],
      "description": "ready=complete, partial=limited, gap=no number. Rules: /label-rules"
    },
    "label_basis": {
      "type": "object",
      "description": "Inputs and rule ids behind both labels"
    },
    "settlement_date": {
      "type": "string",
      "format": "date"
    },
    "settlement_weekday": {
      "type": "string"
    },
    "question": {
      "type": "object",
      "description": "The question as understood: trade date and weekday, business-day count applied, calendars intersected, market/instrument when supplied"
    },
    "convention_applied": {
      "type": "object",
      "description": "The T+n actually used and where it came from: 'cited_convention' (with the instrument, authority and whether it is compelled by law) or 'caller_supplied'. When both were given and differ, the cited cycle is shown beside the caller's."
    },
    "trail": {
      "type": "array",
      "description": "Per-day walk from trade date to settlement: each candidate day, whether it counted, and - when skipped - which calendar blocked it and why (weekend rule or a named public holiday)",
      "items": {
        "type": "object"
      }
    },
    "calendars": {
      "type": "array",
      "description": "Each calendar's basis (national statutory - NOT a CSD or venue calendar), weekend rule, covered period and official source, plus any known divergence worth flagging",
      "items": {
        "type": "object"
      }
    },
    "caveats": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Always worth reading: the specific limits of this answer"
    }
  },
  "required": [
    "status",
    "settlement_date",
    "question",
    "convention_applied"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/mearef-dev-settlement-date-answer"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.