Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WeCP REST APIs Test Platform, 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%2Fwecreateproblems.com%2Fwecreateproblems" | shStep 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%2Fwecreateproblems.com%2Fwecreateproblems" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with WeCP REST APIs Test Platform API.
List tests
Create assessment
Integrate WeCP REST APIs Test Platform into automated workflows
Query and filter WeCP REST APIs Test Platform records by parameters
Monitor WeCP REST APIs Test Platform operational status and events
GET STARTED
Patterns agents use WeCP REST APIs Test Platform API for, with concrete tasks.
★ Developer Tools Operations
Use the WeCP REST APIs Test Platform to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including list tests, create assessment.
Call GET /tests to list tests
Data Retrieval and Monitoring
Query WeCP REST APIs Test Platform 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 WeCP REST APIs Test Platform endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call WeCP REST APIs Test Platform 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 'list tests', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — wecp rest apis developer assessment and testing platform.
METHOD
PATH
DESCRIPTION
/tests
List tests
/assessments
Create assessment
/tests
List tests
/assessments
Create assessment
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the WeCP REST API by hand means placing its API key in the Authorization header on every request and handling retries yourself. Through Jentic you install once, import WeCP from the API Directory, store the API key once, and your agent calls it.
Permission scoping
WeCP takes assessment details in the request body rather than in the path, so limit the agent to the operations it needs, such as listing tests. You choose the operations it may call, so creating assessments is not included unless you add it.
Credential isolation
Your WeCP 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 'list available tests' or 'create an assessment', and Jentic returns the matching WeCP operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using WeCP REST APIs Test Platform API through Jentic.
What authentication does the WeCP REST APIs Test Platform use?
The WeCP REST APIs Test Platform 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 list tests with the WeCP REST APIs Test Platform?
Yes. Use the GET /tests endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the WeCP REST APIs Test Platform?
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 list tests through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list tests'. Jentic returns the matching WeCP REST APIs Test Platform operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the WeCP REST APIs Test Platform have?
The WeCP REST APIs Test Platform exposes 2 endpoints covering assessments, tests operations.
Can I limit what my agent is allowed to do with the WeCP REST APIs Test Platform?
Yes. Because Jentic One is self-hosted, you decide which WeCP operations your agent may call, so you can allow only GET /tests to list tests and withhold POST /assessments to create assessments. Since WeCP takes assessment details in the request body rather than the path, restricting the agent to read-only listing keeps it from creating anything unless you explicitly add that operation. Your WeCP API key is held by your own Jentic One instance and injected at call time, so the agent uses only the operations and credentials your rules permit.
For Agents
Programmatically list tests, create assessment. Covers 2 operations with apiKey authentication.
Use for: I need to tests, I want to assessment, Get the current status of WeCP REST APIs Test Platform resources, List all records from WeCP REST APIs Test Platform
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
WeCP REST APIs developer assessment and testing platform. The API exposes 2 endpoints secured with apiKey authentication.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>