Conturs Scoring API

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

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey2 EndpointsREST

For Agents

Submit a lead profile to Conturs and receive a 0-100 ICP fit score with factor-level reasoning. Agents call POST /leads with the API key and lead attributes.

Connect the Conturs Scoring API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Conturs Scoring API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Conturs Scoring API API.

Score a single lead against the configured ICP model via POST /leads

Receive a 0-100 fit score with factor-level breakdown for sales qualification

Probe API liveness with the GET /health endpoint before bulk scoring runs

Embed scoring directly inline in a CRM enrichment workflow without webhooks

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 scores inbound leads against a customer's personalised Ideal Customer Profile model and returns a 0-100 fit score with factor breakdowns. The API exposes two endpoints — a health probe and a POST /leads scoring call — so integration is small and predictable. Authentication is an API key passed in the request body alongside the lead payload.

Use Cases

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

★ Inbound Lead Qualification

Score every form submission, demo request, or trial signup against the company's ICP model before routing to sales. POST /leads returns a 0-100 score and factor breakdown so reps see exactly why a lead matched. Suited to revenue teams handling between dozens and thousands of inbound leads per week who need consistent, ICP-aligned prioritisation.

Submit a lead with email jane@acme.com, company Acme Inc, and title VP Engineering to POST /leads and return the fit score

CRM Enrichment Workflow

Plug Conturs scoring into the moment a contact is created in the CRM so the score lands on the record without manual review. The single POST /leads call slots into a Zapier or workflow step, returning a numeric score and factor list that can be written back to custom fields. Useful for ops teams that want lead grading visible directly on contact records.

When a new HubSpot contact is created, call Conturs POST /leads with the contact's email and company and write the returned score to the lead_score field

Batch Lead Backfill

Score historical leads stored in a CSV or warehouse against the current ICP model to find latent pipeline. Iterate through the dataset, call POST /leads per record, and write back the score and factor breakdown for sales follow-up. Fits one-off backfills of ten thousand leads or recurring weekly re-scoring as the ICP evolves.

Iterate through last quarter's 5,000 leads, call POST /leads for each, and write a new csv with the score and top factor

Agent-Driven Lead Triage via Jentic

Let an AI agent triage inbound leads through Jentic without hard-coding the Conturs URL. The agent searches Jentic for 'score a lead', loads the schema, and calls POST /leads with values pulled from the inbound payload. Through Jentic the API key sits in the vault, so the agent can run scoring loops without ever holding the secret in context.

Search Jentic for 'score a lead', load the Conturs schema, then score the latest inbound demo request and post the score to Slack

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 the api_key is injected into the request body — the raw key never enters the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'score a lead') and Jentic returns the matching Conturs POST /leads operation with its input schema, so the agent can build the request without browsing docs.

Time to first call

Direct Conturs integration: a few hours for 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 company and contact data that can feed into Conturs scoring inputs.

Use Clearbit before Conturs to fill missing firmographic fields on a lead, then score the enriched record.

Alternative

Apollo.io API

Sales intelligence platform with built-in lead scoring and contact data, broader scope than Conturs.

Choose Apollo when teams want sourcing plus scoring in one tool; pick Conturs when only ICP scoring is needed.

Complementary

Hunter API

Email finder and verification that supplies clean lead emails for Conturs scoring.

Pair with Conturs when inbound forms only capture company domain — Hunter resolves the email before scoring.

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 passed in the request body as the api_key field on each POST /leads call. There is no header-based or OAuth flow. Through Jentic the api_key is held in the vault and injected at execution time so it never appears in the agent's prompt context.

Can I score multiple leads in a single Conturs API call?

POST /leads is documented as the lead scoring endpoint in the spec. For multiple leads, iterate and call /leads per lead — the API surface is intentionally small (two endpoints total) and there is no documented batch operation.

What does the Conturs lead score actually return?

POST /leads returns a 0-100 fit score against your configured ICP model along with a factor breakdown explaining which lead attributes drove the score. Use the factor list to surface qualification reasoning to reps rather than a black-box number.

What are the rate limits for the Conturs Scoring API?

Rate limits are not declared in the OpenAPI spec. Treat the scoring endpoint as soft-limited per API key and respect HTTP 429 responses by backing off. Contact Conturs directly for documented limits on your plan.

How do I score a lead through Jentic?

Run jentic search for 'score a lead', load the returned Conturs POST /leads operation, then execute it with the lead's email, company, and title. Jentic injects the api_key from the vault and returns the score and factors as a structured result.