Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NannyKeeper 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%2Fnannykeeper.com%2Fnannykeeper" | 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%2Fnannykeeper.com%2Fnannykeeper" | 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 NannyKeeper API.
Estimate household employer taxes for one pay period from state, annual_wages, pay_frequency, and filing_status
Check whether a worker's annual wages meet the per-worker FICA threshold for a tax_year
Preview a payroll as a dry run with full tax breakdown, net pay, and employer costs before committing
Run payroll for one or more employees with regular_hours, overtime_hours, bonus, and payment_method
GET STARTED
Return pay stub PDFs for every employee on a payroll, base64-encoded in JSON
Create employer households and employees, and list employees with cursor pagination
Start a direct deposit ACH transfer for a payroll
Patterns agents use NannyKeeper API for, with concrete tasks.
★ Agent-run household payroll through Jentic
A parent's agent, connected through Jentic, handles the nanny's payroll each pay period. It sends the period dates, pay_date, pay_frequency, and each employee's hours to the preview operation, checks the net pay and employer costs, and only then submits the same payload to the run operation. Federal and state taxes and year-to-date totals are tracked by NannyKeeper.
Call POST /payroll/preview with employer_id, pay_period_start='2026-11-02', pay_period_end='2026-11-15', pay_date='2026-11-20', pay_frequency='biweekly', and employees=[{employee_id, regular_hours: 80}], then POST /payroll/run with the same body
Nanny tax estimates before hiring
Families deciding on a salary want to know the full cost before making an offer. The calculate operation takes a two-letter state code and annual_wages, plus optional pay_frequency, filing_status, and residence_state for workers who live in another state, and returns the employer and employee tax picture for a single pay period in any of the 50 states or DC.
Call POST /calculate with state='NY', annual_wages=52000, pay_frequency='weekly', and filing_status='single', then report the employer's total cost per pay period
FICA threshold checks for occasional help
Occasional sitters and housekeepers may or may not trigger household employer taxes. The threshold operation takes state and annual_wages, and an optional tax_year, and reports whether one worker's wages meet the per-worker FICA threshold, which the spec gives as $3,000 for 2026. FUTA and state unemployment depend on household quarterly wages and come back as unassessed.
Call GET /threshold with state='TX', annual_wages=4200, and tax_year=2026, and tell the user whether FICA applies
Pay stubs and direct deposit
After a payroll runs, the pay stub operation returns a PDF for every employee on it, base64-encoded in data.documents with employee_id, file_name, and mime_type. The ACH transfer operation starts direct deposit to the employee, with a fee per subscription tier. W-2 and Schedule H endpoints exist but return 501 not_available_via_api, so those forms come from the dashboard.
Call POST /documents/paystub for the latest payroll, decode each data.documents[] entry from base64, and save it under its file_name
13 endpoints — the nannykeeper api calculates us household employer taxes for nannies and other household workers in all 50 states and dc, and runs payroll for nannykeeper households.
METHOD
PATH
DESCRIPTION
/calculate
Calculate household employer taxes
/threshold
Check the FICA threshold
/payroll/preview
Preview payroll without saving
/payroll/run
Run payroll
/employees
List employees for an employer
/documents/paystub
Generate pay stub PDFs
/ach/transfer
Initiate direct deposit transfer
/calculate
Calculate household employer taxes
/threshold
Check the FICA threshold
/payroll/preview
Preview payroll without saving
/payroll/run
Run payroll
/employees
List employees for an employer
/documents/paystub
Generate pay stub PDFs
/ach/transfer
Initiate direct deposit transfer
What agents get from Jentic-routed access to this vendor.
Setup
Wiring NannyKeeper by hand means juggling live and test bearer keys, knowing which operations need a Starter or Professional plan, and matching the date and pay_frequency formats the payroll body expects. Through Jentic you install once, import NannyKeeper from the API Directory, store the key once, and your agent calls it.
Permission scoping
NannyKeeper carries the employer and employee ids in the request body for payroll, so rules bound which operations your agent may call, not which household. Limit the agent to the operations it needs, such as tax calculation and payroll preview; committing payroll or starting an ACH transfer is not included unless you add it.
Credential isolation
Your NannyKeeper 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 'calculate nanny taxes' or 'run household payroll', and Jentic returns the matching NannyKeeper 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 NannyKeeper API through Jentic.
What authentication does the NannyKeeper API use?
Per its OpenAPI spec, the NannyKeeper API uses a bearer API key. Live keys start with nk_live_ and act on real households; test keys start with nk_test_, are available on the Professional plan, and act only on sandbox households where nothing is emailed, charged, or sent to a bank. Through Jentic, the key is stored once by your own Jentic One instance and injected at call time.
Can I preview payroll before running it with the NannyKeeper API?
Yes. POST /payroll/preview takes the same body as POST /payroll/run, with employer_id, pay_period_start, pay_period_end, pay_date, pay_frequency, and employees, and returns the full tax breakdown, net pay, and employer costs without creating a payroll record. Both operations need a Starter plan or higher.
Can the NannyKeeper API generate W-2s and Schedule H?
Not through the API. POST /documents/w2 and POST /documents/schedule-h validate the request and then answer 501 not_available_via_api; download those forms from Documents in the NannyKeeper dashboard. Pay stubs are available through POST /documents/paystub.
What are the rate limits for the NannyKeeper API?
The OpenAPI spec includes a rate limit exceeded error but does not state the limit itself. Plan limits do apply: each plan caps active employees per employer, and creating past the cap returns 403 with seat_limit_reached. See https://www.nannykeeper.com/developers for current limits.
How do I calculate nanny taxes through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the NannyKeeper API from the API Directory, and store your API key once. Your agent searches for 'calculate nanny taxes', gets the calculate operation with its input schema, and calls POST /calculate with state and annual_wages. 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 NannyKeeper API?
Yes. For an estimating assistant, write a rule that allows only POST /calculate, GET /threshold, and POST /payroll/preview, so the agent can price out wages and dry-run payroll but cannot commit a payroll or move money. Storing a test key instead of a live key keeps any calls on sandbox households.
For Agents
Calculate US nanny taxes by state, check the FICA threshold, preview and run household payroll, fetch pay stubs, and start direct deposit for NannyKeeper households.
Use for: Calculate nanny taxes for a $35,000 salary in California, Check whether my babysitter's wages cross the FICA threshold this year, Preview this week's nanny payroll before I run it, Run biweekly payroll for our nanny with 4 overtime hours
Not supported: Does not file tax returns, collect SSNs or bank details, or issue W-2s through the API. Use for US household employer tax calculation and NannyKeeper payroll only.
The NannyKeeper API calculates US household employer taxes for nannies and other household workers in all 50 states and DC, and runs payroll for NannyKeeper households. It estimates taxes for a single pay period from a state and annual wages, checks whether a worker's wages meet the per-worker FICA threshold, and previews or runs payroll with federal and state taxes and year-to-date tracking. It also lists and creates employers and employees, returns pay stub PDFs for a payroll, and starts direct deposit transfers. Live keys act on real households, while test keys act only on sandbox households where nothing is emailed, charged, or sent to a bank.
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>