Install Jentic One Beta

Connect the Preuve Agent API to your agent

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

Start an asynchronous startup idea analysis with a clientRunId idempotency key and a starter or deep scanType

Poll an analysis for status, readyForExport, enrichment progress, and per-module statuses

Enrich a completed run with deep-only modules such as proofOfDemand, founderFit, playbook, trends, and community

Export a completed analysis as structured JSON at full or summary verbosity, including score, verdict, competitors, and market size

GET STARTED

Start building with Preuve Agent API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Preuve Agent API for, with concrete tasks.

★ Agent-run idea validation loop

An AI agent helping a founder decide what to build can run a full Preuve validation without custom client code. Through Jentic the agent searches for 'validate a startup idea', calls createAnalysis with a starter scanType and a clientRunId, polls getAnalysis until readyForExport is true, and pulls the exportAnalysis JSON for the score, verdict, competitors, and market size. Because starter scans cost nothing, the agent can exercise the whole loop before switching to deep runs.

POST /api/agent/analyses with clientRunId 'coffee-supply-001', scanType 'starter', and the idea text, poll GET /api/agent/analyses/{id} until readyForExport is true, then GET /api/agent/analyses/{id}/export with verbosity 'summary'

Shortlisting several ideas at once

A founder weighing a handful of directions wants them scored side by side. The analysis-batches route accepts up to 5 items, each with its own clientRunId, and can mix starter and deep scans in one batch. The batch export includes only completed, export-ready items and lists every skipped one in omittedItems with a reason, so the comparison never silently drops an idea.

POST /api/agent/analysis-batches with a batch clientRunId, scanType 'starter', and three items each carrying a unique clientRunId and idea, then GET /api/agent/analysis-batches/{batchId}/export and rank the items by score

Deepening a promising idea

Once a starter or deep run looks promising, the enrich operation generates missing core export sections and can start deep-only modules such as proofOfDemand, founderFit, playbook, trends, and community. founderFit underwrites the idea against a founder profile covering hours per week, runway months, and team status, so the export reflects whether this founder can realistically ship it.

POST /api/agent/analyses/{id}/enrich with modules ['founderFit', 'playbook'] and a founderProfile of hoursPerWeek 20 and runwayMonths 6, then re-export the analysis

Consultancy client reports

A consultant running an Agency workspace can create deep client reports through the API against the shared project quota, list every report in the workspace newest first with limit and offset paging, and export the structured JSON of each completed report for a client deliverable.

POST /api/agent/agency/analyses with a clientRunId and a client's idea description, poll GET /api/agent/agency/reports/{id} until it completes, then GET /api/agent/agency/reports/{id}/export

Key Endpoints

14 endpoints — the preuve agent api validates startup ideas programmatically, returning a 0-100 viability score, competitors, market sizing, and source-linked evidence drawn from more than 60 live sources.

METHOD

PATH

DESCRIPTION

POST

/api/agent/analyses

Start an idea analysis

GET

/api/agent/analyses/{id}

Poll an analysis

POST

/api/agent/analyses/{id}/enrich

Enrich a completed analysis

GET

/api/agent/analyses/{id}/export

Export an analysis as JSON

POST

/api/agent/analysis-batches

Start a batch of up to 5 analyses

POST

/api/agent/tools/idea-generator

Generate startup ideas

GET

/api/agent

Unauthenticated discovery document

POST

/api/agent/analyses

Start an idea analysis

GET

/api/agent/analyses/{id}

Poll an analysis

POST

/api/agent/analyses/{id}/enrich

Enrich a completed analysis

GET

/api/agent/analyses/{id}/export

Export an analysis as JSON

POST

/api/agent/analysis-batches

Start a batch of up to 5 analyses

POST

/api/agent/tools/idea-generator

Generate startup ideas

GET

/api/agent

Unauthenticated discovery document

Why Jentic?

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

Setup

