Introducing the Worksome CLI. Ask your AI agent anything, in plain language, and get an answer in seconds.
Every contingent workforce lead knows this moment. Someone in finance, legal, or procurement asks a question no standard report quite answers:
"Which contractors do we keep re-engaging on new assignments, and how long have they actually been working for us once every assignment is added together?"
The data exists. It's sitting in Worksome right now. But getting to it has always meant an export, a spreadsheet, a pivot table, and a reply that lands two days after anyone cared about the answer.
Today that changes. The Worksome CLI puts the whole platform one command away, for your team and for any AI agent your company already uses. Claude, Copilot, a scheduled script, or a person in a terminal. Same tool, same permissions, same answer.
What the CLI actually is
CLI stands for command line interface. In plain terms, it's a way to ask software a direct question in plain language and get a direct answer back, instead of opening a dashboard, building a filtered view, or waiting on someone else to run a report.
Why a CLI, and why now
Let's be honest about what happened this year. AI agents got good at doing real work. They can read, reason, remember, and follow up. What they can't do is reach into systems that were only ever built for a human with a keyboard and mouse.
So the systems that matter in 2026 are the ones agents can actually interact with.
The Worksome CLI is that bridge. It covers 60+ resource groups and over 170 operations, and it's generated directly from our API, so it can never drift from what the platform actually does. Everything your team touches by hand in Worksome, an agent can now touch on their behalf. Hires, contracts, timesheets, payment requests, invoices, budgets, approvals, compliance gates, classifications, talent pools, suppliers. All of it.
And we've published a ready-made skill that teaches Claude how to use it well, so your first working agent is ready in an afternoon, not a months-long project.
Nothing new to secure
We know the first question, because it's the one we'd ask.
You create a personal access token in Worksome. The CLI does exactly what you could do in the browser, and not one thing more. It inherits your role. Tokens expire after six months, and you can revoke them whenever you like. Reading is the default posture, and every action that changes something can be previewed with a dry run before it touches your account.
Bank details, identity documents, and credentials are out of reach for automation. Full stop. Personal and sensitive data stays within the Worksome platform.
What Worksome CLI makes visible on day one
Here's where it gets useful, not theoretical. A few examples that need nothing more than a token and an afternoon:
Active, but not billing. Every hire that's active this period with no payment request behind it. Each answer is one of three things: a worker not getting paid, work that isn't happening, or a hire somebody forgot to close. All three are worth knowing about, and there's a purpose-built filter for it that almost nobody knew existed until now.
Ending in the next 14 days. The most common avoidable failure in any program is an assignment that ends with no decision made. Now the extension conversation starts on time, because the list arrives before the deadline does.
Who can approve payments. The segregation-of-duties report your auditors keep asking for, in one call.
Workers holding more than one hire. On one account we looked at, a quarter of the active workers held more than one engagement. One held six. Sequential contracts hide tenure, and per-hire checks miss it entirely.
None of these needs an integration. None needs a developer. An agent or person runs the command, and a program lead reads the answer.
From one-off questions to standing requests
Once you've asked a question once, the obvious next step is to stop asking. Put the same questions on a schedule and let the answers come to the person who can act on them.
A morning roll-call in your inbox or AI of choice: headcount by entity, plus who started and who ended since yesterday. An ending-soon alert that goes to the hiring manager by name when an assignment is seven days out. An approval queue that escalates itself when something has been waiting too long.
None of this is exotic. It's just the questions you already have, answered before you think to ask them.
Connecting Worksome to enterprise tools and internal systems
The most valuable thing the CLI does is help you see what Worksome can't.
Connect Worksome to your AP ledger, and every payment for external labour that has no hire behind it lights up. That's spend outside the program, which means spend outside your rate cards, your compliance checks, and your classification process. Leakage isn't only a cost problem. It's a risk problem wearing a cost problem's clothes.
Join it to your HRIS and reconcile headcount in both directions. Join it to your identity provider and revoke access the moment an assignment ends, instead of finding a live VPN login on day 20.
This part takes more than an afternoon. But it needs an AP extract from you and nothing else from us, and it's the one that changes how finance sees your program.
Where to start
If you're picking a first three, pick these:
- Unbilled actives. One filter, immediate findings, and the cost of being wrong is an afternoon.
- Ending soon, banded. One schedule, and the extension conversation starts on time.
- Unmanaged spend reconciliation. One join, and finance starts trusting the program's numbers.
Everything at the first two levels is a read. Nothing changes in your account unless you decide it should. Run those long enough to trust your own numbers before you automate anything that acts.
Try it
The Worksome CLI is available now for every Worksome customer. Create a token under Integrations, install the CLI, and ask it something you couldn't answer yesterday.
Worksome is the external workforce platform: one place to source, engage, classify, and pay a company's contractors, freelancers, consultants, and talent sourced through staffing agencies. More than 350 enterprises use Worksome to manage and pay external talent across 150+ countries and all 50 US states.