---
title: "In/out volume of an address"
method: GET
path: "/v1/addresses/{address}/volume"
tags: ["addresses"]
---

# In/out volume of an address

`GET /v1/addresses/{address}/volume`

## Request

- Base URL: `https://stablescan.achivx.com`
- URL: `https://stablescan.achivx.com/v1/addresses/{address}/volume`
- Auth: none required

Check the `*_complete` flags before trusting a total or a 0 — a hub-sized address can run out of budget. On Solana (chain -1) the answer also carries `coverage_status` — `pending` (the address's history is still being filled, or no fill was asked for yet, since this read never starts one) or `partial` (filled to a documented bound). The `*_complete` flags describe the request budget only and never cover the Solana fill state. A Solana answer without `coverage_status` could not read it in time — treat it as `pending`.

## Path parameters

- `address` string, required

## Query parameters

- `chain` union: A network — number, number in a string, slug or CAIP-2 id (the slugs and CAIP-2 ids are /v1/networks' `slug` and `caip2`). The string forms are listed exactly; the server reads them leniently, as A2A and MCP do: surrounding whitespace, a leading + and leading zeros are ignored, slugs and CAIP-2 ids match in any letter case, and an empty or blank value is no chain at all (the default; /v1/freezes/acts alone refuses an empty filter). Anything else (hex, a decimal fraction, a zero-padded CAIP-2 reference, an unindexed network) is 400 invalid_chain.
  - 1 | 10 | 56 | 8453 | 42161 | 728126428 | -1
  - '1' | '10' | '56' | '8453' | '42161' | '728126428' | '-1' | 'ethereum' | 'optimism' | 'bnb-chain' | 'base' | 'arbitrum' | 'tron' | 'solana' | 'eip155:1' | 'eip155:10' | 'eip155:56' | 'eip155:8453' | 'eip155:42161' | 'eip155:728126428' | 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp'
- `days` integer

## Response `200`

In/out volume of an address.

- AddressVolume
  - `address` string, required
  - `address_respelled` boolean, required: true when the address you sent is spelled for another kind of chain than chain_id — a T… (Tron) address asked about an EVM chain, a 0x… address asked about Tron, a 32-byte base58 (Solana) key asked about an EVM chain or Tron — and the answer is about those same bytes on chain_id. Accepted, not refused; the same 20 bytes are the same owner on EVM chains and Tron only for a plain key account, not for a contract. Always false when you did not pass chain: the spelling then chooses the chain.
  - `all_time` object, required
    - `in_usd6` integer, required
    - `out_usd6` integer, required
    - `total_usd6` integer, required
    - `transfers` integer, required
  - `all_time_complete` boolean, required
  - `chain_id` integer, required
  - `chain_source` string, required: How chain_id was chosen: explicit (you passed chain), default (a 0x address with no chain is answered about Base), address_form (a T or base58 address is answered about the chain its spelling implies). The answer is always about the one chain in chain_id.
  - `chains_with_data` object[], nullable, required: The indexed networks, the asked one included, where this address has anything at all (kinds: transfers, labels, issuer_acts) — a cheap presence probe, not a verdict. [] = no indexed network holds a transfer, a label or a standing issuer act for it; null = the map could not be read for this answer, ask again.
    - `chain_id` integer, required
    - `kinds` string[], nullable, required
  - `coverage_status` string: Solana (chain_id -1) only: the fill state of this address. pending - its history is still being filled, or no fill was asked for yet (this read never starts one; a compliance read of the address does), so a small or zero total is not final; partial - filled to a documented bound. period_complete and all_time_complete describe the request budget only, never this. Absent on every other network; a Solana answer without it could not read it in time — treat it as pending.
  - `freshness_seconds` integer, nullable, required: Age in seconds of this chain's newest indexed transfer when the answer was served; null when it could not be read for this answer or the chain has no indexed transfer yet — a failed read is never reported as a number. The verdict never moves on it.
  - `note` string, required
  - `period` object, required
    - `in_usd6` integer, required
    - `out_usd6` integer, required
    - `total_usd6` integer, required
    - `transfers` integer, required
  - `period_complete` boolean, required
  - `period_days` integer, required
  - `requested_address` string, required: The address exactly as you sent it. address beside it is the same bytes written in the spelling of chain_id (0x-hex in lower case on EVM chains, T… on Tron, base58 on Solana) — except on /v1/addresses/{address}/balances, whose address echoes what you sent.
  - `since_day` string

## Other responses

- `400`: The one error envelope. Branch on `error.code`, not on the status.
- `404`: The one error envelope. Branch on `error.code`, not on the status.
- `429`: The per-IP token bucket (20 requests/second, burst 40) is empty — wait `Retry-After`.
- `500`: The one error envelope. Branch on `error.code`, not on the status.
- `503`: The one error envelope. Branch on `error.code`, not on the status.

---

[API](https://skmtc.dev/achivx/apis/stablecoin-scanner-rest-api.md) · [All operations](https://skmtc.dev/achivx/apis/stablecoin-scanner-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/achivx/apis/stablecoin-scanner-rest-api/revisions/cbd001c8925c?raw)