Wiring Preuve by hand means sending the prv_ key in the x-preuve-key header, managing clientRunId idempotency, and writing the poll-until-readyForExport loop for asynchronous runs. Through Jentic you install once, import Preuve from the API Directory, store the key once, and your agent calls it.

Permission scoping

Preuve puts the analysis id in the URL path (/api/agent/analyses/{id}/...), so a rule can tie your agent to the analysis routes it needs. You choose which operations it may call, so quota-spending ones like createAgencyAnalysis or deep batch creation are not included unless you add them.

Credential isolation

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

Intent-based discovery

Agents search Jentic by intent such as 'validate a startup idea' or 'export an idea report', and Jentic returns the matching Preuve operation with its input schema, including clientRunId and scanType, so the agent calls the right endpoint without reading the docs.

FAQs

Specific to using Preuve Agent API through Jentic.

What authentication does the Preuve Agent API use?

Per its OpenAPI spec, the Preuve Agent API authenticates with an API key (prefixed prv_) sent as-is in the x-preuve-key header, with no signing and no bearer token. The discovery document at GET /api/agent is unauthenticated, while the analysis, batch, idea generator, and Agency operations expect the key. Through Jentic the key is held by your own instance and attached to each call.

Can I validate a startup idea for free with the Preuve Agent API?

Yes. Setting scanType to starter on POST /api/agent/analyses costs nothing and returns a real report, which makes it the sandbox for the create, poll, enrich, and export loop. A scanType of deep runs the full paid analysis and consumes account quota.

What are the rate limits for the Preuve Agent API?

The OpenAPI spec states that the idea generator gives free accounts 5 generations per rolling 24 hours and paid accounts a fair-use ceiling of 20 per rolling 24 hours. Rate-limited calls answer 429 with RATE_LIMITED and a Retry-After header. The unauthenticated GET /api/agent discovery document lists the current limits, and https://docs.preuve.ai/ has the full details.

Is there a Preuve MCP server?

You don't need an MCP server to give your agent the Preuve Agent API. Jentic connects it directly from the API Directory: import it, store your x-preuve-key once, and your agent calls the analysis operations on demand without loading another server's tool definitions into its context.

How do I validate an idea and export the report through Jentic?

Search Jentic for 'validate a startup idea', load createAnalysis, and execute it with a clientRunId, a scanType, and the idea text. Poll getAnalysis with the returned id until readyForExport is true, then call exportAnalysis for the structured JSON. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows createAnalysis, getAnalysis, and exportAnalysis and leaves out createAgencyAnalysis, so the agent can run and read personal validations but cannot spend shared Agency project credits. Every call it makes is logged for review.

Preuve Agent API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey14 EndpointsREST

For Agents

Score a startup idea from 0-100 with competitors, market size, and cited evidence, then export the report as structured JSON. Starter scans cost nothing, so an agent can run the full create, poll, enrich, export loop as a sandbox.

Use for: I need to validate a startup idea before building it, Get the viability score and competitors for my product idea, Check whether an analysis run is ready for export, Retrieve the structured JSON report for a completed analysis

Not supported: Does not build products, register companies, or raise funding. Use for scoring and researching startup ideas only.

The Preuve Agent API validates startup ideas programmatically, returning a 0-100 viability score, competitors, market sizing, and source-linked evidence drawn from more than 60 live sources. Analyses run asynchronously: you start one with a clientRunId idempotency key and a scanType of starter (no cost) or deep (paid quota), poll it, enrich the completed run with deep-only modules such as proofOfDemand, founderFit, or playbook, and export a structured JSON report. Batches of up to 5 ideas, a synchronous idea generator, and Agency workspace client reports round out the surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

30%

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: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

73%

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

55%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

52%

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: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Preuve Agent API to your agent

Capabilities

Start building with Preuve Agent API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Preuve Agent API

Jentic AI Readiness Score

Preuve Agent 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