Install Jentic One Beta

Connect the BusyBusy REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BusyBusy REST 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%2Fbusybusy.io%2Fbusybusy" | sh

Step 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%2Fbusybusy.io%2Fbusybusy" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with BusyBusy REST API.

Create, read, and update equipment records

Track employee certifications and record new ones

List and create project cost codes

Read and create budget cost entries for jobs

Retrieve authoritative signature records tied to time entries

GET STARTED

Start building with BusyBusy REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BusyBusy REST API for, with concrete tasks.

★ Agent-Driven Workforce Data Sync

An AI agent keeps a project management or payroll system in step with busybusy by reading equipment, cost codes, and budget costs and creating records when jobs are set up. It reconciles what each system holds and files the differences, so field data captured in busybusy flows into back-office tools without manual re-entry. This suits recurring end-of-day or end-of-week reconciliation runs.

Read the equipment and cost codes for a project, compare them with the payroll system, and create any missing records in busybusy

Equipment and Cost Code Setup

When a new job starts, teams create its equipment list and project cost codes in one pass rather than tapping through the app. The API accepts new equipment and cost code records and lets an integration read them back to confirm. Budget cost entries can be attached so job costing is ready before work begins.

Create the equipment records and project cost codes for a new job, then add the matching budget cost entries

Certification Compliance Tracking

An agent reads employee certifications and flags which crew members are missing a required qualification for a job. It lists certifications on file and records new ones as workers complete training. This turns compliance checks into an automated report rather than a manual roster review.

List the certifications on file for a crew, identify workers missing a required qualification, and record new certifications as they are earned

Key Endpoints

14 endpoints — the busybusy rest api reads and writes workforce records for construction and field teams, covering equipment, employee certifications, project cost codes, and budget costs.

METHOD

PATH

DESCRIPTION

GET

/equipment

List equipment records

POST

/equipment

Create an equipment record

GET

/certification

List certifications

POST

/certification

Create a certification

GET

/cost-code

List project cost codes

GET

/budget-cost

List budget cost entries

GET

/authoritative-signature

List authoritative signatures

GET

/api-key

List API keys

GET

/equipment

List equipment records

POST

/equipment

Create an equipment record

GET

/certification

List certifications

POST

/certification

Create a certification

GET

/cost-code

List project cost codes

GET

/budget-cost

List budget cost entries

GET

/authoritative-signature

List authoritative signatures

GET

/api-key

List API keys

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the BusyBusy REST API by hand means provisioning an API key, learning each resource's record shape, and building create and read calls for equipment, certifications, and costs. Through Jentic you install once, import busybusy from the API Directory, store the key once, and your agent reads and writes those records.

Permission scoping

busybusy's endpoints act on collections, so you scope your agent by operation. A rule can allow reading equipment and certifications while withholding the create and update operations, so the agent reports without changing records. You choose which operations it may call, and every call is logged.

Credential isolation

Your busybusy 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 'list equipment' or 'create a cost code', and Jentic returns the matching busybusy operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using BusyBusy REST API through Jentic.

What authentication does the BusyBusy REST API use?

The BusyBusy REST API authenticates with an API key sent in the X-API-Key request header per its OpenAPI spec, generated from your busybusy account. Through Jentic the key is held encrypted by your own Jentic One instance and attached at call time, so it never reaches the agent's context.

Can I create equipment and cost codes with the BusyBusy REST API?

Yes. The API exposes create operations for equipment, certifications, cost codes, and budget costs, alongside read operations to confirm what exists. An agent can set up a job's records and read them back in the same run.

What are the rate limits for the BusyBusy REST API?

The OpenAPI spec does not specify rate limits. Check the busybusy developer documentation at https://api.busybusy.io/docs for current limits and usage guidance.

Can I limit what my agent is allowed to do with the BusyBusy REST API?

Yes. The endpoints act on collections rather than individual records in the path, so scope your agent by operation: allow reading equipment and certifications while withholding create and update. You choose which operations it may call, and every call is logged.

How do I sync busybusy records through Jentic?

Search Jentic for 'list equipment' or 'create a cost code', add the BusyBusy REST API from the directory, and store your key once. Your agent then reads and writes the records your rule permits. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a busybusy MCP server?

You don't need an MCP server to give your agent the BusyBusy REST API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent reads and writes workforce records. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

BusyBusy REST API

Name: BusyBusy REST API
Brand: BusyBusy REST API
Availability: InStock

Official vendor OpenAPI document · agent-readyHR recruitingEmployee ManagementapiKey14 EndpointsREST

For Agents

Read and write equipment, certifications, cost codes, and budget costs in busybusy, and retrieve authoritative signatures. Returns workforce and job-costing records for an agent to reconcile.

Use for: Create a new equipment record in busybusy, List all certifications on file for the crew, Add a project cost code for a new job, Retrieve budget cost entries for a project

Not supported: Does not handle payroll processing, GPS time clock capture, or scheduling. Use for reading and writing equipment, certification, and job-costing records only.

The BusyBusy REST API reads and writes workforce records for construction and field teams, covering equipment, employee certifications, project cost codes, and budget costs. It also exposes authoritative signature records and API key management for account integrations. Agents can keep an external system in sync with busybusy's time-tracking and job-costing data without operating the mobile app.

Jentic One on Github View OpenAPI Document

Connect the BusyBusy REST API to your agent

Capabilities

Start building with BusyBusy REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

BusyBusy REST API