treasury.monthly-statement

Monthly Treasury Statement (MTS) — Table 4: receipts by source via US Treasury Fiscal Data. Returns monthly totals of federal government receipts grouped by classification (individual income tax, corporate income tax, social-insurance receipts, excise, customs, estate-and-gift, miscellaneous). Each row carries record_date, classification_id, classification_desc, current_month + current_fytd (fiscal year-to-date) gross_rcpt / refund / net_rcpt amounts, plus prior_fytd comparisons. Backbone of any "how much money is the federal government bringing in" question. Use Fiscal Data filter syntax.

price
$0.0012 USDC per call
method
GET/api/treasury/monthly-statement
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The monthly statement API is a pay-per-call treasury endpoint built for AI agents and autonomous software. Monthly Treasury Statement (MTS) — Table 4: receipts by source via US Treasury Fiscal Data.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in monthly statement data source for an agent tool-use loop, an MCP host, or a backend that needs treasury data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
fieldsstring
max 400 chars · match ^[a-z][a-z0-9_]*(,[a-z][a-z0-9_]*)*$
filterstring
max 800 chars · match ^[a-z][a-z0-9_]*:(eq|ne|lt|lte|gt|gte|in):[A-Za-z0-9._:\-+/, ]+(,[a-z][a-z0-9_]*:(eq|ne|lt|lte|gt|gte|in):[A-Za-z0-9._:\-+/, ]+)*$
sortstring
max 200 chars · match ^-?[a-z][a-z0-9_]*(,-?[a-z][a-z0-9_]*)*$
pageSizeinteger
min 1 · max 10000
pageNumberinteger
min 1

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/treasury/monthly-statement?fields=example&filter=example&sort=example&pageSize=100&pageNumber=1'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/treasury/monthly-statement?fields=example&filter=example&sort=example&pageSize=100&pageNumber=1' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/treasury/monthly-statement?fields=example&filter=example&sort=example&pageSize=100&pageNumber=1'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.treasury.monthlyStatement({
  "fields": "example",
  "filter": "example",
  "sort": "example",
  "pageSize": 100,
  "pageNumber": 1
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.treasury.monthly_statement(fields="example", filter="example", sort="example", pageSize=100, pageNumber=1)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "treasury.monthly-statement",
    "arguments": {
      "fields": "example",
      "filter": "example",
      "sort": "example",
      "pageSize": 100,
      "pageNumber": 1
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
pageobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {}
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "page": {
    "number": 1,
    "size": 1,
    "pages": 1
  },
  "meta": {}
}

FAQ

Do I need an API key to use the monthly statement API?
No. treasury.monthly-statement is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the monthly statement API cost?
$0.0012 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the monthly statement API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call treasury.monthly-statement from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: monthly statement api · treasury monthly statement api · monthly statement api for ai agents · x402 treasury api · monthly statement api no api key · pay per call monthly statement api · treasury api