Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PlanSource Benefits Administration 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%2Fplansource.com%2Fplansource-benefits-api" | 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%2Fplansource.com%2Fplansource-benefits-api" | 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 PlanSource Benefits Administration API.
Sync employee demographics and subscriber information from HRIS systems
Manage benefits coverage including elections, enrollments, and qualifying life events
Calculate and export payroll deductions for enrolled benefits
Submit and track Evidence of Insurability (EOI) applications for medical underwriting
GET STARTED
Generate ACA compliance reports including 1095-C forms and affordability calculations
Perform batch operations for subscriber imports, coverage updates, and terminations
Manage administrator accounts with role-based permissions for brokers and HR staff
Patterns agents use PlanSource Benefits Administration API for, with concrete tasks.
★ HRIS Integration and Demographic Synchronization
HR operations teams integrate PlanSource with platforms like Workday, BambooHR, and ADP to maintain single-source-of-truth employee data. The API enables bidirectional sync where new hires flow from HRIS to PlanSource for benefits enrollment, while enrollment elections flow back for payroll deduction setup. Automated sync jobs run nightly to update demographic changes like addresses, dependents, and employment status. This eliminates dual data entry, reduces enrollment errors, and ensures benefit eligibility rules always evaluate against current employee attributes.
Fetch new employees from HRIS API who started in past 24 hours, create subscriber records in PlanSource with demographics and employment data, trigger new hire enrollment workflow.
Open Enrollment Automation and Reporting
Benefits administrators orchestrate annual open enrollment using the API to monitor completion rates, send reminder notifications, and generate executive dashboards. The API provides endpoints to list subscribers who haven't completed enrollment, retrieve their current elections, and track benefit plan participation rates. Automated workflows use this data to trigger personalized reminder emails through marketing automation platforms. Post-enrollment, the API generates summary reports for insurance carrier submissions and payroll system imports.
Query PlanSource for all active subscribers without completed enrollment for current period, export list with contact information, generate enrollment completion report showing plan participation by department.
Payroll Integration and Deduction Management
Payroll teams use the API to retrieve employee benefits deductions for each pay period and import them into payroll systems. The API calculates deductions based on enrollment elections, pay frequency, and contribution amounts, handling scenarios like new enrollment proration and mid-month coverage changes. For companies with multiple payroll calendars (salaried, hourly, commission), the API supports filtering deductions by employee group and pay schedule. This ensures accurate benefit premiums are withheld and remitted to carriers on time.
Retrieve payroll deductions for all subscribers for upcoming pay date, group by payroll calendar, format for payroll system import, validate total deduction amounts against carrier invoices.
Compliance Reporting for ACA and Government Regulations
HR compliance teams use the API to generate Affordable Care Act (ACA) reports including 1095-C forms, measurement period calculations, and affordability safe harbor analysis. The API aggregates enrollment data, hours worked, and premium contributions to determine full-time employee status and offer compliance. It also supports COBRA continuation coverage tracking and HIPAA special enrollment period validation. Automated compliance workflows pull data monthly to identify at-risk scenarios before IRS filing deadlines.
Generate ACA compliance report for tax year covering all full-time employees, calculate affordability percentages, identify employees not offered minimum essential coverage, export data for 1095-C form generation.
52 endpoints — plansource is a cloud-based benefits administration platform serving hr departments, brokers, and insurance carriers.
METHOD
PATH
DESCRIPTION
/subscriber
Create or update subscriber demographic information
/subscriber/{subscriber_id}/coverage
Retrieve coverage elections for a subscriber
/payroll/deductions
Get payroll deductions for a pay period
/eoi/application
Submit an Evidence of Insurability application
/aca/enrollees
Retrieve ACA enrollment data for compliance reporting
/subscriber
Create or update subscriber demographic information
/subscriber/{subscriber_id}/coverage
Retrieve coverage elections for a subscriber
/payroll/deductions
Get payroll deductions for a pay period
/eoi/application
Submit an Evidence of Insurability application
/aca/enrollees
Retrieve ACA enrollment data for compliance reporting
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PlanSource Benefits Administration API by hand means learning its bearer token auth and hand-building requests across its subscriber, coverage, payroll-deduction and enrollment endpoints yourself. Through Jentic you install once, import PlanSource from the API Directory, store the token once, and your agent calls it.
Permission scoping
PlanSource puts the subscriber id in the URL path (/subscriber/{subscriber_id}/coverage), so a rule can pin your agent to one subscriber: it reads that subscriber's coverage and nothing else. You choose the operations it may call, so state-changing ones like creating a subscriber or submitting an EOI application are not included unless you add them.
Credential isolation
Your PlanSource 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 'get an employee's benefits enrollments' or 'read payroll deductions', and Jentic returns the matching PlanSource 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 PlanSource Benefits Administration API through Jentic.
What authentication does the PlanSource API use?
The PlanSource Administrative API uses Bearer token authentication. You obtain API credentials from your PlanSource account administrator and pass the token in the Authorization header for all requests.
Can I automate open enrollment workflows with the PlanSource API?
Yes. The API provides endpoints to monitor enrollment completion, retrieve pending enrollments, update employee elections, and generate participation reports. You can build automated reminder workflows and track completion rates programmatically.
How do I integrate PlanSource with my payroll system?
Use the payroll deductions endpoints to retrieve calculated benefit premiums for each pay period. The API supports filtering by pay schedule and employee group, returning deduction data in formats compatible with most payroll systems for import.
What is Evidence of Insurability (EOI) and how does the API handle it?
EOI is medical underwriting required for certain coverage amounts (like high-value life insurance). The API allows submitting EOI applications with medical questionnaires, tracking approval status, and receiving carrier decisions-automating a traditionally paper-based process.
How do AI agents use the PlanSource API through Jentic?
Agents search Jentic for tasks like 'sync employee benefits enrollments' and receive PlanSource operation schemas. Jentic securely stores API credentials and handles authentication, enabling agents to query enrollments, calculate deductions, and generate reports with natural language parameters.
Can I limit what my agent is allowed to do with the PlanSource Benefits Administration API?
Yes. Because you run Jentic One yourself, your own rules decide which PlanSource operations and credentials the agent can use. Since the API carries the subscriber id in the URL path, such as /subscriber/{subscriber_id}/coverage, you can pin the agent to a single subscriber so it reads that person's coverage and nothing else. You also choose the exact operations it may call, so state-changing ones like creating a subscriber or submitting an EOI application stay off unless you add them.
For Agents
Manage employee benefits enrollment, coverage, payroll deductions, and EOI submissions through PlanSource's benefits administration platform.
Use for: Sync new employee data from our HRIS to PlanSource, Get all active benefits enrollments for an employee, Calculate payroll deductions for this pay period, Submit evidence of insurability for life insurance coverage
Not supported: Provides benefits administration and enrollment management. Does not handle employee time tracking, performance reviews, or core HRIS functions-use dedicated HR platforms. Does not process insurance claims-use carrier APIs.
PlanSource is a cloud-based benefits administration platform serving HR departments, brokers, and insurance carriers. The Administrative API provides comprehensive control over employee enrollment workflows, coverage management, payroll deduction calculations, and Evidence of Insurability (EOI) submissions. HR teams use it to sync employee demographics from HRIS systems, automate open enrollment periods, manage qualifying life events, and generate compliance reports for ACA, COBRA, and HIPAA. The API supports batch operations for high-volume subscriber imports, coverage updates during acquisition integrations, and bulk termination processing. It enables benefits administration to operate as part of a unified HR technology stack, connecting PlanSource with payroll systems, time tracking tools, and employee self-service portals.
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>