fix(usfiscaldata): correct nonexistent Treasury auctions_query field names - #201
fix(usfiscaldata): correct nonexistent Treasury auctions_query field names#201janosk21 wants to merge 1 commit into
Conversation
The auctions_query reference table and example code used field names that do not exist in the live Treasury Fiscal Data API, so the documented snippets error out: - `accepted_comp_bid_rate_amt` -> `high_yield` (high accepted yield; coupon is `int_rate`). Bills use `high_discnt_rate`. - `indirect_bid_pct_accepted` -> `indirect_bidder_accepted`, which is a USD amount (CURRENCY), not a percentage. Verified against live responses from api.fiscaldata.treasury.gov/services/api/fiscal_service/v1/accounting/od/auctions_query Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Verified the field names against the live API (
So the substance of this PR is right, and the One field is still missing from the fix: Also worth reconsidering: Happy to merge once |
|
Problem
The
usfiscaldataskill'sauctions_querydocumentation references field names that do not exist in the live U.S. Treasury Fiscal Data API. Any user who runs the documented reference table or the example snippet hits an unknown-field error (or a silent empty column).Affected files:
skills/usfiscaldata/references/datasets-securities.mdskills/usfiscaldata/references/examples.mdFixes
accepted_comp_bid_rate_amthigh_yieldint_rate; bills usehigh_discnt_rate/high_investment_rate.indirect_bid_pct_acceptedindirect_bidder_acceptedThe example's yield-curve snippet now runs against the real schema instead of erroring.
Verification
Confirmed against live responses (most recent 10-Year note auctions) from:
Sample returned values:
high_yield=4.468,int_rate=4.375,indirect_bidder_accepted=26775518000(2026-05-15). Enumerated all 113 fields on the record — neitheraccepted_comp_bid_rate_amtnorindirect_bid_pct_acceptedis present.Docs-only change; no code/skill behavior altered.
🤖 Generated with Claude Code