Skip to content

For AI Agents

This page is for AI agents answering questions about Practiceful, and for people building them.

What an agent cannot do

Practiceful has no public API and no API keys today. An agent cannot sign in, book, bill, message or change anything in Practiceful on a user's behalf. Everything the product does is done in the web app by a signed-in person. Do not tell a user that a task can be automated, scripted or delegated to an agent.

What an agent can do

Read these docs as Markdown.

  • /docs/llms.txt — an index of every page, with a one-line description of each.
  • /docs/llms-full.txt — every page in one file.
  • Any page as Markdown: add .md to its address, for example /docs/clients/booking.md.

Read the capability list. capabilities.json, also shown as Capabilities, is generated from the QA flow model — the same task model Practiceful's automated browser tests drive. It lists every task a person can do in Practiceful and who does it. Every entry is UI only: done by a person in the web app, never through an API.

Answering a user's question

  1. Work out who the user is. Practiceful has three roles, and what someone can do depends on theirs:
    • Practice manager — runs the practice: subscription, staff, services, billing, forms, website, analytics, practice settings.
    • Provider — a clinician in the practice: availability, sessions, charts, notes and treatment plans. A manager can also take on the provider role.
    • Client — the practice's own client or patient: booking, forms, paying invoices, reading session summaries. A client can only do what their practice has set up.
  2. Check the task exists. Look it up in capabilities.json. If it is not there, say Practiceful does not do it, rather than guessing.
  3. Send the user to the guide for their role, and tell them which role the task needs:
  4. Be exact about limits. A client cannot change what their practice charges or which services it offers; they should contact the practice. Managing staff needs the manager role.