Install Jentic One Beta

Connect the CompanyProof REST API to your agent

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

Resolve a company from a name or identifier to a canonical match

Retrieve a structured company profile by id

Stream an adaptive intelligence query about a company

Verify company claims and create a durable verification proof

Inspect your current API usage and allowance

GET STARTED

Start building with CompanyProof REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CompanyProof REST API for, with concrete tasks.

★ Agent Resolves and Profiles a Company

An AI agent connected to the CompanyProof REST API can turn a messy company name into a canonical record and read its profile. It calls the search endpoint to resolve the name to a company id, then retrieves the structured profile by that id, so downstream steps work from a resolved entity rather than a free-text string. This gives an agent a reliable starting point for any company-centric task.

Search for the company named Acme Corp, take the top resolved id, and retrieve its structured profile

Claim Verification with a Durable Proof

When a company asserts something that matters, the CompanyProof REST API verifies the claim and returns a durable verification proof that can be stored and referenced later. An agent reviewing a vendor's stated certifications or facts can submit them to the verify endpoint and keep the proof, so the check is auditable rather than a one-off result that disappears.

Submit a company's stated claims to the verify endpoint and store the durable verification proof it returns

Adaptive Intelligence Query

Beyond a static profile, the CompanyProof REST API streams an adaptive intelligence query about a company, so an agent can ask a specific question and receive a response as it is generated. A research agent can pose a targeted question about a company and consume the streamed answer, rather than fetching a whole profile and parsing it for the one fact it needs.

Stream an intelligence query asking about a company's primary business lines and summarize the response

API Allowance Monitoring

Because REST and MCP share account-wide rate and usage limits, an agent needs to know where it stands. The CompanyProof REST API's usage endpoint reports the current allowance, so an agent can check remaining capacity before a batch of resolutions or verifications and pace itself to stay within the plan.

Read the usage endpoint and report the remaining allowance before starting a batch of company verifications

Key Endpoints

5 endpoints — the companyproof rest api resolves companies from a name or identifier, retrieves structured company profiles by id, and streams adaptive intelligence queries about a company.

METHOD

PATH

DESCRIPTION

POST

/v2/companies/search

Resolve companies

GET

/v2/companies/{id}/profile

Retrieve a company profile

POST

/v2/intelligence/query

Stream an intelligence query

POST

/v2/claims/verify

Verify company claims

GET

/v2/usage

Inspect the current API allowance

POST

/v2/companies/search

Resolve companies

GET

/v2/companies/{id}/profile

Retrieve a company profile

POST

/v2/intelligence/query

Stream an intelligence query

POST

/v2/claims/verify

Verify company claims

GET

/v2/usage

Inspect the current API allowance

Why Jentic?

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

Setup

Wiring the CompanyProof REST API by hand means handling its cp_live_ or cp_test_ bearer key, keeping test keys isolated from live claim verification, and watching the account-wide usage limits. Through Jentic you install once, import CompanyProof from the API Directory, store the key once, and your agent calls it.

Permission scoping

CompanyProof puts the company id in the URL path (/v2/companies/{id}/profile), so a rule can pin your agent to the search and profile reads you need. You can let it resolve and read company profiles without granting the claim-verification or intelligence operations.

Credential isolation

Your CompanyProof 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 'resolve a company' or 'verify company claims', and Jentic returns the matching CompanyProof operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CompanyProof REST API through Jentic.

What authentication does the CompanyProof REST API use?

The CompanyProof REST API authenticates with a bearer token per its OpenAPI spec: an API key prefixed cp_live_ or cp_test_, sent as an Authorization: Bearer header and kept server-side. All endpoints require a key; test keys are isolated to fixture verification while live keys verify real-company claims, and search, profile, and intelligence need an active access tier. Through Jentic the key is stored once by your own self-hosted instance and injected at call time, so it never sits in your agent's prompt or logs.

Is there a CompanyProof MCP server?

Yes - CompanyProof is reachable over MCP, which shares the account's rate and usage limits with the REST API. You can also connect CompanyProof directly through Jentic: your agent gets the full 5-endpoint surface, including resolve, profile, and claim verification, without loading another server's tool definitions into its context, your API key is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call.

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

Yes. Write a rule that allows only the company search and profile reads, so the agent can resolve and read companies but cannot run intelligence queries or submit claim verifications. The calls it makes are logged, so you can audit exactly what the agent touched.

Can I verify company claims with the CompanyProof REST API?

Yes. Call POST /v2/claims/verify with the claims to check and the API returns a durable verification proof you can store and reference later. Resolve the company first with POST /v2/companies/search and read its profile with GET /v2/companies/{id}/profile so the verification runs against the right entity.

What are the rate limits for the CompanyProof REST API?

The OpenAPI spec does not state a fixed per-second rate limit, and notes that REST and MCP share account-wide rate and usage limits. GET /v2/usage reports the current allowance so an agent can check remaining capacity. Check the documentation at https://companyproof.ai for current plan limits.

How do I resolve a company with the CompanyProof REST API through Jentic?

Search Jentic for 'resolve a company' and it returns the POST /v2/companies/search operation with its input schema. Pass the company name or identifier and the agent gets back the resolved company id to profile or verify. To run it on your own infrastructure, install Jentic One from its GitHub repo.

CompanyProof REST API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer5 EndpointsREST

For Agents

Resolve companies, retrieve structured profiles, stream intelligence queries, and verify company claims with a durable proof. Reports the account's current API allowance.

Use for: Resolve a company name to a canonical company record, Get a structured profile for a company by id, Verify a claim a company is making, Create a durable proof that a company claim checked out

Not supported: Does not screen individuals, run background checks, or store your own CRM records. Use for company resolution, profiles, intelligence, and claim verification only.

The CompanyProof REST API resolves companies from a name or identifier, retrieves structured company profiles by id, and streams adaptive intelligence queries about a company. It verifies company claims and returns a durable verification proof, and reports the account's current API allowance. Live keys verify real-company claims, while test keys are isolated to fixture verification.

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).

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.

75%

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

41%

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.

50%

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: B-Signals: 1

60%

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

80%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CompanyProof REST API to your agent

Capabilities

Start building with CompanyProof REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CompanyProof REST API

Jentic AI Readiness Score

CompanyProof REST 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