canonical: https://jentic.com/apis/companyproof.ai/companyproof

# CompanyProof REST API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Companies** — Resolve companies from a name or identifier and retrieve a structured profile by id
- **Intelligence** — Stream an adaptive intelligence query about a company
- **Verification** — Verify company claims and return a durable verification proof
- **Usage** — Inspect the account's current API allowance, shared across REST and MCP

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 75 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 80 / 100
- **View full report:** https://jentic.com/apis/companyproof.ai/companyproof/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Clearbit** — Company enrichment from firmographic and technographic data rather than claim verification with proofs.
- **Diffbot** — Knowledge graph of organizations built from the web, versus CompanyProof's resolution and verification.
- **People Data Labs** — Adds person-level data to the company records CompanyProof resolves and profiles.
- **ComplyAdvantage** — KYB and sanctions screening that pairs with CompanyProof's company resolution and claim proofs.

## FAQ

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