get_quote
Feed in your requirements — free-form concerns, questions, whole areas of interest — and get back an enumerated quote: your requirements intelligently grouped and disambiguated into well-formed watched topics, then checked BY CODE, topic by topic, against what we actually read: a topic is priced ($20/topic/month at the opening rate) ONLY when a desk, a Watch we keep or a standard Watch reads it from sources with a recent item. How recent is not a fixed number: the live bar is derived from the topic's own cadence and served with each quote in coverage.basis.bars.liveDays, beside coverage.rule, which states it in words. Every topic carries coverage — its state (covered, gap, or cannot-check with the reason), the sources, how many and how fresh. Gaps come back under coverageRequests at $0, never billed, each with the free propose_topic call that asks us to start keeping it; coverage.summary says it in one line. A model proposes the topics; it never decides what is sold. The count is disclosed in BOTH directions: overlaps are merged, broad requirements are split into the separate daily reports they actually need, and billing.expansion states the requirement-to-topic ratio outright so a split is as visible as a merge. Large baskets are resolved in batches, so a requirement the desk cannot place does not sink the rest: you get a quote for everything it could place, partial: true, and unresolvedRequirements naming what it could not and why — never a topic invented to cover a gap. A quote is not a charge, needs no contact details, and holds for 30 days. Real model work: ~10 quotes/day per network address (shared egress shares the allowance).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| requirements | Yes | What you want watched, in your own words — one blob of text or bullet points; the desk does the grouping |