LEAD INTELLIGENCE / DEVELOPER PREVIEW

A lead-data API for agents
that need more than a list.

From a target to structured company data. Built to fit the software you're building, not replace it.

Vantrill / Data workspaceSample sandbox
TARGET / 001

Austin roofing companies

Fictional fixtures
Records3
EnvironmentSandbox
Live collectionNot enabled
Three fictional records, with synthetic scores used only to demonstrate the API schema
CompanyCategoryFit score
EExample Roofing Coexample.comCommercial roofing84
EExample Commercial Servicesexample.orgCommercial roofing76
EExample Contractorsexample.netCommercial roofing65
Unknown contact fields remain null.Inspect the contract →
SAMPLE RECORD

qualification.score 84

source.provider sample_fixture

scraped_at null

API response / illustrationJSON
{
  "mode": "sandbox",
  "sample": true,
  "scraped_at": null
}
No live scraping or verified contacts.
01 / A PREVIEW OF THE EXPERIENCE

Illustrative workspace. The live sandbox returns fictional records; live scraping, AI enrichment and contact verification are not enabled.

Built around the tools that need better data.

AI agentsInternal toolsVertical softwareDeveloper workflows
01 / SET THE TARGET

Start with the company
you want to find.

A website, a niche or a keyword. Give your agent a clear brief and an API shape it can work with.

Explore target requests

Available in the sample sandbox.

New targetPOST /targets
Target typeNiche
IndustryRoofing companies
LocationAustin, TX · US
Maximum records10
02 / REFINE THE RECORD

The useful part isn't
another thousand rows.

We're building a pipeline for Apify collection, normalization, deduplication, enrichment and qualification. A score should have a reason, and missing data should stay missing.

See what is live today

Production pipeline in development.

Data pipelinePlanned
01CollectApify sources
02NormalizeA consistent schema
03DeduplicateA cleaner record set
04Enrich & qualifyContext behind the score

Source permissions and data rights must be validated before live collection.

03 / BUILD ON IT

Your agent owns
the next step.

Use structured JSON in your own workflow. No campaign software to adopt and no sending inbox to connect.

Read the API specification

Private sandbox key required for data routes.

Submit a targetJavaScript
const response = await fetch(
  `${VANTRILL_BASE_URL}/targets`,
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${API_KEY}`,
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      type: 'niche',
      niche: 'roofing companies',
      location: { city: 'Austin',
        region: 'TX', country: 'US' },
      max_leads: 10
    })
  }
);

A small interface.
Room for your own ideas.

One predictable shape.

Company records, source fields and qualification reasons in a consistent contract. Build against the sample shape before production access opens.

companyqualificationsource

Clear boundaries.

Bearer authentication, cursor pagination, explicit errors and rate limits. Today's sandbox tells you when a feature isn't available.

PaginationCursor-based →Preview rate limit30 requests / min

Data, not outreach.

Vantrill doesn't send messages or start campaigns. You choose the workflow and remain responsible for lawful use of any future data.

Vantrill→Your software

Where the product stands.

AVAILABLE

A sample API you can build against.

Sample targets, lead retrieval, search, usage and pagination. No real companies are collected.

↗
AVAILABLE

A place on the early-access list.

Requests are saved. No checkout, automated email or production key is issued.

→
PLANNED

The production data pipeline.

Live scraping, real enrichment, contact verification and live keys are still ahead.

↗

EARLY ACCESS

What would you build
with a better data layer?

Tell us what your software needs to find. Your use case can help shape the first production version.

Joining is free. Production access is not open yet.

Before you get started.

What can I use right now?

The developer documentation, persisted signup form and private-key sample API are available. Sample jobs use fictional fixtures and simulate collection; they do not scrape or run AI enrichment.

Where will the data come from?

The production plan starts with Apify-based target collection, followed by cleaning, deduplication, enrichment and scoring. Sources, permissions, privacy obligations and verification must be validated before live data is enabled.

Can I buy a production plan?

Not yet. Joining early access costs nothing. Prices in the draft specification are proposals only; billing and production-key issuance are not active.

Give your next build
a clearer starting point.

Join early access