canonical: https://jentic.com/apis/skillspark.ai/skillspark

# Skill Spark API

Skill Spark API for AI-powered course creation, authentication, and Zapier integration. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically user login, refresh auth token. Covers 11 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- User login
- Refresh auth token
- Generate JWT
- Create course via AI
- List categories
- Check course ID

## Use cases

### Identity and Authentication Operations

Use the Skill Spark API to perform identity auth operations programmatically. The API provides 11 endpoints covering core functionality including user login, refresh auth token, generate jwt.

Example prompt: Call POST `/api/authentication` to user login

### Automated Authentication Management

Automate authentication operations by combining multiple Skill Spark API endpoints. Agents can refresh auth token and then generate jwt in a single workflow.

Example prompt: Call POST `/api/generate-Auth-Token` to refresh auth token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Skill Spark 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 'user login', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/authentication` | User login |
| POST | `/api/generate-Auth-Token` | Refresh auth token |
| POST | `/api/jwt-token-generate` | Generate JWT |
| POST | `/api/ai-Course-Create` | Create course via AI |
| GET | `/api/get-Category-List` | List categories |
| POST | `/api/ai-course/create` | Create course with SCORM |
| POST | `/api/ai-courseId/check` | Check course ID |
| POST | `/api/zapier/authentication` | Zapier authentication |

## Key resources

- **Authentication** — Operations related to Authentication
- **Courses** — Operations related to Courses
- **Zapier** — Operations related to Zapier

## 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:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/skillspark.ai/skillspark/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 Skill Spark API by hand means working through its several token endpoints for authentication and JWT generation and then carrying the bearer token across every course call yourself. Through Jentic you install once, import Skill Spark from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Skill Spark carries its targets in the request body rather than as a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as listing categories or checking a course id, and leave out course creation unless you add it.
- **Credential handling:** Your Skill Spark credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'authenticate a user' or 'list course categories', and Jentic returns the matching Skill Spark operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Skill Spark API use?

The Skill Spark 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 user login with the Skill Spark API?

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

### What are the rate limits for the Skill Spark 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 user login through Jentic?

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

### How many endpoints does the Skill Spark API have?

The Skill Spark API exposes 11 endpoints covering authentication, courses, zapier operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Skill Spark operations and credentials the agent may use. The Skill Spark API carries its targets in the request body rather than as an id in the URL path, so you scope the agent by operation rather than by resource: allow only what it needs, such as listing categories or checking a course id, and leave out operations like AI course creation or JWT generation unless you deliberately add them. The stored bearer credential is injected only for the operations you have permitted, so the agent cannot call anything outside that set.