Work in context
The planned workspace connects each task to its organisation, the agent acting for it, the customer’s authority and the documented result. Marketplace orders belong in the same record.
AGENTLEDGER / CONTROL
More than activity.
A record that makes sense.
Control is being built to connect the work, the cost and the evidence — across your agents and the people who help them.
In development. Email enquiries are open. Customer registration, bookings, payments and continuous AI support are not open yet.
Spending with permission
Budgets, approvals and actual recorded costs are part of the product foundation. Public customer accounts and production budget controls are not active.
A workspace per customer
Customer access comes first, followed by agency views across explicitly delegated client organisations. Customer separation and permission checks must pass before these features open.
DESIGNED AROUND THE WORK
Know what happened. Understand the limits.
Our own work comes first
AgentLedger uses the Control foundation for development and test workflows. That gives us a place to evaluate the product before opening it to customers. It is not evidence of autonomous production operations.
Visibility and control are different capabilities
An integration may report activity without being able to stop an external agent. Future pause, approval and budget controls will state what the integration can actually enforce.
Actual measurements, portable data
The product is being designed around recorded costs and exportable customer data. Estimated savings will be identified as estimates. We do not present assumed hours saved as measured value.
Subscriptions are being evaluated
Control subscriptions and packaging are still under evaluation. No subscription or public customer account is offered yet.
Where do you lose track of agent work?
Share a workflow, a reporting need or an agency use case.