Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Reference, 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%2Fsalarybox.in%2Fsalarybox" | 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%2Fsalarybox.in%2Fsalarybox" | 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 API Reference API.
Pull daily attendance, the attendance muster, and punch time entries for a start_date to end_date range
Filter attendance by SalaryBox ids, branch names, or department names
Look up staff by name, employee id, branch, department, job title, or phone number
Read employee CTC, monthly salary breakdowns, and salary and advance amounts paid
GET STARTED
Generate a payroll summary for a month from its month_from_date
Check leave balances and leave policies for staff
List pending leave, reimbursement, and device-verification requests awaiting approval
Patterns agents use API Reference API for, with concrete tasks.
★ AI agent HR assistant
An AI assistant for a small business owner answers questions like who was absent today or how much leave someone has left. Through Jentic the agent searches for 'get daily attendance', loads the SalaryBox operation with its input schema, and calls it with the required start_date and end_date while the API key is attached at call time. It replies with the attendance list without the owner opening the dashboard.
Call GET /attendance/daily with start_date and end_date set to today and summarise the attendance returned for each staff member
Monthly payroll reconciliation
Finance teams closing a month compare what each employee should earn with what was paid. SalaryBox returns employee CTC, a salary breakdown for a required month, salary paid, and advances paid, and POST /payroll/summary produces a summary from month_from_date. Together these feed a reconciliation sheet or accounting import.
Fetch GET /payroll/fetch-salary-breakdown for month 2026-10 and GET /payroll/fetch-salary-paid, then flag employees whose paid amount differs from the breakdown
Approval queue digest
Managers miss approvals buried in the app. SalaryBox lists pending leave requests, pending reimbursements, and pending device-mapping verifications, so a scheduled job can send a morning digest of everything awaiting action. Leave balances and policies add context to each leave request.
List GET /pending-requests/leave and GET /pending-requests/reimbursements and post a combined summary of open requests
Attendance export for branches
Multi-branch businesses need attendance per site for compliance and wages. The muster, time-entry, shift, and break operations accept branch_names and department_names filters with pagination, so each branch's register can be exported for the month.
Call GET /attendance/muster for October with branch_names set to one branch and page through all results
19 endpoints — the salarybox api reads staff, attendance, leave, and payroll records from a company's salarybox account, the indian staff management and payroll app.
METHOD
PATH
DESCRIPTION
/attendance/daily
Daily attendance
/attendance/muster
Attendance muster
/staff/
List staff
/leave/balance
List leave balances
/payroll/fetch-salary-breakdown
Fetch salary breakdown
/payroll/summary
Payroll summary
/pending-requests/leave
List pending leave requests
/attendance/daily
Daily attendance
/attendance/muster
Attendance muster
/staff/
List staff
/leave/balance
List leave balances
/payroll/fetch-salary-breakdown
Fetch salary breakdown
/payroll/summary
Payroll summary
/pending-requests/leave
List pending leave requests
What agents get from Jentic-routed access to this vendor.
Setup
Wiring SalaryBox by hand means formatting the Authorization header as Api-Key followed by your key, supplying required date or month parameters, and paging through page and page_size on every list. Through Jentic you install once, import SalaryBox from the API Directory, store the key once, and your agent calls it.
Permission scoping
SalaryBox selects employees, branches, and dates through query parameters rather than path ids, so rules bound which operations your agent may call, such as the attendance reads, not which employees it sees. You choose the operations it may call, so payroll reads like CTC and salary paid are not included unless you add them.
Credential isolation
Your SalaryBox 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.
Intent-based discovery
Agents search Jentic by intent such as 'get daily attendance' or 'list pending leave requests', and Jentic returns the matching SalaryBox operation with its input schema so the agent supplies the required dates and filters.
Alternatives and complements available in the Jentic catalogue.
Specific to using API Reference API through Jentic.
What authentication does the SalaryBox API use?
Per its OpenAPI spec, the SalaryBox API uses an API key sent in the `Authorization` header in the format `Api-Key {api-key}`, declared on every operation. Through Jentic the key is stored by your own instance and added at call time, so the agent never sees it.
Can I filter SalaryBox attendance by branch or department?
Yes. GET /attendance/daily, /attendance/muster, and /attendance/time-entry take required start_date and end_date parameters plus optional salarybox_ids, branch_names, and department_names filters, with page and page_size for pagination.
What are the rate limits for the SalaryBox API?
The OpenAPI spec does not specify rate limits. Check the SalaryBox documentation at https://docs.salarybox.in for current limits before scheduling large attendance exports.
Is there a SalaryBox MCP server?
You don't need an MCP server to give your agent SalaryBox. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the attendance, leave, and payroll operations it needs, discovered on demand.
How do I get a payroll summary from SalaryBox through Jentic?
Search Jentic for 'payroll summary for a month', load the POST /payroll/summary operation, and execute it with the required month_from_date in the body. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the SalaryBox API?
Yes. For an attendance assistant, write a rule that allows only the GET operations under /attendance/ and /leave/, so the agent can answer attendance and leave questions while salary, CTC, and payroll figures stay out of reach. Each call it makes is logged.
For Agents
Read SalaryBox staff lists, daily attendance and punches, leave balances, and monthly payroll figures such as CTC and salary paid.
Use for: I need yesterday's attendance for the Pune branch, Get the attendance muster for last month, Find all staff in the sales department, Check the leave balance for an employee
Not supported: Does not run payroll, approve requests, or mark attendance. Use for reading SalaryBox staff, attendance, leave, and payroll records only.
The SalaryBox API reads staff, attendance, leave, and payroll records from a company's SalaryBox account, the Indian staff management and payroll app. It returns daily attendance, the monthly muster, punch time entries, shifts, breaks, and holiday lists for a date range, filterable by SalaryBox id, branch, or department. Payroll reads cover employee CTC, salary breakdowns, salary and advances paid, and a payroll summary for a month, and pending leave, reimbursement, and device-verification requests can be listed for review.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>