---
title: "A SIGNED statement of what an address spent (proof for a principal)"
method: GET
path: "/api/statement/spend"
tags: ["transparency"]
---

# A SIGNED statement of what an address spent (proof for a principal)

`GET /api/statement/spend`

## Request

- Base URL: `https://api.anygas.xyz/svc`
- URL: `https://api.anygas.xyz/svc/api/statement/spend`
- Auth: none declared

An AI agent that spends on someone's behalf cannot currently PROVE what it spent — its own summary is a claim by the party being audited, and a dashboard screenshot proves nothing. This returns every transfer in the window with the fee on each broken down, SIGNED by Robyn's relayer key. The principal verifies the signature against the published signer address and knows the numbers came from us, unmodified — without trusting the agent and without trusting a web page. NOW COVERS EVERY RAIL — the float lane plus routed settlements (CCTP, Stellar, Solana, Tron, Chainflip, aggregators) — with a `byRail` split so a merged total cannot hide which rails were used. It previously covered the float lane only; that was declared as a limitation, but an honest limitation was still a hole. Third-party bridge fees taken inside a routed leg are not itemised and are excluded, which `limitations` states.

## Query parameters

- `address` string
- `days` integer

## Response `200`

Signed statement: entries, per-entry fee breakdown, totals, digest, signature, limitations

- object

---

[API](https://skmtc.dev/anygas/apis/robyn-anygas-api.md) · [All operations](https://skmtc.dev/anygas/apis/robyn-anygas-api/llms.txt) · [OpenAPI document](https://skmtc.dev/anygas/apis/robyn-anygas-api/revisions/9b7498be8304?raw)