us_macro
US macro dashboard from BLS in one call: CPI and core CPI, unemployment, nonfarm payrolls, hourly earnings, participation, PPI and JOLTS openings. Latest value, month, MoM / YoY change and 13-month history. Includes BLS retrieval date and disclaimer. Price: $0.01 USDC per successful call (x402, S...
This record as markdown: /tools/com-it-scorptech-x402/us-macro.md
What us_macro does on ScorpTech x402 API
AI agents call us_macro to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
history | integer | — | months of history per indicator, 0-24 (default 13) |
indicators | string | — | comma-separated subset (default all): cpi, core_cpi, unemployment_rate, nonfarm_payrolls, avg_hourly_earnings, labor_force_participation, ppi_final_demand, jolt |
Parameters from the server's own tool schema.
Why us_macro is rated Low
Even though us_macro only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs us_macro safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For us_macro, this is the rule to start with:
us_macro is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every us_macro call is checked against it from then on.
Questions about us_macro
US macro dashboard from BLS in one call: CPI and core CPI, unemployment, nonfarm payrolls, hourly earnings, participation, PPI and JOLTS openings. Latest value, month, MoM / YoY change and 13-month history. Includes BLS retrieval date and disclaimer. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/us-macro. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
us_macro accepts 2 parameters: history, indicators. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for us_macro: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
us_macro is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the us_macro rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for us_macro. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
us_macro is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue