Design partner access
We are onboarding a small number of builders who want to test Headless Records against real finance-agent or SEC data workflows.
Who qualifies
- You are building a finance agent, SEC data workflow, research tool, or public-record data product.
- You currently scrape, parse, normalize, or manually review SEC filings.
- You care about freshness, filing-level provenance, and structured caveats.
- You can test one endpoint in a real workflow within two weeks.
What design partners get
- A bounded watched ticker universe configured around your workflow
- API key access to early endpoints
- Freshness and provenance responses for your selected tickers
- Direct input into response shape, caveats, and access patterns
- MCP setup guidance for local stdio demos
What we need from you
- Your project and the workflow you want to test first
- The tickers or universe you care about
- Your desired freshness window
- Your preferred access style
- Any source citation or caveat requirements your agent needs
What happens after you email
We review fit, confirm the watched ticker universe, agree on a freshness window, issue API key access, and identify the first workflow you will test.
What a watched ticker universe means
A watched ticker universe is the bounded set of tickers configured for your API key. Freshness, assessment, and provenance responses are scoped to that configured universe during design partner access.
Available access styles
API key access comes first. Local stdio MCP setup guidance is available when the workflow and integration pattern become clear.
Expected test workflow
The ideal first test is one real workflow where your app or agent calls GET /v1/insider-activity/{ticker}/assessment, checks freshness and caveats, cites sources, and avoids claims the filing data cannot support.