canonical: https://jentic.com/apis/swaggerhub.xvrbovskym/b-vsa-semestrlny-projekt-2

# Xvrbovskym B-VSA Semestrálny Projekt 2

Špecifikácia REST webových služieb slúžia pre detailný opis požadovanej funkcionality pre Semestrálny Projekt 2 v rámci predmetu B-VSA akademický rok 2022/2023. Pre dopyty na väčšinu služieb (okrem createStudent a createTeacher) je potrebné byť prihlásený. Služby pracujú s Basic autentifikáciou. Každý študent a učiteľ je používateľ systému, ktorý sa môže prihlásiť. Niektoré služby vyžadujú autoriz. The API exposes 15 endpoints secured with basic authentication.

## For AI agents

Programmatically create new student, get all students. Covers 15 operations with basic authentication.

## Scope

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

## Capabilities

- Create new student
- Get all students
- Delete a student by id
- Query and filter B-VSA Semestrálny Projekt 2 records by parameters
- Monitor B-VSA Semestrálny Projekt 2 operational status and events

## Use cases

### Education Operations

Use the B-VSA Semestrálny Projekt 2 to perform education operations programmatically. The API provides 15 endpoints covering core functionality including create new student, get all students, get a student by id.

Example prompt: Call POST `/api/students` to create new student

### Automated student Management

Automate student operations by combining multiple B-VSA Semestrálny Projekt 2 endpoints. Agents can get all students and then get a student by id in a single workflow.

Example prompt: Call GET `/api/students` to get all students, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call B-VSA Semestrálny Projekt 2 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 basic tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/students` | Create new student |
| GET | `/api/students` | Get all students |
| GET | `/api/students/{id}` | Get a student by id |
| DELETE | `/api/students/{id}` | Delete a student by id |
| POST | `/api/teachers` | Create new teacher |
| GET | `/api/teachers` | Get all teachers |
| GET | `/api/teachers/{id}` | Get a teacher by id |
| DELETE | `/api/teachers/{id}` | Delete a teacher by id |

## Key resources

- **student** — Operations related to student
- **teacher** — Operations related to teacher
- **thesis** — Operations related to thesis

## Why Jentic

- **Setup:** Wiring the B-VSA Semestralny Projekt 2 API by hand means handling its HTTP basic auth on every call and shaping the student, teacher, and thesis payloads against its host yourself. Through Jentic you install once, import the B-VSA Semestralny Projekt 2 API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** This API puts each record id in the URL path (`/api/students/{id}`, `/api/theses/{id}`), so a rule can pin your agent to one student, teacher, or thesis: it can read that record and nothing else. You choose the operations it may call, so destructive ones like deleting a student or a teacher are not included unless you add them.
- **Credential handling:** Your B-VSA Semestralny Projekt 2 basic auth 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 'create a new student' or 'assign a thesis', and Jentic returns the matching B-VSA Semestralny Projekt 2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Schoology** — Alternative education API
- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows

## FAQ

### What authentication does the B-VSA Semestrálny Projekt 2 use?

The B-VSA Semestrálny Projekt 2 uses HTTP Basic authentication with username and password. 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 new student with the B-VSA Semestrálny Projekt 2?

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

### What are the rate limits for the B-VSA Semestrálny Projekt 2?

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 new student through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create new student'. Jentic returns the matching B-VSA Semestrálny Projekt 2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the B-VSA Semestrálny Projekt 2 have?

The B-VSA Semestrálny Projekt 2 exposes 15 endpoints covering student, teacher, thesis operations.

### Can I limit what my agent is allowed to do with the B-VSA Semestralny Projekt 2 API?

Yes. Jentic One is self-hosted, so you decide which of the B-VSA Semestralny Projekt 2 operations your agent may call, and you can leave out destructive ones like deleting a student or a teacher unless you deliberately add them. Because each record id sits in the URL path, such as `/api/students/{id}` or `/api/theses/{id}`, your own rules can pin the agent to a single student, teacher, or thesis so it reads that record and nothing else. The basic auth credentials are held encrypted by your instance and injected only at execution time, so the agent never sees the raw secret.