US Treasury

Official Treasury Fiscal Data series: debt, rates, outlays, auctions

This Actor pulls official US Treasury Fiscal Data API datasets (debt to the penny, average interest rates, MTS Table 1, record-setting auctions) for feeds you configure and emits source-linked change rows.

Not FX mid-market rates. Not financial advice. Not a trading signal. Public Treasury APIs only.

from $9.00 / 1,000 Treasury fiscal data change row ($0.009 per delivered apify-default-dataset-item). No Actor Start. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

Open US Treasury Data Scraper on Apify

US Treasury Data Scraper, not a neighboring Actor

Use this page for this Actor’s job. Use Forex Exchange Rate Scraper for FX snapshots; Use Grants.gov Scraper for Grants.gov notices; Use Campaign Finance Scraper for FEC/LDA filings.

Store ID: taroyamada/treasury-fiscal-data-digest. Respect source terms, robots.txt, and rate limits.

Use cases

• Debt-to-the-penny watches
• Average interest-rate diffs
• Scheduled fiscal snapshotKey runs

How is US Treasury Data Scraper different from Forex Exchange Rate Scraper and Grants.gov Scraper?

US Treasury Data Scraper (taroyamada/treasury-fiscal-data-digest): This Actor pulls official US Treasury Fiscal Data API datasets (debt to the penny, average interest rates, MTS Table 1, record-setting auctions) for feeds you configure and emits source-linked change rows. Not FX mid-market rates. Not financial advice. Not a trading signal. Public Treasury APIs only. Forex Exchange Rate Scraper is for FX snapshots (input baseCurrency; open.er-api.com; exchange-rate snapshots). Not Treasury fiscal series. Grants.gov Scraper is for Grants.gov notices (input feeds / watchTerms; Grants.gov API; funding digest rows). Not TED/SAM.gov bid queues. Campaign Finance Scraper is for FEC/LDA filings (input feeds / watchTerms; OpenFEC / LDA.gov; campaign digest rows). Not OFAC sanctions or Federal Register.

What input is required?

Live required fields: feeds. Published exampleRunInput is shown below. Quickstart: configure one or more feeds, keep delivery=dataset, and run once to seed the baseline

Published Store example run input (omitted fields take schema defaults):

{
  "feeds": [
    {
      "id": "debt-daily",
      "name": "Debt to the Penny",
      "source": "debt_to_penny"
    },
    {
      "id": "marketable-rates",
      "name": "Marketable Treasury Rates",
      "source": "avg_interest_rates",
      "securityDescriptions": "Treasury Bills,Treasury Notes,Treasury Bonds"
    },
    {
      "id": "monthly-budget",
      "name": "MTS Receipts & Outlays",
      "source": "mts_table_1"
    },
    {
      "id": "record-auctions",
      "name": "Recent Record-Setting Auctions",
      "source": "record_setting_auction",
      "securityTypes": "Bills,Notes",
      "lookbackDays": 180
    }
  ],
  "watchTerms": "deficit,10-Year,Treasury Bills",
  "lookbackDays": 180,
  "maxEvidencePerFeed": 5,
  "delivery": "dataset",
  "datasetMode": "all",
  "snapshotKey": "treasury-fiscal-data-digest-quickstart",
  "notifyOnNoNew": true,
  "dryRun": false
}

Run US Treasury Data Scraper on Apify

How do dataset, webhook, and dry-run delivery work?

delivery defaults to dataset on the live schema. Dataset output is the billable surface when rows are written. webhookUrl is used when delivery is webhook (and typically not during dryRun). dryRun true validates or samples without the usual dataset/webhook side effects described on the Store schema. datasetMode can limit emits to changes_only / changed_only / action_needed versus all. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

What does a result contain?

README output fence is truncated or invalid JSON on Store. Illustration head: { "meta": { "feedCount": 4, "totalEvidenceRows": 8, "actionNeededCount": 3, "executiveSummary": { "overallStatus": "action_needed", "brief": "3 feed(s) require review; 4 changed since the last run." } }, "digests": [ { "feedId": "monthly-budget", "status": "action_needed", "headl… Treat README samples as illustrations, not a live coverage guarantee. There is no published output JSON schema on the Store page.

How is US Treasury Data Scraper priced?

Billing is pay per event. The live Store card is from $9.00 / 1,000 Treasury fiscal data change row ($0.009 per delivered apify-default-dataset-item). No Actor Start. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE. Current PPE:

The published README Cost block is stale versus the live Store pricing tab. README Cost still quotes actor-start $0.01. README Cost quotes dataset-item $0.003; live primary is $0.009 (Treasury fiscal data change row). Live: Treasury fiscal data change row $0.009. This page quotes live PPE only.

from $9.00 / 1,000 Treasury fiscal data change row ($0.009 per delivered apify-default-dataset-item). No Actor Start. Unchanged runs that write zero default-dataset rows typically charge $0.00 on current PPE.

See US Treasury Data Scraper pricing on Apify

Limits to keep in mind

• feeds required
• Treasury Fiscal Data APIs
• maxEvidencePerFeed cap
• Not financial advice
• Respect source terms, robots.txt, and rate limits.

Open US Treasury Data Scraper on Apify

Related pages

• Forex Exchange Rate Scraper — FX pairs, not Treasury series.
• Grants.gov Scraper — Grant notices, not fiscal totals.
• Campaign Finance Scraper — FEC/LDA, not Treasury APIs.
• FDIC & NCUA Peer Financial Trend Report — bank/CU call reports.
• Tools