Edge Background Check Connector

Name: Edge Background Check Connector API
Brand: Edge Background Check Connector
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic2 EndpointsREST

For Agents

Programmatically this endpoint will be used by edge to retrieve a list of available packages, this endpoint will be used by edge to initiate a background check. Covers 2 operations with basic authentication.

Connect the Edge Background Check Connector to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Edge Background Check Connector, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Edge Background Check Connector API.

This endpoint will be used by Edge to retrieve a list of available packages

Manage developer tools data programmatically

Integrate Edge Background Check Connector into automated workflows

Query and filter Edge Background Check Connector records by parameters

GET STARTED

Start building with Edge Background Check Connector API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Edge Background Check Connector, keeping it validated and agent-ready.

Edge Custom Background Check API Template. Use this template to help generate your API contracts so that you can connect with CSOD and become a custom background check provider. Detailed in this API are endpoints that should be implemented so that the contract can adhere to Edge Custom Background Check Provier standards. The API exposes 2 endpoints secured with basic authentication.

Use Cases

Patterns agents use Edge Background Check Connector API for, with concrete tasks.

★ Developer Tools Operations

Use the Edge Background Check Connector to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including this endpoint will be used by edge to retrieve a list of available packages, this endpoint will be used by edge to initiate a background check.

Call GET /api/Packages to this endpoint will be used by edge to retrieve a list of available packages

Data Retrieval and Monitoring

Query Edge Background Check Connector resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Edge Background Check Connector endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Edge Background Check Connector 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 basic tokens manually.

Search Jentic for 'this endpoint will be used by edge to retrieve a list of available packages', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — edge custom background check api template.

METHOD

PATH

DESCRIPTION

GET

/api/Packages

This endpoint will be used by Edge to retrieve a list of available packages

POST

/api/InitiateBackgroundCheck

This endpoint will be used by Edge to initiate a background check

GET

/api/Packages

This endpoint will be used by Edge to retrieve a list of available packages

POST

/api/InitiateBackgroundCheck

This endpoint will be used by Edge to initiate a background check

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Edge Background Check Connector basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'this endpoint will be used by edge to retrieve a list of available packages') and Jentic returns the matching Edge Background Check Connector operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Edge Background Check Connector integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Edge Background Check Connector API through Jentic.

What authentication does the Edge Background Check Connector use?

The Edge Background Check Connector uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I this endpoint will be used by edge to retrieve a list of available packages with the Edge Background Check Connector?

Yes. Use the GET /api/Packages endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Edge Background Check Connector?

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 this endpoint will be used by edge to retrieve a list of available packages through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'this endpoint will be used by edge to retrieve a list of available packages'. Jentic returns the matching Edge Background Check Connector operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Edge Background Check Connector have?

The Edge Background Check Connector exposes 2 endpoints covering initiatebackgroundcheck, packages operations.