canonical: https://jentic.com/apis/wecreateproblems.com/wecreateproblems

# Wecreateproblems WeCP REST APIs Test Platform

WeCP REST APIs developer assessment and testing platform. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list tests, create assessment. Covers 2 operations with apiKey authentication.

## Scope

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

## Capabilities

- 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

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'list tests', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/tests` | List tests |
| POST | `/assessments` | Create assessment |

## Key resources

- **Assessments** — Operations related to Assessments
- **Tests** — Operations related to Tests

## AI readiness

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.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/wecreateproblems.com/wecreateproblems/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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