Install Jentic One Beta

Connect the Proovid Electronic Verification to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Proovid Electronic Verification, 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%2Fproovidapi.azurewebsites.net%2Fproovidapi-azurewebsites" | 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%2Fproovidapi.azurewebsites.net%2Fproovidapi-azurewebsites" | 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 Proovid Electronic Verification API.

Address_verifyById

Address_verifyCertificatePdf

Address_verifyByLevel

Address_createNaturalPersonElv

Address_linkResponse

GET STARTED

Start building with Proovid Electronic Verification API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Proovid Electronic Verification API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Proovid Electronic Verification to perform identity auth operations programmatically. The API provides 33 endpoints covering core functionality including address_verifybyid, address_verifybyid, address_verifycertificatepdf.

Call GET /api/Address/AddressVerification/{id} to address_verifybyid

Automated NaturalPerson Management

Automate naturalperson operations by combining multiple Proovid Electronic Verification endpoints. Agents can address_verifybyid and then address_verifycertificatepdf in a single workflow.

Call DELETE /api/Address/AddressVerification/{id} to address_verifybyid, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Proovid Electronic Verification endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'address_verifybyid', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

33 endpoints — proovid api is a restful application that specializes in electronic verification (proof of address and proof of identity) by employing an advanced risk-tiered approacch in combination with a smart risk assessment system.

METHOD

PATH

DESCRIPTION

GET

/api/Address/AddressVerification/{id}

Address_verifyById

DELETE

/api/Address/AddressVerification/{id}

Address_verifyById

GET

/api/Address/AddressVerification/{id}/certificate.pdf

Address_verifyCertificatePdf

POST

/api/Address/VerificationByLevel

Address_verifyByLevel

POST

/api/Address/NaturalPersonELV

Address_createNaturalPersonElv

POST

/api/Address/LinkResponse

Address_linkResponse

GET

/api/Document/DocumentVerification/{id}

Document_verifyStatus

DELETE

/api/Document/DocumentVerification/{id}

Document_verifyDeletion

GET

/api/Address/AddressVerification/{id}

Address_verifyById

DELETE

/api/Address/AddressVerification/{id}

Address_verifyById

GET

/api/Address/AddressVerification/{id}/certificate.pdf

Address_verifyCertificatePdf

POST

/api/Address/VerificationByLevel

Address_verifyByLevel

POST

/api/Address/NaturalPersonELV

Address_createNaturalPersonElv

POST

/api/Address/LinkResponse

Address_linkResponse

GET

/api/Document/DocumentVerification/{id}

Document_verifyStatus

DELETE

/api/Document/DocumentVerification/{id}

Why Jentic?

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

Setup

Wiring Proovid Electronic Verification by hand means setting its API key in the Authorization header, tracking verification ids across the address and document flows, and handling errors yourself. Through Jentic you install once, import Proovid Electronic Verification from the API Directory, store the key once, and your agent calls it.

Permission scoping

Proovid puts the verification id in the URL path (/api/Address/AddressVerification/{id} and /api/Document/DocumentVerification/{id}), so a rule can pin your agent to reading a specific verification. You choose the operations it may call, so destructive ones like deleting an address or document verification are not included unless you add them.

Credential isolation

Your Proovid Electronic Verification 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 'verify an address' or 'fetch a document verification result', and Jentic returns the matching Proovid operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Proovid Electronic Verification API through Jentic.

What authentication does the Proovid Electronic Verification use?

The Proovid Electronic Verification uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I address_verifybyid with the Proovid Electronic Verification?

Yes. Use the GET /api/Address/AddressVerification/{id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Proovid Electronic Verification?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I address_verifybyid through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'address_verifybyid'. Jentic returns the matching Proovid Electronic Verification operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Proovid Electronic Verification have?

The Proovid Electronic Verification exposes 33 endpoints covering naturalperson, address, document operations.

Can I limit what my agent is allowed to do with the Proovid Electronic Verification API?

Yes. Because Jentic One is self-hosted and you set its rules, you decide exactly which Proovid operations your agent may call and which API key it uses. Proovid puts the verification id in the URL path, such as /api/Address/AddressVerification/{id} and /api/Document/DocumentVerification/{id}, so a rule can pin the agent to reading a specific verification. Destructive operations like the DELETE on an address or document verification stay out of reach unless you explicitly grant them.

Proovidapi Proovid Electronic Verification

Name: Proovid Electronic Verification API
Brand: Proovid Electronic Verification
Availability: InStock

AI ReadinessNon-Ready (F)10/100

See full scorecard

Community OpenAPI document · agent-readyIdentity AuthAuthenticationapiKey33 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically address_verifybyid, address_verifybyid. Covers 33 operations with apiKey authentication.

Use for: I need to address_verifybyid, I want to address_verifybyid, Search for address_verifycertificatepdf, Find all address_verifybylevel

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Proovid API is a RESTful application that specializes in electronic verification (Proof of address and Proof of Identity) by employing an advanced risk-tiered approacch in combination with a smart Risk assessment system. <a href='docs/PROOVid_ELV.pdf' target='_blank'>More information</a>. The API exposes 33 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

88%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

100%

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.

48%

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: FSignals: 4

11%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Proovid Electronic Verification to your agent

Capabilities

Start building with Proovid Electronic Verification API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Proovidapi Proovid Electronic Verification

Jentic AI Readiness Score

Proovid Electronic Verification

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