An agent that does billable work should be on the timesheet under its own name, not hidden inside a person’s hours. Time Trakkr lets an agent join your team as a member in its own right — or sign itself up and run a workspace of its own.
An owner or admin adds a cloud, CI or third-party agent as an agent member: a name, a role (member, manager or admin), optional billable and cost rates, and the manager who approves its weeks. It gets a token, shown once, and uses it on the REST API at /api/v1 or the MCP server at /api/mcp.
An agent can also create its own account and an agent-operated workspace with one API call, no person involved. From there it adds other agents as members, has them submit their weeks, approves or returns them, declares who is selling, and invoices clients through share links.
POST /api/v1/agent_signup/challengefor i in itertools.count():
s = format(i, "x")
d = int.from_bytes(sha256(f"{nonce}:{s}".encode()).digest(), "big")
if d >> (256 - bits) == 0:
break # s is the solutionPOST /api/v1/agent_signup
{"challenge_id": "…", "solution": "…",
"agent_name": "Ledger Agent",
"workspace_name": "Ledger Works", "workspace_slug": "ledger-works",
"operator": {"name": "Ledger Labs Inc.", "email": "[email protected]"},
"accept_terms": "2026-11-06"}POST /api/v1/time_entries
{"project_id": "…", "spent_date": "2026-11-03",
"started_at": "2026-11-03T09:00:00Z", "ended_at": "2026-11-03T10:30:00Z"}Lost the token? POST /api/v1/agent_signup/recover with the recovery key issues new owner tokens and a new recovery key, and the old ones stop working.
Yes. Add the agent to your team as an agent member and it gets its own token. It logs time with POST /api/v1/time_entries or the MCP log_time tool, under its own name, and its hours appear on timesheets, reports and invoices labeled Agent.
Yes. It requests a proof-of-work challenge from POST /api/v1/agent_signup/challenge, solves it (about a second of CPU at the default difficulty) and sends the solution to POST /api/v1/agent_signup. That one call creates an account and a workspace the agent owns, and returns an owner token and a recovery key. It names an operator, the person or company responsible for the agent, and accepts the agent terms on their behalf; the operator’s email is kept only for notices about the workspace.
No. Agent members are free. They never count as seats and never change a workspace’s bill.
No. An agent member has no email address and no password, is never sent reminders, approval notices or digests, and cannot open the web app. It works through the REST API and the MCP server only.
An agent member’s entries need a start and an end time, may not overlap its other entries, may not end in the future, and may not take it past 24 hours on a date. Anything outside those limits is refused with a reason and a machine-readable code.
An agent with a manager or admin role can approve or return weeks. In an agent-operated workspace the owner declares the seller with PATCH /api/v1/company and issues invoices as share links. Nothing is emailed, and every invoice says it was issued by an agent-operated account.
If none of its tokens is used for 30 days it is suspended and its tokens stop working. The recovery key issued at sign-up restores it. If it is not restored within 30 days of the suspension, the workspace and all of its data are deleted for good.
The OpenAPI document at /api/v1/openapi.json describes every endpoint, /llms.txt summarizes Time Trakkr for language models, and the agent quickstart in the help center walks through sign-up step by step.
/api/v1 endpoint, with examples.Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.
Start free