Accountable Redemption API

On-chain redemption rate feeds.

OpenAPI Specification

accountable-redemption-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Accountable NAV / Proof of Reserves Feeds Redemption API
  version: '1.1'
  description: High-availability API providing real-time collateralization, net asset value (NAV), and redemption rate data with ripcord signalling for on-chain consumption by Chainlink. Endpoints can be queried directly from the source node and carry cryptographic guarantees (TEE attestations + HTTP Message Signatures per RFC 9421) for the integrity of the data. Accountable central nodes route to the underlying distributed network, provide fault tolerance across three clouds, and forward the cryptographic guarantees for the source data.
  contact:
    name: Accountable
    url: https://docs.accountable.capital/
  x-logo:
    url: https://accountable.capital/favicon-light.ico
servers:
- url: https://{node}
  description: 'Per-client source node in Accountable''s distributed network (example in docs: https://source.node.com). Central nodes route to the underlying network. Replace {node} with the node host provisioned at onboarding.'
  variables:
    node:
      default: source.node.com
      description: Source node host provisioned per client at onboarding.
tags:
- name: Redemption
  description: On-chain redemption rate feeds.
paths:
  /redemption-rate:
    get:
      operationId: getRedemptionRate
      summary: On-chain redemption rate (derived from NAV per share)
      description: Returns the current redemption rate per token unit alongside rate bounds and ripcord status. This is the primary endpoint consumed for on-chain PoR write operations.
      tags:
      - Redemption
      responses:
        '200':
          description: Current redemption rate snapshot.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RedemptionRate'
        '503':
          description: Feed is stale (protection bound breached or source unavailable).
components:
  schemas:
    RedemptionRate:
      type: object
      required:
      - client
      - net_asset_value
      - redemption_rate_value
      - redemption_rate_usd
      - outstanding_shares
      - min_rate
      - max_rate
      - updatedAt
      - ripcord
      - ripcordDetails
      properties:
        client:
          type: string
          description: Issuer identifier.
        net_asset_value:
          type: string
          description: NAV per token unit as a high-precision decimal string. Typically equals the collateralization ratio.
        redemption_rate_value:
          type: string
          description: Redemption rate in token-native units. Fed directly into the on-chain contract.
        redemption_rate_usd:
          type: string
          description: Redemption rate denominated in USD. Used for off-chain reconciliation and monitoring.
        outstanding_shares:
          type: string
          description: Total token supply outstanding. Mirrors totalSupply from the /reserves endpoint.
        min_rate:
          type: number
          description: Minimum acceptable redemption rate. Circuit-breaker lower bound (e.g. 0.98).
        max_rate:
          type: number
          description: Maximum acceptable redemption rate. Circuit-breaker upper bound (e.g. 1.05).
        updatedAt:
          type: string
          format: date-time
          description: UTC timestamp of the last successful data refresh from the underlying custodian data source.
        ripcord:
          type: boolean
          description: true if one or more ripcord conditions are active. When true, on-chain updates must be halted.
        ripcordDetails:
          type: array
          items:
            type: string
          description: List of active ripcord category codes. Empty array when ripcord is false.
x-apievangelist:
  generated: '2026-07-17'
  method: derived
  source: https://docs.accountable.capital/accountable-documentation/data-verification-network-dvn/nav-feeds
  note: Derived faithfully from Accountable's published "NAV / Proof of Reserves Centralized Endpoint" documentation (Version 1.1, March 2026). Field names, types, and descriptions are taken verbatim from the docs. No values were fabricated. The API is served from Accountable's distributed node infrastructure (per-client source nodes routed by central nodes across AWS, Google Cloud and Azure); the public base host is per-deployment, so the server below is templated.