Connect AI to your ShiftCare.
AutonAI is a secure connector that lets Claude — and your own dashboards — work directly with your ShiftCare data: clients, shifts, billing, incidents, compliance and more. One login covers every ShiftCare account you manage.
One secure connector, three front doors.
Your ShiftCare credentials are captured once, encrypted, and never enter a chat or a browser. Everything else works through them — safely.
Claude connector (MCP)
Add AutonAI to Claude as a custom connector and ask questions of your real data — or have it do the admin work with you.
- Works with claude.ai and Claude Desktop
- Reads and writes across 12 domains
- Every write supports dry-run preview
- Destructive actions require explicit confirmation
REST API for your dashboards
Scoped API keys let your own dashboards, reports and integrations pull live data across every connected account — and, if you choose, drive the same guard-railed write tools.
- Read-only keys by default
- Read + write keys are opt-in, with explicit risk acknowledgment
- OpenAPI spec, docs and llms.txt included
- Keys expire, and revoke instantly
Customer portal
Sign in to manage your workspace yourself: connect ShiftCare accounts, create and revoke API keys, and use the growing set of built-in dashboards.
- Connect accounts with your ShiftCare login
- Self-serve API key management
- Built-in cancellations dashboard, more coming
- Passwords are exchanged for tokens, never stored
Sign in with ShiftCare once per company you manage. AutonAI stores an encrypted token — not your password.
Point Claude's custom connector at AutonAI, and create API keys for anything you're building yourself.
Queries fan out across all connected accounts, with every row tagged by company — one view of the whole operation.
84 tools across 12 domains.
Every tool is typed, validated and guard-railed, with the quirks of the real ShiftCare API already handled. This list is generated from the live registry — it can't drift from what's actually deployed.
Clients 6
manage_client manage_client_contacts manage_client_funds manage_client_documents manage_client_custom_attribute list_clients
Health & risk 4
get_client_health_risk get_client_risk_insights manage_client_health manage_medical_history
Funds & budgets 5
list_client_funds list_fund_transactions manage_expense update_fund_transaction_status list_sah_claims
Care plans 7
manage_care_plan manage_focus_area manage_goal manage_task manage_care_plan_review manage_rating list_strategies
Medications 3
manage_medication manage_medication_plan manage_medication_administration
Shifts 11
manage_shift bulk_edit_series approve_shift bulk_approve_shifts list_shifts get_shift list_recurring_shift_ids list_facilities list_facility_shifts manage_progress_note manage_note_template
Billing 9
manage_quote manage_quote_status manage_quote_recipients list_price_books list_invoices manage_invoice list_invoiceable_items manage_invoice_payment list_timesheets
Quality & risk 9
list_incidents get_incident create_incident update_incident delete_incident manage_incident_discussion archive_incident manage_complaint complaint_stats
Forms 7
list_forms get_form manage_form manage_form_response create_form_assignment list_form_assignments list_form_responses
Workforce 7
list_staff manage_staff staff_compliance list_staff_qualifications manage_staff_qualification upload_staff_document manage_leave
Dashboards 9
dashboard_operations dashboard_user_tasks run_report report_hub scheduler_financials create_dashboard_api_key list_dashboard_api_keys revoke_dashboard_api_key get_dashboard_api_docs
Workspace 7
list_accounts whoami remove_account list_segments manage_segment manage_notifications manage_webhooks
Build on your own data.
Everything Claude can see, your software can too. Mint a key in the portal and call
the API from your server — the OpenAPI spec at /openapi.json documents every endpoint.
// Read: list clients across every connected account const res = await fetch("https://autonai.app/api/v1/clients", { headers: { Authorization: "Bearer " + API_KEY }, }); // Write (read_write key): preview first with dry_run await fetch("https://autonai.app/api/v1/tools/manage_progress_note", { method: "POST", headers: { Authorization: "Bearer " + API_KEY, "content-type": "application/json" }, body: JSON.stringify({ action: "create", dry_run: true, /* … */ }), });
Read-only keys (default)
Load data for dashboards and reports. Can never change anything in ShiftCare — if the key leaks, the damage stops at "someone saw data".
Read + write keys (opt-in)
Unlock the same 84-tool surface Claude uses, for your own automations. Created only after an explicit risk acknowledgment: automated writes have no per-action human approval, so you own the software that holds the key. Dry-run previews and confirmation flags on destructive actions still apply.
Sensible limits
Keys expire (up to 12 months), are capped per workspace, list and revoke instantly, and are stored only as hashes — AutonAI can't leak what it doesn't keep.
Built like it's holding care data — because it is.
AutonAI sits in front of client, staff and billing records, so the defaults are conservative and the guardrails are code, not policy documents.
Credentials encrypted at rest
ShiftCare tokens are envelope-encrypted with AWS KMS. Your ShiftCare password is exchanged for a token and never stored.
Keys hashed, shown once
API keys and OAuth secrets are stored as SHA-256 hashes — the raw value never lands in the database.
Guard-railed writes
Write tools support dry-run previews; destructive and outward-facing actions (bulk email, void, cancel, delete) require explicit confirmation flags.
Tenant isolation
A key or login resolves to exactly one workspace. Account filters only narrow within it — there is no path to another customer's data.
Hosted in Sydney
The service and its data run in AWS ap-southeast-2, behind AWS WAF with rate limits on every authentication surface.
Read-only by default
New API keys can't write anything. Write scope exists — but only when you deliberately create it, acknowledge the risk, and take responsibility for the software holding it.
From $50 a month.
AutonAI is in closed beta. Pricing starts at $50 AUD/month per workspace — book a call, and if it fits we'll switch your accounts on the same day.
AutonAI workspace
- The Claude connector (MCP) — all 84 tools
- The REST API with scoped keys — read-only and read + write
- The customer portal: connections, keys and built-in dashboards
- Every ShiftCare account you manage, in one workspace
- Direct support from the person who built it
How activation works
- We confirm your ShiftCare setup fits (region, accounts, what you want from it)
- Your workspace is switched on the same day — access is per ShiftCare account
- Billing is by invoice during the beta; self-serve billing is coming
- No lock-in — access is turned off when you stop, and your keys die with it
Need hands-on ShiftCare help instead? Consulting, onboarding and team training are a separate service by the same builder — Paul Slater Consulting.
paulslaterconsulting.comPut your ShiftCare data to work.
Book a short call, see it against your own accounts, and walk away connected the same day — or not at all. No obligation either way.
Book a call