The US economic-data release CALENDAR — when official economic reports are published, from the Federal Reserve's FRED. Returns upcoming release dates (date, release name, FRED release id), starting from `from` (default today), ascending. Filter by name to find a specific report's schedule (e.g. name="Consumer Price Index" → the next CPI dates; "Employment Situation" → jobs report; "Gross Domestic Product"; "FOMC"), or by releaseId. Free, public-domain (FRED). Future release dates an LLM cannot possibly know — essential for trading, scheduling, and macro-monitoring agents that need to act around data drops. Pair with econ.fred to pull the actual numbers once a release is out.
/api/econ/fred-releasesPAYMENT-SIGNATURE.The fred releases API is a pay-per-call econ endpoint built for AI agents and autonomous software. The US economic-data release CALENDAR — when official economic reports are published, from the Federal Reserve's FRED.
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 fred releases data source for an agent tool-use loop, an MCP host, or a backend that needs econ data on demand without onboarding to yet another vendor portal.
| Name | Type | Description |
|---|---|---|
from | string | match ^\d{4}-\d{2}-\d{2}$ |
name | string | min 1 chars · max 80 chars |
releaseId | integer | min 1 · max 100000 |
limit | integer | min 1 · max 100 |
# 1. Probe with no auth → 402 envelope with PaymentRequirements curl -sS 'https://2s.io/api/econ/fred-releases?from=2024-01-01&name=example&releaseId=1&limit=1' # 2. Sign + retry with PAYMENT-SIGNATURE: curl -sS 'https://2s.io/api/econ/fred-releases?from=2024-01-01&name=example&releaseId=1&limit=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/econ/fred-releases?from=2024-01-01&name=example&releaseId=1&limit=1'
import { TwoS } from '@2sio/sdk'
const client = new TwoS({
privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})
const result = await client.econ.fredReleases({
"from": "2024-01-01",
"name": "example",
"releaseId": 1,
"limit": 1
})
console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)import os
from twosio import TwoS
client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])
result = client.econ.fred_releases(from="2024-01-01", name="example", releaseId=1, limit=1)
print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)// 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": "econ.fred-releases",
"arguments": {
"from": "2024-01-01",
"name": "example",
"releaseId": 1,
"limit": 1
}
}
}| Field | Type | Description |
|---|---|---|
ok | boolean | one of: true |
items | array | |
total | integer | Total matching rows upstream; null when unknown. |
source | object |
{
"ok": true,
"items": [
{
"date": "example",
"releaseName": "example",
"releaseId": 1
}
],
"total": 1,
"source": {
"provider": "example",
"url": "example",
"license": "example"
}
}