agentOS by letmc.com APIs for AI Agents
ProductivityCalendar SchedulingTask ManagementMixed ProvenanceapiKey, basicAgent Ready
agentOS by letmc.com API Catalog
2 APIs across 1 product group. All share one credential.
Productivity2
agentOS API V3, Diary Call GroupRead diary allocations, book and update viewing appointments, manage recurring appointments, and search applicants for the agentOS lettings platform.~13 endpointsagentOS API V3, Maintenance Call GroupCreate a new maintenance job for a specific letmc.com agentOS branch so that property maintenance work can be raised against an existing tenancy.~1 endpoint
Which agentOS by letmc.com API should I use?
| I want to... | Use | Why |
|---|---|---|
| Book, reschedule, cancel, or give feedback on viewing appointments and search applicants | agentOS API V3, Diary Call Group | 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 | agentOS API V3, Maintenance Call Group | The Maintenance Call Group exposes the single createmaintenancejob operation that files a repair into agentOS. |
Install Jentic One Beta
Connect the agentOS by letmc.com APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the agentOS by letmc.com APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fletmc.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fletmc.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “book a lettings viewing and raise a property maintenance job on agentOS”.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
FAQs
Specific to using agentOS by letmc.com APIs through Jentic.
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.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
