The same data the desk runs on.

Two calls tell you most of what you need. Responses below are truncated for the page; shapes are exact.

$ curl -s "https://dhawal.org/api/quotes?symbols=SPY,QQQ"
{"quotes":{"SPY":{"symbol":"SPY","last":751.71,"changePct":0.84,
  "prevClose":745.40,"dayHigh":751.97,"dayLow":745.59, ...},
 "QQQ":{...}},"fetchedAt":1783690000,"ttlSeconds":30}

$ curl -s "https://dhawal.org/api/congress?ticker=NVDA&limit=2"
{"trades":[{"transactionDate":"2026-06-30","filingDate":"2026-07-08",
  "ticker":"NVDA","type":"Sale (Partial)","side":"sell",
  "amountLabel":"$15,001 - $50,000","member":"Sheldon Whitehouse",
  "chamber":"senate","party":"D","state":"RI","daysToFile":8,
  "late":false,"docUrl":"https://efdsearch.senate.gov/..."}, ...],
 "count":2,"asOf":"2026-07-08","source":"congress-trading-monitor"}

Rendered from the same OpenAPI document the machines read, so this table cannot drift from the deployment. All endpoints are GET, all return JSON, and starred parameters are required.

Every successful JSON GET response exposes three evidence headers. X-Dataset-Version names the response contract, X-Content-SHA256 hashes the exact bytes received, and X-Data-As-Of carries the payload's top-level observation or generation time when one is available. These headers are CORS-visible, so a saved request can verify its payload before parsing it.

The statistics endpoint supports an inclusive UTC observation-date cutoff, for example /api/statistics?metric=price&symbol=SPY&asOf=2024-10-12. It excludes every later observation and reports the date it actually resolved. This uses the latest available historical series, so it does not claim to reconstruct revisions that were unknown on that date.

FRED-backed macro requests go further. Adding asOf=YYYY-MM-DD sends that date to FRED as a vintage date, so later observations and revisions are excluded. Macro and net-liquidity statistics inherit this vintage policy. The response reports the requested vintage separately from the latest observation that was actually available within it.

Regime, breadth, and SPX options statistics can also resolve an exact retained Machine Floor date. A successful archive match returns the immutable artifact URL, its payload SHA-256, the archive date, and the underlying observation date separately. Dates without a retained snapshot stay on the explicitly labeled latest-history policy.

Cited Ask responses and the MCP get_brief tool use the same financial-fact-v2 envelope. A stable canonicalId identifies the sourced observation. Response-local labels such as F1 only connect answer prose to that fact inside one response.

Product, calculation method, primary source, and equivalent API response are separate destinations. A missing destination stays null and is described as an evidence gap. It is never replaced with a nearby link.

{
  "statement": "The macro regime composite was 68.4/100.",
  "rawValue": 68.4,
  "formattedValue": "68.4/100",
  "unit": "score out of 100",
  "sourceName": "dhawal.org composite from FRED and Yahoo Finance",
  "sourceUrl": "https://fred.stlouisfed.org/",
  "artifactUrl": "/data/regime-history-source.json",
  "productUrl": "/markets/",
  "methodologyId": "macro-regime-composite",
  "methodologyUrl": "/methodology/",
  "apiUrl": "/api/macro",
  "transformation": "macro-regime-composite",
  "period": "Latest available observation for each leg",
  "asOf": "2026-07-10T20:00:00.000Z",
  "observationDate": null,
  "observedAt": "2026-07-10T20:00:00.000Z",
  "capturedAt": "2026-07-10T20:01:00.000Z",
  "generatedAt": "2026-07-10T20:02:00.000Z",
  "freshness": "delayed",
  "expectedCadence": "each market session",
  "limitation": "The composite is descriptive and may mix source observation dates.",
  "canonicalId": "fact_0z7sbu8"
}

This example is generated from the same typed fixture used by the OpenAPI FinancialFact schema and contract tests.

Best effort, not an SLA: these endpoints run the live site first and your scripts second. Edge caching reduces repeated identical upstream work, but it is not client rate limiting or abuse protection. Be gentle and cache on your side too.

Attribute what you use: credit dhawal.org and the primary source named on each endpoint (FRED, CFTC, SEC EDGAR, the U.S. Treasury, the Congress Trading Monitor dataset, and so on), the same way this site credits them on every page. Endpoints evolve with the desk; material changes land in the changelog first.

Nothing here is investment advice. Delayed and derived data, disclosed methodology, and the same honesty rules as the rest of the site: how every number is computed is on the methodology page.

The full OpenAPI 3.1 document, including response schemas for every envelope above, is served at /.well-known/api/v1/spec.json. Point an agent, a client generator, or a curious REPL at it; this page is rendered from the same document.

The desk speaks the Model Context Protocol. An AI agent (Claude, ChatGPT, Cursor, or your own) connects once and calls the data live, so a person never has to copy a number out of a page and paste it into a chat. The endpoint is stateless Streamable HTTP, no key and no login:

https://dhawal.org/mcp

23 tools, including the canonical agent contract: ask_desk, get_quote, get_regime, run_screen, explain_signal, get_symbol, get_calendar, get_congress_trades, get_13f, get_dataset, get_brief, get_state_vector, find_analogs, and get_signal_performance. The original specialist tools remain available for options, COT, insiders, seasonality, the yield curve, and the news wire. The three institutional tools verify SHA-256 before returning an immutable evidence URL. get_regime is the compatibility alias for get_macro_regime. Calls return readable text and structured JSON where the result is tabular. Add it to Claude Code with:

$ claude mcp add --transport http dhawal https://dhawal.org/mcp

Agent instructions are also published at /skill.md, and aggregate-only tool traffic is visible on /machine. No prompt, argument, symbol, address, user agent, or session is recorded.

In Claude or ChatGPT, add it as a custom connector or developer-mode MCP server, pasting the same URL. It negotiates protocol revision 2025-11-25. No credentials to manage; the same terms as the JSON API apply.