One vault.
Every key and token sealed under your tenant's own key. The agent never sees a credential. Neither does the prompt.
The next-generation action layer for agents and humans. One MCP gateway into Xero, HaloPSA, your CRM and your databases. Your rules. Every action on the record.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcp100,000 free calls · No card · From NZ$89 a month
sha256One question. Two systems. One answer, priced and on the record.
actionlake, in one paragraph
actionlake is an MCP gateway: one remote MCP server that connects Claude and other AI agents to 1,000+ connectors, from Xero, HaloPSA, HubSpot and Microsoft 365 to your own databases. Every key gets a scope and a spending cap, risky actions wait for approval, and every call is recorded. 100,000 calls a month free, no card.
One line, no key needed: the consent page creates your sandbox.
Counted 24 October 2026. Read the price book · browse every connector
01Why now
A business runs on thirty systems, none built for AI. So every AI project starts by rebuilding integrations. The model was never the problem. The missing layer was.
Payments needed a network. Data needed a lake. Actions need one too.
02Do
Create the ticket. Send the invoice. Your agent finds the action, checks it and does it: one exact write, never retried, with a receipt.
Checking is free. You pay when a request reaches a vendor.
find_actions "create a ticket for Acme" free check ok · permitted · 1 call · $0.0003 free do ✓ ticket #48112 · 1 call · 91 ms · on the record
confirm: true.03Ask
Real questions span systems. actionlake fetches from each, joins them on the customer and returns the answer: four rows, not 2,400 pages. Rows never enter the model, so your token bill falls too.
finance.invoice.list means the same thing across 101 connectors; crm.contact.list across 177.
Ask again inside the cache window: free, and no hit to your vendor's rate limit.
04Plans and schedules
Anything your agent does once, it can do again: save the run as a plan, or hand it a written procedure. Run it on demand or on a schedule. No flows. No scripts.
0 8 * * 1Every Monday. Without anyone.899 in the store899 plans, ready.approval · waitingPauses for a yes.Agents and schedules start the work. No triggers to wire.
05Connectors
1,000+ connectors, 289,000+ actions: accounting, PSA, CRM, identity, support, code and your own databases. System missing? Your agent reads its docs and builds the connector: tested and signed.
Your agent reads the documentation and drafts the connector itself. Only live-tested actions are marked working.
Eight tools, however many systems. Your agent never drowns in its toolbox.
06Control
Every key and token sealed under your tenant's own key. The agent never sees a credential. Neither does the prompt.
Read-only. One system. One action. Or everything. Your call, per key.
keys.create "desk agent" · allowed_actions: read:*A cap on every key, in calls. Budgets cascade: a worker can never exceed its parent. At the cap, the call is refused before it is sent.
Sensitive actions stop and wait for a named person. The run pauses. They decide. It resumes.
Revoke one key and every key it minted stops.
07The record
Every action is recorded: who, what, which system, the cost, the result and the agent's reason. Records are chained and sealed daily, so a changed row shows.
Each row carries the hash of the one before. Hashes shown are illustrative.
7b10…e4c2sha256a3f9…c21ewhythe user asked which clients are overdue and have an urgent ticket open
a3f9…c21esha2560d77…91afwhythe user asked for a ticket for Acme's printer on level 2
0d77…91afsha2565e2b…7d04whypay the Acme Ltd bill; a named person approved it
08Built for agents. Not bolted on.
An agent can create its account, connect its systems, mint keys and cap budgets on its own, in its first minute. People get the same from one chat.
A person steps in where a vendor's OAuth needs a sign-in.
tenant.create ✓ 100,000 free calls · no card connections.create ✓ halopsa · secret sealed on arrival keys.create ✓ cap 500 · service.ticket.query check ✓ permitted · 1 call · $0.0003 do ✓ done · key "desk agent" · on the record
09Illustrative scenarios
Three illustrations of the work, not customer quotes. We publish no testimonial we cannot attribute to a named customer.
Every closed job never invoiced: the agent checks the PSA against the books, finds seventeen, drafts the invoices and waits for a yes.
A week of security-review screenshots becomes one screen: every run, who allowed it, what it cost, hash-chained.
The agent reads the books and the bank feed, writes nothing without approval, on a budget of a few dollars a month.
10Pricing
per action that reaches a vendor, past the free allowance; down to NZ$0.00016 in a bucket.
Finding, checking, planning, cached answers: NZ$0.Billed in NZD.
You pay when a request reaches a vendor. Finding, checking, planning and cached answers are free. No seats. The price book is public, with 60 days' notice of any change.
Billed in NZD. Prices exclude GST. GST is added to New Zealand invoices.
08Questions
What it is, what it costs, how far an agent can go.
An MCP gateway for AI agents: one MCP server and eight tools that connect Claude and other MCP clients to 1,000+ connectors and 289,000+ actions. You set what each agent may touch and spend, and every action is recorded. The first 100,000 calls a month are free.
One Model Context Protocol server between your agents and many systems. The agent connects once; the gateway holds the credentials, enforces limits and keeps the record.
Claude Code: claude mcp add --transport http actionlake https://connect.actionlake.com/mcp. Other MCP clients that support remote Streamable HTTP servers can add the same URL; we have tested Claude Code and the Claude app. Anything else can use the REST API.
No. You ask in plain words and the agent picks the action. A person mints narrower keys and, for OAuth systems such as Xero, registers the vendor app and signs in once.
100,000 calls a month free, no card. Starter is NZ$89 a month for 250,000 calls. You pay only when a request reaches a vendor; searching, checking, planning and cached answers are free. No seats: people and agents are never counted.
You decide. A key can be read-only, limited to one system or action, and capped. Require approval for every write or only named actions. Writes are never retried, and every action is on a hash-chained record.
In one region, DigitalOcean Sydney, stored in Australia; traffic passes through Cloudflare. Credentials are encrypted per tenant and never shown to the agent. No model sits on the data path, and your traffic never trains one.
Point your agent at the system's API docs. It drafts, tests and signs a connector, private to you unless you publish it.
100,000 free calls. No card. Hard caps on every key. Cached answers are free.