Conturs Scoring API

Name: Conturs Scoring API API
Brand: Conturs Scoring API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey2 EndpointsREST

For Agents

Score leads against an AI-powered ICP model and receive a 0-100 quality score with factor breakdown. Agents call POST /leads with the api_key, email, and lead attributes.

Quickstart

Get started with Conturs Scoring API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"score a lead against my icp"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Conturs Scoring API API.

Score a lead against the configured ICP model and return a 0-100 quality score

Receive a factor-level breakdown explaining the score for sales qualification

Probe service availability with the GET /health endpoint before scoring runs

Authenticate per-call using the api_key plus email pattern in the request body

GET STARTED

Start building with Conturs Scoring API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Conturs Scoring API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Conturs Scoring API, keeping it validated and agent-ready. Conturs is a lead scoring service that uses AI-powered ICP matching to evaluate leads with a 0-100 quality score and factor breakdown. The API exposes a POST /leads endpoint for scoring and a GET /health endpoint for service checks. Authentication is an API key sent in the request body alongside an email field for caller identification.

Use Cases

Patterns agents use Conturs Scoring API API for, with concrete tasks.

★ AI-Powered Inbound Lead Qualification

Score every form submission, signup, or demo request through Conturs to filter strong-fit leads from noise. POST /leads returns a 0-100 score plus factor breakdown so SDRs see exactly which ICP traits matched. Suited to teams handling several hundred to several thousand inbound leads per month who want consistent grading without manual rules.

Send a lead with email jane@acme.com, company Acme Inc, and title VP Engineering to POST /leads and surface the top three matching factors

Sales Pipeline Triage

Apply Conturs scoring to refresh priorities across an active pipeline, surfacing previously deprioritised leads that match an updated ICP. Iterate over the list and call POST /leads per record, then sort by score to focus rep effort on the strongest fits. Useful when go-to-market focus shifts or the ICP definition is tuned.

Score the 200 open leads in stage 'New' via POST /leads and tag any with a score above 80 as 'hot'

Form-to-Score Webhook

Wire a marketing form submission directly to Conturs so the score lands on the lead record before the rep ever sees it. The single POST /leads call fits inside a no-code workflow step and returns the score and factors in milliseconds. Removes the lag between submission and prioritisation.

On a Webflow form submission, call POST /leads with the submitted email and company and add a 'high-fit' tag if the score is above 75

Agent-Driven ICP Scoring via Jentic

An AI agent triages inbound leads through Jentic by searching for the scoring intent, loading the Conturs schema, and calling POST /leads with extracted attributes. Through Jentic the api_key is injected from the vault, so the agent runs scoring loops continuously without ever holding the secret in its prompt context.

Search Jentic for 'score a lead', load the Conturs schema, then score the most recent inbound lead and post the score and factors to a Slack channel

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for conturs scoring api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/leads

Score a lead against the configured ICP model

GET

/health

Health check endpoint

POST

/leads

Score a lead against the configured ICP model

GET

/health

Health check endpoint

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Conturs API keys are stored encrypted in the Jentic vault. Agents receive scoped access at execution time, and Jentic injects the api_key and email into the POST /leads body so the raw secret never enters the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'score a lead against my ICP') and Jentic returns the matching Conturs operation with its input schema, so the agent constructs valid requests without browsing docs.

Time to first call

Direct Conturs integration: a few hours for body-auth wiring and field mapping. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Clearbit API

Enriches firmographic and contact attributes that feed into Conturs scoring inputs.

Use Clearbit before Conturs when inbound forms capture only an email — enrich, then score the fuller record.

Alternative

Apollo.io API

Sales intelligence with prospecting plus its own scoring, broader scope than Conturs.

Choose Apollo when teams want sourcing and scoring in one tool; pick Conturs for ICP-only scoring on existing leads.

Complementary

Hunter API

Finds and verifies business emails so Conturs receives clean inputs for scoring.

Pair with Conturs when only the company domain is captured — Hunter resolves the email before scoring runs.

FAQs

Specific to using Conturs Scoring API API through Jentic.

Why is there no official OpenAPI spec for Conturs Scoring API?

Conturs does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Conturs Scoring API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Conturs Scoring API use?

The API uses an api_key sent in the request body together with an email field on each POST /leads call. There is no Authorization header or OAuth handshake. Through Jentic the api_key is stored in the vault and injected at execution time so it never enters the agent's prompt.

What does a Conturs lead score include?

POST /leads returns a 0-100 quality score against your AI-trained ICP model plus a factor breakdown showing which lead attributes drove the result. The factor list lets reps see qualification reasoning rather than treating the score as a black box.

Can I score leads in bulk with the Conturs API?

The spec exposes only POST /leads and GET /health. There is no documented batch endpoint, so for bulk scoring iterate per lead with POST /leads. Throttle calls and respect HTTP 429 responses if rate limiting kicks in.

What are the rate limits for the Conturs Scoring API?

Rate limits are not declared in the OpenAPI spec. Assume the scoring endpoint is soft-limited per api_key and back off on HTTP 429 responses. Contact Conturs for documented limits on your plan.

How do I score a lead through Jentic?

Run jentic search for 'score a lead against my ICP', load the Conturs POST /leads operation, then execute it with the lead's email, company, and any known attributes. Jentic injects the api_key and email from the vault and returns the score and factor breakdown as a structured result.