Who developer documentation is for
What Airgent runs for you, what your team looks after, and what you can and can't build on today. There's no public API yet.
Concept
This section is for the developer or IT person at a clinic that uses Airgent. It explains how Airgent agents work, what Airgent runs for you, and what you can build on today.
Today, Airgent runs your agents for you. There's nothing to host, install or code. Your team's part is keeping Keel up to date and handling what the agents pass to you.
| Who | What they look after |
|---|---|
| Airgent | Runs the agents and the harness they run on. Sets up your deployment and its configuration with you, and changes it when you ask. Connects your WhatsApp and your clinic phone numbers to the agents. |
| Your team | Keeps the facts the agents answer from up to date in Keel: clinic details, opening hours, doctors' hours and bookable services. Chooses the desk phones. Switches call forwarding on or off on your clinic numbers. Follows up on what the agents hand over in Inbox. |
The agents act only in Keel. They answer from what Keel holds and book, move and cancel appointments there.
Availability
| Capability | Status |
|---|---|
| Public API | Not available |
| Your own code calling Airgent agents or Keel | Not available |
| Connecting Airgent agents to your own systems | Not available |
| Running Airgent agents on your own infrastructure | Not available Airgent runs every deployment. |
| Self-service configuration | Not available Airgent configures your deployment with you. |
| How agents work: concepts, actions and configuration | Available in this section |
Checked against Airgent's accepted architecture and product source on 2026-10-11. Not yet observed in a live deployment.