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

# SkillzRun API

Skills assessment and talent management API. The API exposes 6 endpoints secured with bearer authentication.

## For AI agents

Programmatically create assessment, list assessments. Covers 6 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Create assessment
- List assessments
- Get assessment
- Assign assessment to candidate
- Monitor SkillzRun API operational status and events

## Use cases

### HR and Recruiting Operations

Use the SkillzRun API to perform hr recruiting operations programmatically. The API provides 6 endpoints covering core functionality including create assessment, list assessments, get assessment.

Example prompt: Call POST /assessments to create assessment

### Automated Assessments Management

Automate assessments operations by combining multiple SkillzRun API endpoints. Agents can list assessments and then get assessment in a single workflow.

Example prompt: Call GET /assessments to list assessments, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SkillzRun API 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/assessments` | Create assessment |
| GET | `/assessments` | List assessments |
| GET | `/assessments/{assessmentId}` | Get assessment |
| POST | `/candidates` | Create candidate |
| GET | `/candidates` | List candidates |
| POST | `/candidates/{candidateId}/assessments` | Assign assessment to candidate |

## Key resources

- **Assessments** — Skills assessment operations
- **Candidates** — Candidate management

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/skillzrun.com/skillzrun/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 SkillzRun API by hand means setting up its bearer token and carrying it across every assessment and candidate call on the external API host yourself. Through Jentic you install once, import SkillzRun from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SkillzRun puts the assessment and candidate ids in the URL path (`/assessments/{assessmentId}`, `/candidates/{candidateId}/assessments`), so a rule can pin your agent to one candidate: it can read that candidate and their assessments and nothing else. You choose the operations it may call, so creating new assessments or candidates is not included unless you add it.
- **Credential handling:** Your SkillzRun 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.
- **Discovery method:** Agents search Jentic by intent such as 'create an assessment' or 'list candidates', and Jentic returns the matching SkillzRun operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the SkillzRun API use?

The SkillzRun API 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 create assessment with the SkillzRun API?

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

### What are the rate limits for the SkillzRun API?

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 create assessment through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create assessment'. Jentic returns the matching SkillzRun API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SkillzRun API have?

The SkillzRun API exposes 6 endpoints covering assessments, candidates operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which SkillzRun operations and credentials the agent may use. SkillzRun puts the assessment and candidate ids in the URL path (`/assessments/{assessmentId}` and `/candidates/{candidateId}/assessments`), so you can pin the agent to a single candidate and let it read only that candidate and their assessments. You pick the operations it may call, so creating new assessments or candidates stays off limits unless you grant it.