Get in touch
Questions about coverage, a key, a backfill request, or a venue you'd like us to add? We read everything.
The fastest way to reach us is depthfeed@vcorp.co. For a free Explorer key, mention which venue and workflow you care about (Polymarket, Kalshi, or both) so we can point you to the relevant coverage and API surface.
Coverage requests
We expand coverage based on demand. If there's an asset, market type, or venue you need backtested, tell us — it helps us prioritize. See what we cover today on the coverage section.
What to include for a faster answer
Tell us the venue, market series or asset, date range, resolution, order-book depth, and intended delivery method. If the request supports a backtest, include the decision cadence and whether you need trades, displayed depth, a reference price, or settlement metadata. These details let us distinguish an existing endpoint from a genuine backfill or coverage request.
Before contacting sales
You can review the API documentation, inspect historical coverage concepts, and compare plans on the pricing section. DepthFeed does not promise observations outside the documented archive, so ask for an exact coverage check when a specific historical start date is essential.
How we evaluate a custom data request
A request is a fit when the required venue and market can be captured or already exists in the archive, the delivery format is concrete, and the research question can be answered without overstating what displayed liquidity proves. We will distinguish stored history, current forward capture, and a new integration because those have different lead times and coverage guarantees.
For procurement or enterprise review, include the expected users, monthly request pattern, retention needs, and any requirement for a data dictionary or sample export. Do not send credentials, private keys, or sensitive trading logic by email. A minimal description of the inputs and output fields is enough to begin a coverage check.