The TaskLinkr suite
AgentLedger
The agent-native accounting layer of the TaskLinkr suite: a data-layer posting contract over the business's books.
How it works
A posting contract, not another ledger
AgentLedger is a data-layer posting contract over the books the business already keeps — agent-booked work gets recorded against them, in a form agents and the business can both read.
Interim: QuickBooks via MCP
Today the contract runs over QuickBooks via MCP, read-mostly. The business's existing books stay where they are while agent activity is posted against them.
The suite's closing layer
AgentCal books the appointment and CredoPay settles it; AgentLedger is where that activity lands in the books — the last step of one system.
Built only when it earns it
A native ledger build starts only on a money-costing gap, or when TaskLinkr's own ledger needs one. Until then, the posting contract does the job — stated plainly, because that's where things stand.
The rest of the suite
AgentLedger records it. The rest of the suite books it, settles it, and fills the quiet hours around it.
AgentCal
The booking rail: agent-native scheduling against live availability.
CredoPay
The payment rail for agent-booked services, settling over ACH and FedNow.
Local Offers
Off-peak demand matching against real availability, inside TaskLinkr.
TaskLinkr
The directory itself — where agents find every listed business.