Install Jentic One Beta

Connect the Configuration APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Configuration APIs, 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%2Fpropexo.com%2Fpropexo" | 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%2Fpropexo.com%2Fpropexo" | 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 Configuration APIs.

Get all data diffs

Query write job logs

Create an integration

Use Cases

Patterns agents use Configuration APIs for, with concrete tasks.

★ Developer Tools Operations

Use the Configuration APIs to perform developer tools operations programmatically. The API provides 33 endpoints covering core functionality including get all data diffs, get log by id, get a link to the job log raw request and response data of a write job..

GET STARTED

Start building with Configuration APIs

Explore with Jentic One

View OpenAPI Document

Automated Admin Management

Automate admin operations by combining multiple Configuration APIs endpoints. Agents can get log by id and then get a link to the job log raw request and response data of a write job. in a single workflow.

Call GET /v1/admin/job-logs/{job_log_id}/ to get log by id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Configuration APIs 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 bearer tokens manually.

Search Jentic for 'get all data diffs', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

33 endpoints — propexo.

METHOD

PATH

DESCRIPTION

GET

/v1/admin/data-diffs/

Get all data diffs

GET

/v1/admin/job-logs/{job_log_id}/

Get log by ID

GET

/v1/admin/job-logs/{job_log_id}/data

Get a link to the job log raw request and response data of a write job.

GET

/v1/admin/logs/writes/

Query write job logs

GET

/v1/admin/logs/jobs/

Get logs

GET

/v1/admin/logs/jobs/{id}

Get logs by job ID

POST

/v1/admin/integrations/

Create an integration

GET

/v1/admin/integrations/

Get all my integrations

GET

/v1/admin/data-diffs/

Get all data diffs

GET

/v1/admin/job-logs/{job_log_id}/

Get log by ID

GET

/v1/admin/job-logs/{job_log_id}/data

Get a link to the job log raw request and response data of a write job.

GET

/v1/admin/logs/writes/

Query write job logs

GET

/v1/admin/logs/jobs/

Get logs

GET

/v1/admin/logs/jobs/{id}

Get logs by job ID

POST

/v1/admin/integrations/

Create an integration

GET

/v1/admin/integrations/

Get all my integrations

Why Jentic?

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

Setup

Wiring the Propexo Configuration APIs by hand means setting bearer auth, choosing the production or sandbox host, and reading job logs and data diffs yourself. Through Jentic you install once, import the Configuration APIs from the API Directory, store the token once, and your agent calls it.

Permission scoping

Propexo puts the job log id in the URL path (/v1/admin/job-logs/{job_log_id}/), so a rule can pin your agent to reading a specific job log and its data. You choose the operations it may call, so writes like creating an integration are not included unless you add them.

Credential isolation

Your Propexo Configuration APIs token 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 'list data diffs' or 'read a job log', and Jentic returns the matching Propexo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Configuration APIs through Jentic.

What authentication does the Configuration APIs use?

The Configuration APIs uses a Bearer token 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 get all data diffs with the Configuration APIs?

Yes. Use the GET /v1/admin/data-diffs/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Configuration APIs?

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 get all data diffs through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get all data diffs'. Jentic returns the matching Configuration APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Configuration APIs have?

The Configuration APIs exposes 33 endpoints covering admin, webhooks operations.

Can I limit what my agent is allowed to do with the Propexo Configuration API?

Yes. Jentic One runs self-hosted, so you set the rules that decide which Propexo operations and credentials your agent may use. Because Propexo carries the job log id in the URL path (for example GET /v1/admin/job-logs/{job_log_id}/), you can pin the agent to reading a specific job log and its raw request and response data. You choose the operations it may call, so a write like POST /v1/admin/integrations/ to create an integration is not included unless you add it.

Propexo Configuration APIs

Name: Configuration APIs
Brand: Configuration APIs
Availability: InStock

AI ReadinessNon-Ready (C)56/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer33 EndpointsREST

For Agents

Programmatically get all data diffs, get log by id. Covers 33 operations with bearer authentication.

Use for: I need to all data diffs, I want to log by id, Search for a link to the job log raw request and response data of a write job., Find all query write job logs

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

propexo.com/main version 1.0.0. The API exposes 33 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4

29%

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

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.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

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

67%

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.

57%

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

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Configuration APIs to your agent

Capabilities

Use Cases

Start building with Configuration APIs

Key Endpoints

Why Jentic?

Related APIs

FAQs

Propexo Configuration APIs

Jentic AI Readiness Score

Configuration APIs

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