---
title: "Asset/Liability Coverage"
method: POST
path: "/v1/tools/compute_asset_liability_coverage"
tags: ["TODO_TAGS_REVIEW", "TODO_AP2_EXPORT_REVIEW"]
---

# Asset/Liability Coverage

`POST /v1/tools/compute_asset_liability_coverage`

## Request

- Base URL: `https://ainumbers.co`
- URL: `https://ainumbers.co/v1/tools/compute_asset_liability_coverage`
- Auth: none declared

General, jurisdiction-neutral solvency check: total_assets_musd / total_liabilities_musd, plus surplus_shortfall_musd = total_assets_musd - total_liabilities_musd, per asset-class and liability-class breakdown, rolled up. COVERED at or above 1.0, SHORTFALL below it. A zero-liabilities line resolves coverage_ratio null and status NO_LIABILITIES_OUTSTANDING -- never a division artifact. Aggregate totals only (no per-customer or per-wallet line item). No single normative anchor exists for exchange-level asset/liability coverage (unlike bank capital-adequacy ratios elsewhere in the suite) -- stated explicitly rather than inventing a crosswalk citation.

**Tool URL:** https://ainumbers.co/chaingraph/art-539-asset-liability-coverage.html

## Request body

- object
  - `assets` unknown, required
  - `liabilities` unknown, required

## Response `200`

Successful tool execution result

- object
  - `asset_breakdown` object[]
    - `amount_musd` integer
    - `asset_class` string
  - `coverage_ratio` number
  - `formula` string
  - `liability_breakdown` object[]
    - `amount_musd` integer
    - `liability_class` string
  - `note` string
  - `status` string
  - `surplus_shortfall_musd` integer
  - `total_assets_musd` integer
  - `total_liabilities_musd` integer

---

[API](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite.md) · [All operations](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite/llms.txt) · [OpenAPI document](https://skmtc.dev/ainumbers/apis/ainumbers-co-fintech-intelligence-suite/revisions/b462e4f5bb28?raw)