Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OSV Customer Payroll Portal 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%2Fonesourcevirtual.io%2Fonesourcevirtual" | 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%2Fonesourcevirtual.io%2Fonesourcevirtual" | 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 OSV Customer Payroll Portal API.
List the companies and payroll options available to a customer
Search payroll runs and return payroll details and statistics
Retrieve settlements and search them by criteria
Request a settlement action and read its distribution shipping details
Read same-day ACH banking information and custom metadata
GET STARTED
Patterns agents use OSV Customer Payroll Portal API for, with concrete tasks.
★ AI Agent Payroll Access
Give an AI agent read access to a customer's payroll portal. The agent discovers the payroll and settlement operations through Jentic, stores the OneSource Virtual credentials once, and answers questions about runs, details, and statistics without bespoke HTTP wiring. Sensitive actions stay behind the operations you allow.
Search a company's recent payroll runs and summarize the payroll statistics for the latest period
Payroll Reporting
Report on payroll activity across a customer's companies. The API searches payroll runs and returns per-run details and aggregate statistics, so a reporting job can roll up spend and headcount figures by company and period.
List a customer's companies, search each one's payroll runs, and compile a statistics report
Settlement Management
Track and act on payroll settlements. The API retrieves settlements, searches them by criteria, requests a settlement action, and returns the distribution shipping details for a settlement, so a finance workflow can follow funds through to delivery.
Search settlements for a company, request a settlement action, and return its distribution shipping details
Banking Details Lookup
Surface the banking information behind payroll funding. The same-day ACH banking information operation returns the account details tied to a customer's payroll, so an agent can confirm funding routes before a run.
Retrieve the same-day ACH banking information for a customer and return the funding account details
14 endpoints — the osv customer payroll portal api from onesource virtual gives payroll customers programmatic access to their payroll and settlement data.
METHOD
PATH
DESCRIPTION
/api/v1/companies
List a customer's companies
/api/v1/payroll/search
Search payroll runs
/api/v1/payroll/details
Retrieve payroll details
/api/v1/settlements
List settlements
/api/v1/settlements/request
Request a settlement action
/api/v1/companies
List a customer's companies
/api/v1/payroll/search
Search payroll runs
/api/v1/payroll/details
Retrieve payroll details
/api/v1/settlements
List settlements
/api/v1/settlements/request
Request a settlement action
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the OSV Customer Payroll Portal API by hand means learning its bearer-token and encrypted-request-key auth and threading payroll and settlement searches together yourself. Through Jentic you install once, import the API from the API Directory, store the credentials, and your agent calls the operation it needs.
Permission scoping
You decide which OSV operations your agent may call. A rule can grant payroll reads and reporting while withholding settlement requests, so the agent can report on payroll without moving funds, and the rule bounds operations rather than a single record.
Credential isolation
Your OneSource Virtual credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search a customer's payroll runs', and Jentic returns the matching OSV operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using OSV Customer Payroll Portal API through Jentic.
What authentication does the OSV Customer Payroll Portal API use?
The API authenticates with a bearer token in the Authorization header, and also accepts an X-Encrypted-Request-Key header for encrypted requests, as declared by its OpenAPI spec. Through Jentic these credentials are stored encrypted by your own Jentic One instance and injected when a call runs, so they never enter the agent's prompt or logs.
Can the OSV Customer Payroll Portal API return payroll statistics?
Yes. It searches payroll runs, returns per-run details, and provides aggregate payroll statistics, so an agent can report on payroll activity for a company and period.
What are the rate limits for the OSV Customer Payroll Portal API?
The OpenAPI spec does not publish specific rate limits. Check the OneSource Virtual documentation for current limits, and have your agent back off and retry when it receives a throttling response.
How do I read payroll data with the OSV Customer Payroll Portal API through Jentic?
Search Jentic for an intent like 'search a customer's payroll runs', and it returns the matching OSV operation with its input schema. Import the connector once, store your credentials, and your agent reads payroll and settlement data without hand-written HTTP code. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a OneSource Virtual MCP server?
You don't need an MCP server to give your agent the OSV Customer Payroll Portal API. Jentic connects it directly from the Jentic API Directory: import the API, store your credentials once, and your agent calls the payroll and settlement operations. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.
Can I limit what my agent is allowed to do with the OSV Customer Payroll Portal API?
Yes. You choose the operations the agent may call, so a rule can allow payroll reads and reporting while withholding settlement requests unless you add them. A rule bounds which operations run rather than which individual record is touched, and every call is logged.
Know of an official OpenAPI document? Contribute it →
For Agents
Read a customer's companies, payroll runs, details, and statistics, and retrieve, search, and request settlements through the OSV Customer Payroll Portal API.
Use for: I want to search a customer's payroll runs, Retrieve payroll details for a company, List the settlements for a customer, Request a settlement action
Not supported: Does not run payroll or onboard employees. Use it to read payroll runs, details, and statistics and to retrieve, search, and request settlements only.
The OSV Customer Payroll Portal API from OneSource Virtual gives payroll customers programmatic access to their payroll and settlement data. It lists companies and available payroll options, searches payroll runs, and returns payroll details and statistics. It also retrieves settlements, searches and requests settlement actions, exposes same-day ACH banking information, and returns distribution shipping details for a settlement.
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>