US macroeconomic time series as stable JSON: CPI, unemployment, payrolls, GDP, and rates, with alias sets. POST /v1/us with a {series} and get the observations as one JSON object. Deterministic per source vintage. Pay per request in USDC; no account, no API key.
POST https://agent.pocket.network/v1/us-macro/v1/toolThe first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.
A real, working call — the request the service card verifies against.
curl -X POST https://agent.pocket.network/v1/us-macro/v1/tool \
-H 'content-type: application/json' \
-d '{"arguments":{"series":"GDP"}}'The response this call returned, captured 2026-09-21 23:50:03 UTC.
{
"portal": {
"provenance": "third-party-supplier",
"serviceId": "us-macro",
"schemaCheck": "unchecked"
},
"data": {
"as_of": "2026-09-21T23:50:02Z",
"bls_lane": {
"reason": "api.bls.gov 403 on all shapes 09-07 — retryable lane",
"status": "not_available"
},
"end": "2026-09-21",
"freshness_note": "FRED updates lag by days; values as-of source",
"lane": "fredgraph.csv (keyless)",
"series": [
{
"count": 10,
"observations": [
{
"date": "2024-01-01",
"value": "28708.161"
},
{
"date": "2024-04-01",
"value": "29147.044"
},
{
"date": "2024-07-01",
"value": "29511.664"
}
],
"series_id": "GDP",
"title": "Gross Domestic Product"
}
],
"start": "2024-01-01",
"status": "ok"
}
}Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.
Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.
| Method | Effect |
|---|---|
GET /v1/health | read |
GET /v1/version | read |
POST /v1/tool | read |
POST /v1/us | read |
Published by the service itself. The example above is generated from these.
{
"type": "object",
"description": "A macro series to fetch. On the MCP relay route POST /v1/tool these fields are wrapped under an `arguments` object; the direct route takes them at the top level.",
"properties": {
"series": {
"type": "string",
"description": "Series name or alias, e.g. GDP, CPI, unemployment."
}
},
"required": [
"series"
]
}{
"type": "object",
"description": "For POST /v1/us, a JSON object with a `series` array of observations. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}