For Agents
Programmatically create employee, list employees. Covers 13 operations with bearer authentication.
Use for: I need to employee, I want to employees, Search for employee, Find all employee
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stafiz API, 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%2Fstafiz.net%2Fstafiz" | 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%2Fstafiz.net%2Fstafiz" | 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 Stafiz API.
Create employee
List employees
Get employee
Update employee
GET STARTED
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
Stafiz API for staff management, scheduling, and workforce optimization. The API exposes 13 endpoints secured with bearer authentication.
Delete employee
Patterns agents use Stafiz API for, with concrete tasks.
★ HR and Recruiting Operations
Use the Stafiz API to perform hr recruiting operations programmatically. The API provides 13 endpoints covering core functionality including create employee, list employees, get employee.
Call POST /employees to create employee
Automated employees Management
Automate employees operations by combining multiple Stafiz API endpoints. Agents can list employees and then get employee in a single workflow.
Call GET /employees to list employees, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Stafiz 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.
Search Jentic for 'create employee', load the operation schema, and execute with Jentic-managed credentials
13 endpoints — stafiz api for staff management, scheduling, and workforce optimization.
METHOD
PATH
DESCRIPTION
/employees
Create employee
/employees
List employees
/employees/{employeeId}
Get employee
/employees/{employeeId}
Update employee
/employees/{employeeId}
Delete employee
/schedules
Create schedule
/schedules
List schedules
/schedules/{scheduleId}
Get schedule
/employees
Create employee
/employees
List employees
/employees/{employeeId}
Get employee
/employees/{employeeId}
Update employee
/employees/{employeeId}
Delete employee
/schedules
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Stafiz API by hand means learning its bearer auth against stafiz.net/api/v1 and threading the employee and schedule ids into paths yourself. Through Jentic you install once, import the Stafiz API from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
Stafiz puts the employee id in the URL path (/employees/{employeeId}), so a rule can pin your agent to reading a single employee. You choose the operations it may call, so ones like updating or deleting an employee are not included unless you add them.
Credential isolation
Your Stafiz bearer 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.
Intent-based discovery
Agents search Jentic by intent such as 'list employees' or 'get an employee's schedule', and Jentic returns the matching Stafiz 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 Stafiz API through Jentic.
What authentication does the Stafiz API use?
The Stafiz 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 employee with the Stafiz API?
Yes. Use the POST /employees endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Stafiz 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 employee through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create employee'. Jentic returns the matching Stafiz API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Stafiz API have?
The Stafiz API exposes 13 endpoints covering employees, schedules, shifts operations.
Create schedule
/schedules
List schedules
/schedules/{scheduleId}
Get schedule