Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fconturs.com%2Fconturs" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fconturs.com%2Fconturs" | 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.

Score leads against your ideal customer profile with a 0-100 quality rating

Get a factor breakdown showing what drove each lead's score

Submit multiple leads in a single scoring request

Check service health before running a scoring batch

Use Cases

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

GET STARTED

Start building with Conturs Scoring API

Explore with Jentic One

View OpenAPI Document

★ Agent-Driven Lead Triage

An AI agent connected through Jentic can take a batch of newly captured leads, send them to Conturs for scoring, and route only the high-fit ones to a sales rep. Because each result carries a 0-100 quality score and a factor breakdown, the agent can explain its routing decision and let the team focus on the leads most likely to convert.

Send a batch of ten inbound leads to Conturs, read the quality score for each, and forward the leads scoring above 70 to the sales queue

Inbound Lead Prioritization

Marketing teams capture more leads than sales can call, so ordering the queue by fit matters. The Conturs Scoring API evaluates each lead against the ideal customer profile and returns a 0-100 quality score, letting a workflow sort a day's inbound leads so reps work the strongest fits first.

Score today's inbound leads and sort them from highest to lowest quality score for the sales team's call list

CRM Fit-Score Annotation

Sales operations want a fit signal stored next to each lead record. The Conturs Scoring API returns a quality score and factor breakdown that an integration can write back into a CRM, so every lead carries an ICP-fit rating without a rep judging it by hand.

Score a lead, then write its quality score and top contributing factor back onto the matching CRM lead record

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 batch of leads against the ideal customer profile

GET

/health

Check that the scoring service is available

POST

/leads

Score a batch of leads against the ideal customer profile

GET

/health

Check that the scoring service is available

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Conturs by hand means handling its API key plus the account email the request expects and shaping the lead batch it scores. Through Jentic you install once, import Conturs from the API Directory, store the key once, and your agent calls the scoring operation.

Permission scoping

Conturs carries lead data in the request body rather than a URL path, so a rule bounds which operations your agent may call, not which leads it sees. You can allow only the scoring operation, keeping the agent to scoring and health checks.

Credential isolation

Your Conturs API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'score leads against our ICP', and Jentic returns the matching Conturs operation with its input schema so the agent calls it with the right lead fields.

FAQs

Specific to using Conturs Scoring 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. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What authentication does the Conturs Scoring API use?

The Conturs Scoring API authenticates with an API key per its OpenAPI spec, sent with the request alongside the account email address. Through Jentic the key is stored once by your own self-hosted instance and injected when the agent calls, so it never appears in the agent's prompt or logs.

Is there a Conturs MCP server?

You don't need an MCP server to give your agent the Conturs Scoring API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the scoring operation. Operations are discovered on demand, so nothing extra loads into the agent's context.

Can I limit what my agent is allowed to do with the Conturs Scoring API?

Yes. Conturs exposes a lead-scoring operation and a health check, and it carries lead data in the request body, so a rule bounds which operations the agent may call rather than which records it touches. Allow only the scoring operation, and the agent can score leads and check service health but nothing more, with every call logged.

Can I score multiple leads in one request with the Conturs Scoring API?

Yes. The scoring operation accepts a batch of leads in a single request and returns a 0-100 quality score with a factor breakdown for each lead, so you can rank a whole queue without one call per lead.

What are the rate limits for the Conturs Scoring API?

The OpenAPI spec does not specify rate limits. Check the Conturs documentation at https://conturs.com for current limits and batch-size guidance before running large scoring jobs.

How do I score leads with the Conturs Scoring API through Jentic?

Search Jentic by intent, for example 'score leads against our ICP', and Jentic returns the scoring operation with its input schema. Your agent submits the leads and reads back each quality score and factor breakdown. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Conturs Scoring API

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

Agent-ready OpenAPI document · curated by JenticAI/MLMl InferenceapiKey2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Score a batch of leads against your ideal customer profile and get a 0-100 quality score plus a factor breakdown for each. Authenticates with an API key.

Use for: Score a list of inbound leads against our ideal customer profile, Rank these leads by fit so sales calls the best ones first, Get the score and factor breakdown for one lead, Check whether the scoring service is up before I send a batch

Not supported: Does not handle lead enrichment, email outreach, or CRM storage. Use for AI lead fit scoring only.

Jentic publishes the only available OpenAPI specification for Conturs Scoring API, keeping it validated and agent-ready. The Conturs Scoring API scores inbound leads against your ideal customer profile using AI-driven ICP matching, returning a 0-100 quality score and a factor breakdown for each lead. It accepts a batch of leads in a single scoring request and exposes a health check for monitoring.

Jentic One on Github View OpenAPI Document