Install Jentic One Beta

Connect the Catchpoint API to your agent

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

List the synthetic monitoring tests in an account

Retrieve a single test by its identifier

Read all sections of a test's configuration

Update a test's configuration

Use Cases

Patterns agents use Catchpoint API for, with concrete tasks.

GET STARTED

Start building with Catchpoint API

Explore with Jentic One

View OpenAPI Document

Monitoring Configuration Management

Teams keep synthetic tests consistent by reading a test's sections and updating its configuration when standards change. The API returns the full test definition and accepts an update for one test at a time. This suits rolling a configuration change across many tests in a controlled pass.

Read a test's current sections, apply a configuration change, and submit the updated test

Coverage Reporting

An agent builds a report of what monitoring exists by listing all tests and summarizing their sections. This gives stakeholders a current picture of monitoring coverage without opening the portal. It runs as a recurring digest of the account's synthetic tests.

List all tests and produce a summary of their sections as a monitoring coverage report

Key Endpoints

4 endpoints — the catchpoint api lists and inspects synthetic monitoring tests, retrieves a single test and all of its sections, and updates a test's configuration.

METHOD

PATH

DESCRIPTION

GET

/ui/api/v1/tests

List monitoring tests

GET

/ui/api/v1/tests/{id}

Retrieve a test by identifier

POST

/ui/api/v1/tests/{id}

Update a test's configuration

GET

/ui/api/v1/tests/{id}/allSections

Read all sections of a test

GET

/ui/api/v1/tests

List monitoring tests

GET

/ui/api/v1/tests/{id}

Retrieve a test by identifier

POST

/ui/api/v1/tests/{id}

Update a test's configuration

GET

/ui/api/v1/tests/{id}/allSections

Read all sections of a test

Why Jentic?

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

Setup

Wiring the Catchpoint API by hand means learning its test object shape and building calls to list, read, and update tests and their sections. Through Jentic you install once, import Catchpoint from the API Directory, and your agent lists and updates tests.

Permission scoping

Catchpoint puts the test identifier in the URL path, so a rule can bound your agent to a single test. You can also scope by operation, allowing listing and reading while withholding the update, and every call the agent makes is logged.

Credential isolation

The Catchpoint spec does not declare a security scheme, so no secret is required to call it as described. Where a deployment fronts the API with a key, Jentic holds that secret encrypted in your own Jentic One instance and attaches it at execution time, so it never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list monitoring tests' or 'update a test', and Jentic returns the matching Catchpoint operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Catchpoint API through Jentic.

What authentication does the Catchpoint API use?

The Catchpoint API's OpenAPI spec does not declare a security scheme, so authentication is not described in the spec itself. Consult the Catchpoint documentation for how to authenticate in production; where a secret is required, Jentic holds it encrypted in your own Jentic One instance and attaches it at call time.

Can I update a monitoring test with the Catchpoint API?

Yes. The API lets you read a test and all of its sections and then submit an updated configuration for that test. An agent can adjust one test at a time as part of a controlled change.

What are the rate limits for the Catchpoint API?

The OpenAPI spec does not specify rate limits. Check the Catchpoint documentation at https://io.catchpoint.com for current limits and usage guidance.

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

Yes. Because the test identifier sits in the URL path, a rule can bound your agent to a single test, and you can scope by operation to allow listing and reading while withholding the update. You choose which operations it may call, and every call is logged.

How do I audit Catchpoint tests through Jentic?

Search Jentic for 'list monitoring tests', add the Catchpoint API from the directory, and your agent then lists tests and reads their sections. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Catchpoint MCP server?

You don't need an MCP server to give your agent the Catchpoint API. Jentic connects it directly from the API Directory: import it and your agent lists, reads, and updates tests. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

Catchpoint API

AI ReadinessFoundational (D+)49/100

See full scorecard

Community OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilitynone4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List Catchpoint synthetic monitoring tests, read a single test and its sections, and update a test's configuration. Returns test definitions for an agent to audit or adjust.

Use for: List all synthetic monitoring tests in the account, Retrieve the configuration of a specific test, Read every section of a monitoring test, Update the configuration of a test

Not supported: Does not handle raw performance telemetry, alerting rules, or dashboard rendering. Use for listing, reading, and updating synthetic monitoring tests only.

The Catchpoint API lists and inspects synthetic monitoring tests, retrieves a single test and all of its sections, and updates a test's configuration. It exposes the test objects behind Catchpoint's digital experience monitoring so they can be read and adjusted programmatically. Agents can audit and tune monitoring coverage without clicking through the Catchpoint portal.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

14%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

75%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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 Catchpoint API to your agent

Capabilities

Use Cases

Start building with Catchpoint API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Catchpoint API

Jentic AI Readiness Score

Catchpoint 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