U.S. Treasury Fiscal Data
The U.S. Treasury Bureau of the Fiscal Service manages the government's finances including collecting revenue, paying federal bills, managing federal debt, and producing the nation's financial accounts. Their Fiscal Data API provides free, open access to federal financial data through a standardized RESTful API covering 80+ datasets. Key datasets include the Debt to the Penny (daily public debt outstanding), Treasury Reporting Rates of Exchange (quarterly foreign currency rates), Average Interest Rates on U.S. Treasury Securities, Daily Treasury Statements, Monthly Treasury Statements, and U.S. savings bond data. No authentication required.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles U.S. Treasury Fiscal Data the way a machine reads it — 69 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — U.S. Treasury Fiscal Data scores 52.8/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile U.S. Treasury Fiscal Data
Each block below is one kind of artifact we hold for U.S. Treasury Fiscal Data. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
U.S. Treasury Fiscal Data Exchange Rates API
Treasury reporting rates of exchange for foreign currencies.
U.S. Treasury Fiscal Data National Debt API
Federal debt, public debt outstanding, and interest rate data.
U.S. Treasury Fiscal Data Securities API
Treasury securities, savings bonds, and investment data.
U.S. Treasury Fiscal Data Treasury Statements API
Daily and monthly Treasury financial statements.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
U S Treasury Fiscal Data Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Features 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
No Authentication Required
All Treasury Fiscal Data API endpoints are publicly accessible without API keys or registration, enabling immediate programmatic access.
Flexible Field Selection
Use the fields parameter to request only the specific data fields needed, reducing response payload size and improving performance.
Advanced Filtering
Filter datasets using field:operator:value syntax supporting equality, range, and set membership operators across any field in the dataset.
Pagination Support
All endpoints support page[number] and page[size] pagination with metadata indicating total record count and total pages available.
Multiple Output Formats
API responses available in JSON, XML, and CSV formats suitable for programmatic consumption, data warehousing, and spreadsheet analysis.
Comprehensive Coverage
80+ datasets covering all major Bureau of the Fiscal Service financial reports from the Debt to the Penny to Monthly Treasury Statements.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
U.S. Treasury Fiscal Data API Rules
SPECTRALU.S. Treasury Fiscal Data API Rules
SPECTRALJSON Schema 14
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
DailyTreasuryRecord
JSON SCHEMADailyTreasuryStatementResponse
JSON SCHEMADebtRecord
JSON SCHEMADebtToPennyResponse
JSON SCHEMAErrorResponse
JSON SCHEMAExchangeRateRecord
JSON SCHEMAExchangeRateResponse
JSON SCHEMAFiscalLinks
JSON SCHEMAFiscalMeta
JSON SCHEMAGenericFiscalResponse
JSON SCHEMAInterestRateRecord
JSON SCHEMAInterestRateResponse
JSON SCHEMAMonthlyTreasuryRecord
JSON SCHEMAMonthlyTreasuryStatementResponse
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 14
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Treasury Daily Treasury Record Structure
JSON STRUCTURETreasury Daily Treasury Statement Response Structure
JSON STRUCTURETreasury Debt Record Structure
JSON STRUCTURETreasury Debt To Penny Response Structure
JSON STRUCTURETreasury Error Response Structure
JSON STRUCTURETreasury Exchange Rate Record Structure
JSON STRUCTURETreasury Exchange Rate Response Structure
JSON STRUCTURETreasury Fiscal Links Structure
JSON STRUCTURETreasury Fiscal Meta Structure
JSON STRUCTURETreasury Generic Fiscal Response Structure
JSON STRUCTURETreasury Interest Rate Record Structure
JSON STRUCTURETreasury Interest Rate Response Structure
JSON STRUCTURETreasury Monthly Treasury Record Structure
JSON STRUCTURETreasury Monthly Treasury Statement Response Structure
JSON STRUCTUREScroll within the panel for all 14 ·
Examples 14
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Treasury Debt Record Example
EXAMPLETreasury Fiscal Meta Example
EXAMPLEScroll within the panel for all 14 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
National Debt Tracking
Journalists, economists, and citizens monitor daily changes in U.S. public debt outstanding including amounts held by the public and intragovernmental holdings.
Exchange Rate Research
Federal agencies, researchers, and businesses use Treasury exchange rates for reporting foreign currency transactions in accordance with federal accounting standards.
Budget Analysis
Policy analysts and budget offices track federal government receipts and outlays from Monthly Treasury Statements to assess deficit trends.
Interest Rate Monitoring
Economists and investors track average interest rates on Treasury securities to analyze government borrowing costs and monetary policy.
Treasury Cash Management
Financial researchers analyze Daily Treasury Statement data to understand federal government cash flows and liquidity management.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
FRED Economic Database
Federal Reserve Economic Database (FRED) integrates Treasury Fiscal Data series for economic research and modeling applications.
USASpending.gov
Federal spending transparency portal uses Bureau of the Fiscal Service data alongside Treasury Fiscal Data for comprehensive spending analysis.
Federal Accounting Standards
Treasury exchange rates and fiscal data support OMB/FASAB-compliant financial reporting across federal agencies and programs.
fiscaldata.treasury.gov
The official Treasury Fiscal Data portal provides data visualization, dataset explorer, and download tools built on the same API.
Resources
Every other property we hold for U.S. Treasury Fiscal Data — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/u-s-treasury-fiscal-data · machine-readable index on apis.io