shinnslist docs

The information no one else has, wired into your stack. Start here, then go deep: API key auth, parcel queries, chat search, list building — all on real public records. Nothing fabricated: if a signal has no free source, the docs say so.

getting started LIVE

Four steps to your first result: get an API key, run your first parcel query, run your first chat search, build your first list.

api reference LIVE

Every signal as one REST endpoint and one MCP tool: request shapes, response envelopes, tiers, quotas, and honest live/degraded/pending status.

api keys LIVE

Get a key, send it as x-api-key, read your usage, and see the exact error responses. A working reference of the real auth endpoints — planned features stay draft-badged.

rate limits LIVE

The exact throttles the code enforces — the 100 req/min edge limit, per-endpoint token buckets, exact 429 shapes, and retry guidance.

error reference LIVE

Every error the platform actually returns — exact response JSON, causes, and fixes for 400s, 401s, 403s, 429s, 404s, 500s, 502s, and MCP JSON-RPC errors. Planned errors stay draft-badged.

data freshness LIVE

Every record's own freshness stamp: retrieved_at (pipeline-set) and data_as_of (adapter-declared, honestly null when unknown), the caches that touch your data, and what degraded means for staleness. Planned SLAs stay draft-badged.

changelog LIVE

What every sprint actually shipped, sprint by sprint — generated from the real git history. Every entry cites its commit; nothing invented.

usage & billing LIVE

1,000 v1 calls/month free, the modeled $0.003/call price, what counts as a billable read (one signal × one parcel), and what bills $0 — all quoted from the metering code.

v1 recipes LIVE

Composite signal queries as deterministic billable plans: the exact recipe shape, compile-time errors, the estimate that binds the charge, paged execution, and completed-only billing — quoted from the deployed recipe compiler.

v1 tutorials LIVE

Three end-to-end walkthroughs you can actually execute: assumable mortgages in a ZIP, buying a list from chat, and checking freshness before trusting a price — every endpoint, param, and error code verified against the real code.

engine LIVE

The buyer-intent engine as working reference: /api/engine/* endpoints (assumable, motivated, combined, stats, geoip), the scoring model, constants, and the KV cache — all re-derived from the deployed code.

mcp LIVE

JSON-RPC for agent builders: server/discover → tools/list → tools/call. 271 signal tools, same auth/rate/quota/entitlement gates as the REST API — quoted from the deployed code.

webhooks COMING

Push notifications when a signal changes on a parcel you watch. Not live yet — the page documents the planned design (draft badges), never fake endpoints.

faq LIVE

Short answers from the real code: API keys, quotas, freshness fields, recipe pricing and credits, unbuilt-signal behavior, MCP — nothing invented, drafts stay badged.

sdks LIVE

No published packages yet — but real client surface today: the MCP agent tools and the chat page's copy-paste snippet generators (cURL, Python, JavaScript), quoted verbatim from the deployed code. Typed clients stay draft-badged.

full map

getting startedapi key auth · first parcel query · first chat search · first list build
api keyskey issuance · auth · tiers & quotas · error responses
rate limitsedge throttle · token buckets · exact 429 shapes · retry guidance
error referenceexact 400/401/403/429/404/500/502 shapes · mcp json-rpc errors · fixes
data freshnessretrieved_at · data_as_of · cache ttls · degraded as staleness signal
usage & billingbillable reads · 1,000 calls/mo free · modeled $0.003/call · 402 quota shape
v1 recipesrecipe compiler · estimate binds the charge · paged execution · completed-only billing
v1 tutorialsassumable-mortgage zip run · chat-to-list purchase path · freshness checks
engineassumable · motivated · combined · stats · geoip — buyer-intent endpoints
changelogsprint-by-sprint shipping history · every entry cites its commit
mcpjson-rpc · server/discover · tools/list · tools/call · gates & codes
api referencerest · mcp · tiers & quotas · every signal's status
faqapi keys · quotas · freshness · recipe pricing · unbuilt signals · mcp
webhooks COMINGparcel-watch push events — planned design, no endpoints shipped
sdks LIVEreal client surface: mcp tools + snippet generators · typed clients planned

honest-status promise. Statuses on these pages regenerate from the build's own records (docs/ADAPTER-QUEUE.md). Degraded and pending adapters name their exact reasons. "Coming" sections are marked as such — we don't document endpoints that don't exist.