QuickContact logo
QuickContact
Context-aware contact resolution API
API-first

Resolve phone numbers with real page context, confidence and alternatives.

QuickContact API helps browser workflows, CRMs, internal tools and operational systems turn a number plus local context into a better contact decision.

Built for context-aware resolution, browser plugins, internal operations and staged partner integrations.
POST /v1/resolve
Context-aware resolution High confidence Alternatives surfaced
{
  "rawNumber": "+351 253 601 200",
  "captureMode": "EXTENSION",
  "sourceType": "TEL_LINK",
  "origin": {
    "host": "www.uminho.pt",
    "title": "Contactos",
    "nearHeading": "Academic division"
  }
}
Primary result Academic Division · 0.92 confidence · grounded by page title, host and nearby heading.
Alternatives General Reception and Student Services remain visible when the context supports more than one plausible entity.
Designed for browser workflows

Good fit for extensions, operational tooling and CRM plugins that already see the page around the number.

Returns confidence, not false certainty

QuickContact prefers a grounded main result plus alternatives instead of pretending weak evidence is enough.

Separates API from consumer app

The API is the primary message here. The Android app is available as a separate testing and consumer flow.

What the API does

Context-aware contact resolution for real tooling.

QuickContact API combines the number with the surrounding evidence: source host, title, headings, labels, nearby text and other local signals that make contact resolution more reliable.

Resolve likely entities

Return a main result when the evidence is good enough, instead of forcing a number-only workflow every time.

Show alternatives

Keep plausible alternatives visible when the page context supports more than one candidate.

Track uncertainty honestly

Fall back conservatively when the context is weak, missing or inconsistent.

How it works

Capture context, resolve, review, then act.

The API is strongest when a number arrives together with local page context from a browser workflow or another source that already understands the surrounding page.

1

Capture a number

Start from a `tel:` link, tapped number, selected number or a controlled manual input path.

2

Attach local evidence

Send title, host, nearby labels, headings and compact excerpts instead of a blind number-only query.

3

Resolve with confidence

Use retrieval, structural grounding and semantic arbitration to produce a useful primary result.

4

Review or save

Consume the main result, alternatives and confidence to drive browser workflows, CRM actions or manual review.

Integration use cases

Built for teams, plugins and internal operations.

The API is suitable for workflows where a browser or tool already has access to the local page and needs a better entity suggestion than a plain number lookup can provide.

Browser extensions

Resolve numbers directly from web pages and offer better save flows without copying information across multiple tools.

CRM and helpdesk plugins

Turn inbound or discovered numbers into likely entities with confidence and alternatives before a record is created.

Internal operations tools

Support back-office teams, research flows and browser-assisted operations with a more reliable contact decision layer.

Why context helps

Most number tools start from the number alone.

QuickContact is most useful when the number arrives with the local clues already present in the page or browser flow. That is where better contact resolution actually becomes possible.

What that changes

Less guesswork, clearer uncertainty.

You get a primary result, alternatives and a clearer distinction between “strong enough to act” and “not enough evidence yet”.

API pricing

Plans for pilots, teams and production usage.

The public API is aimed at internal tools, browser workflows, CRM plugins and staged partner integrations. Consumer app access is handled separately.

Developer

Pilot

For early prototypes, internal tools and teams validating the workflow.

€59/ month
Up to 1,000 requests/month
No SLA
Best for pilots and demos
  • Context-aware resolution API access
  • Main result plus alternatives
  • Good fit for small teams and early testers
Growth

Production

For CRM plugins, internal platforms and early white-label deployments.

€499/ month
Up to 20,000 requests/month
Higher rate limits
Overage: €0.05 per request
  • Observability-oriented features
  • Faster support path
  • Built for broader internal adoption
Docs and operational links

Everything you need to evaluate the API.

Consumer app

Want to try the consumer app?

QuickContact for Android is available as a separate testing and consumer flow. Firefox + extension is the recommended path. Manual lookup remains available as fallback.

Open the app page

Prelaunch note

API-first here, app separately.

This homepage now explains the API first. The app remains real and available, but it no longer carries the main message of the site.

Get access

Request API access for real workflows.

Start with docs and pricing, then contact us for pilot access, internal tooling, browser integrations or staged partner deployments.