canonical: https://jentic.com/apis/letmc.com

# agentOS by letmc.com APIs

agentOS by letmc.com is a lettings and property-management platform for letting agents. Its agentOS V3 APIs let software read diary allocations, book, update, cancel, and give feedback on viewing appointments, search applicants, look up company branches, and raise maintenance jobs against a managed tenancy. The APIs are scoped to appointment scheduling and maintenance intake for a specific branch rather than the full lettings CRM.

## For AI agents

An agent can find open diary slots and book, reschedule, cancel, or give feedback on lettings viewing appointments, search applicants, route bookings to the right branch, and raise a maintenance job against a managed property, all on the agentOS V3 platform.

## Scope

Use for: Booking and managing lettings viewing appointments and raising property maintenance jobs against a branch on the agentOS V3 platform

Not supported:
- property listings
- tenancy contracts
- rent collection
- maintenance job closure
- full ticket lifecycle

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| agentOS API V3, Diary Call Group | productivity | 13 | Read diary allocations, book and update viewing appointments, manage recurring appointments, and search applicants for the agentOS lettings platform. |
| agentOS API V3, Maintenance Call Group | productivity | 1 | Create a new maintenance job for a specific letmc.com agentOS branch so that property maintenance work can be raised against an existing tenancy. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Book, reschedule, cancel, or give feedback on viewing appointments and search applicants | diary | The Diary Call Group reads allocations and manages appointments, recurring appointments, branches, and applicant search. |
| Raise a new property maintenance job against a branch and tenancy | maintenance | The Maintenance Call Group exposes the single createmaintenancejob operation that files a repair into agentOS. |

## Cross-API use cases

### Viewing to repair follow-up

An agent books a property viewing through the Diary Call Group, and when the applicant reports a fault seen at the viewing it raises a maintenance job for the same branch through the Maintenance Call Group. Both calls run against one branch credential so the handoff needs no second integration.

Example prompt: Book a viewing with the Diary Call Group, then post a maintenance job with the Maintenance Call Group for the same branch when a fault is reported.

### Branch-scoped lettings assistant

A chat assistant for one branch handles both sides of tenant contact: it reads open diary allocations to offer viewing slots and books them, and it files maintenance jobs for existing tenants. The Diary Call Group covers scheduling and the Maintenance Call Group covers repair intake, both pinned to the same branch short name.

Example prompt: Route applicant requests to the Diary Call Group for viewings and tenant repair requests to the Maintenance Call Group, scoped to a single branch.

### Property manager triage inbox

An agent triaging inbound tenant messages classifies each one and acts across both call groups: reschedule or cancel a viewing through the Diary Call Group, or open a repair through the Maintenance Call Group. This keeps the branch diary tidy and gets repairs into the back office without manual rekeying.

Example prompt: Classify each tenant message, then call the Diary Call Group to reschedule or cancel a viewing or the Maintenance Call Group to raise a repair job.

## Why Jentic

- **Setup:** Wiring the agentOS V3 APIs by hand means combining an ApiKey header with HTTP Basic credentials, targeting the live-api.letmc.com host, and threading the branch short name and IDs through every diary and maintenance path. With Jentic you install Jentic One once, add the agentOS Diary and Maintenance APIs from the Jentic directory, store the credentials once, and your agent calls both.
- **Permission scoping:** Both call groups put the branch short name in the URL path, so your own rules can pin an agent to one branch and to a chosen set of operations. You decide whether it may only read allocations and book viewings, or also cancel appointments and raise maintenance jobs.
- **Credential handling:** Your agentOS ApiKey and Basic credentials are stored encrypted by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context, and the same stored credential covers both call groups.
- **Discovery method:** An agent searches the Jentic directory by intent, such as booking a viewing or raising a maintenance job, and Jentic returns the matching agentOS operation with its input schema, so the agent picks the right diary or maintenance endpoint without parsing the letmc.com paths by hand.

## Related vendors

- **Calendly** — General-purpose scheduling API when the booking workflow is not lettings-specific.
- **Acuity Scheduling** — Hosted appointment booking pages as an alternative to agentOS diary scheduling.
- **PandaDoc** — Document automation for tenancy or works-order paperwork alongside maintenance jobs.

## FAQ

### What is agentOS by letmc.com and what can an agent do across its APIs?

agentOS is a lettings and property-management platform for letting agents. Across its two agentOS V3 APIs an agent can find diary allocations, book, update, cancel, and give feedback on viewing appointments, search applicants, look up branches, and raise maintenance jobs against a managed property.

### How many APIs does agentOS expose and how do they fit together?

There are two call groups. The Diary Call Group handles viewing appointments, recurring appointments, branch lookup, and applicant search. The Maintenance Call Group handles raising a new maintenance job. Together they cover the scheduling and repair-intake sides of the same branch.

### Do the agentOS APIs share the same authentication?

Yes. Both call groups use an ApiKey HTTP header plus HTTP Basic authentication issued per branch, against the same live-api.letmc.com host. One branch credential set works for both the diary and maintenance operations.

### Can one agent handle both viewings and maintenance for a branch?

Yes. Because both call groups address the same branch short name and share the same credential model, an agent can book a viewing through the Diary Call Group and raise a repair through the Maintenance Call Group in one flow without a separate integration for each.

### What is out of scope for the agentOS APIs?

These APIs do not cover property listings, tenancy contract creation, rent collection, or the full maintenance ticket lifecycle. The Maintenance Call Group only creates jobs; editing, closing, dispatch, and triage happen inside agentOS rather than over the API.

### How does an agent discover and call these APIs through Jentic?

Once Jentic One is installed, you or your agent can find and add the agentOS Diary and Maintenance APIs from the Jentic directory. The agent then searches by intent, such as booking a viewing or raising a repair, and Jentic returns the matching operation with its input schema.