Install Jentic One Beta

Connect the leadtributor.cloud - API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the leadtributor.cloud - 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%2Fleadtributor.cloud%2Fleadtributor" | 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%2Fleadtributor.cloud%2Fleadtributor" | 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 leadtributor.cloud - API.

Create a lead from a prospect and interest field list and commission it to a sales partner, optionally into a specific salesPipelineId

Offer a lead on a market so the platform brokers it to relevant sales partners

List leads filtered by commission.stepName, commission.responsible, commission.closedAt, or lead.createdAt, and sort by modifiedAt

Find likely duplicates of a lead with a 0 to 100 score, tuned by maxDistanceKm and minScore

GET STARTED

Start building with leadtributor.cloud - API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use leadtributor.cloud - API for, with concrete tasks.

★ Agent-run lead routing through Jentic

An AI agent handling inbound enquiries can create each lead in Leadtributor, check it for duplicates, and commission it to the right sales partner. Through Jentic the agent finds each operation by intent and the Authorization header key is injected at execution time, and a rule can allow lead creation and commissioning while leaving partner deletion and webhook changes out of reach.

Call POST /leads with the prospect and interest field lists from the web form, call GET /leads/{leadId}/duplicates with minScore 80, and if none are returned call POST /leads/{leadId}/commissions with the chosen salesPartnerId

Partner channel lead distribution

Manufacturers selling through dealers, installers, or resellers need each lead to reach a partner who can act on it. Leadtributor supports direct commissioning to a named sales partner and pipeline, and market-based brokerage where a lead is offered on a market and distributed to relevant partners.

Call POST /markets/{marketId}/brokerages with the leadId of the new enquiry to offer it on the regional market

Commission progress reporting

Once leads are with partners, the brand wants to know what happened to them. Listing leads with filters on commission.stepName, commission.responsibleName, commission.startedAt, and commission.closedAt shows where each lead stands in the partner's process, and notes added by either side carry the context.

Call GET /leads with a commission.closedAt filter for the current month and includeFieldLists true, then summarise closed leads by partner

Sales partner network management

A partner network changes as dealers join and leave. The sales partner operations invite a partner by email with optional tags and attributes, list partners by status such as ACTIVE, PENDING:INVITED, or ENDED, update their tags and attributes, and end or delete a relationship.

Call POST /sales-partners with email 'dealer@example.com', name 'Example Solar GmbH', and tags ['bavaria'], then list partners with GET /sales-partners and status 'PENDING:INVITED' to confirm the invite

Key Endpoints

22 endpoints — the leadtributor api distributes sales leads from a manufacturer or brand to its network of sales partners and tracks how each lead progresses with the partner it went to.

METHOD

PATH

DESCRIPTION

POST

/leads

Create a lead

GET

/leads

List leads

POST

/leads/{leadId}/commissions

Commission a lead to a sales partner

POST

/markets/{marketId}/brokerages

Offer a lead on a market

GET

/leads/{leadId}/duplicates

Get duplicate candidates

POST

/sales-partners

Invite a sales partner

POST

/webhooks

Subscribe a webhook

POST

/leads

Create a lead

GET

/leads

List leads

POST

/leads/{leadId}/commissions

Commission a lead to a sales partner

POST

/markets/{marketId}/brokerages

Offer a lead on a market

GET

/leads/{leadId}/duplicates

Get duplicate candidates

POST

/sales-partners

Invite a sales partner

POST

/webhooks

Subscribe a webhook

Why Jentic?

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

Setup

Wiring Leadtributor by hand means sending the key in the Authorization header, keeping production and demo hosts apart, building prospect and interest field lists with typed fields, and running the two-step attachment upload. Through Jentic you install once, import Leadtributor from the API Directory, store the key once, and your agent calls it.

Permission scoping

Leadtributor puts the lead, market, and sales partner ids in the URL path (/leads/{leadId}/commissions, /sales-partners/{salesPartnerId}), so a rule can pin your agent to one lead, market, or partner and the operations you pick. You choose the operations it may call, so destructive ones like deleting a sales partner or unsubscribing a webhook are not included unless you add them.

Credential isolation

Your Leadtributor 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 'commission a lead to a sales partner' or 'find duplicate leads', and Jentic returns the matching Leadtributor operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using leadtributor.cloud - API through Jentic.

Is there a Leadtributor MCP server?

You don't need an MCP server to give your agent the Leadtributor API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so your agent's context carries no tool definitions it will not use.

What authentication does the Leadtributor API use?

Per its OpenAPI spec, the Leadtributor API uses an API key sent in the Authorization header, declared as the apiKey scheme. The spec lists a production host and a separate demonstration platform host, so use the key that belongs to the platform you call. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time.

Can I detect duplicate leads with the Leadtributor API?

Yes. GET /leads/{leadId}/duplicates returns potential duplicates of a lead, each with a score from 0 for no match to 100 for an exact match and the criteria that matched, covering email, name, company, and location. Use minScore to drop weak candidates and maxDistanceKm to bound location matching.

What are the rate limits for the Leadtributor API?

The OpenAPI spec does not specify rate limits. Check https://developer.leadtributor.cloud for current limits.

How do I send a lead to a sales partner through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Leadtributor API from the directory, and store your API key. Your agent then searches for 'commission a lead to a sales partner' and Jentic returns POST /leads/{leadId}/commissions, which requires salesPartnerId and accepts an optional salesPipelineId. To run it on your own infrastructure, install Jentic One from its GitHub repo.

How do I attach a file to a Leadtributor lead?

It takes two steps. Call POST /leads/{leadId}/attachments to announce the upload, then send the file as a multipart/form-data POST to the uploadUrl in the response, along with the fields it returned.

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

Yes. For an intake assistant, write a rule that allows POST /leads, GET /leads/{leadId}/duplicates, and POST /leads/{leadId}/notes: the agent can create leads, check for duplicates, and add notes, but cannot commission leads, invite or delete partners, or change webhooks, and every call it makes is logged.

leadtributor.cloud - API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMDeal PipelineapiKey (Authorization header)22 EndpointsREST

For Agents

Create sales leads, commission them to sales partners and pipelines or offer them on a market, track commission progress, detect duplicate leads, and manage your sales partner network.

Use for: I need to send this inbound lead to our dealer in Munich, Create a lead for a prospect asking about solar panel installation, List all leads whose commission was closed this month, Check whether this lead is a duplicate of one we already have

Not supported: Does not handle email marketing, quoting or invoicing, partner payouts, or contact enrichment. Use for creating leads and distributing them to sales partners and markets only.

The Leadtributor API distributes sales leads from a manufacturer or brand to its network of sales partners and tracks how each lead progresses with the partner it went to. A lead is created from two field lists, the prospect and their interest, and can then be commissioned directly to a sales partner and sales pipeline, or offered on a market so the platform brokers it to relevant partners. The API also lists leads filtered by commission step, responsible person, and dates, finds likely duplicate leads with a 0 to 100 match score, adds notes and attachments, invites and manages sales partners, and subscribes webhooks to platform events.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

78%

Example Validity

Percentage of examples that conform to their schemas.

44%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

45%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

95%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the leadtributor.cloud - API to your agent

Capabilities

Start building with leadtributor.cloud - API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

leadtributor.cloud - API

Jentic AI Readiness Score

leadtributor.cloud - Api

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness