Local services & SaaS
DaySmart
Appointments, clients, pets and sales in DaySmart Salon or Pet.
15 endpoints
RunLoyal's Partner APIs cover the pet owner booking flow, and no RunLoyal MCP server was found (checked 17 Nov 2026). Cotlet runs a hosted RunLoyal MCP server with 40 tools that ChatGPT and Claude use in your own Business Portal. Report cards, messages, bookings and refunds wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by RunLoyal. RunLoyal is a trademark of its owner. If RunLoyal's own integrations cover what you need, use them first.
40 tools Read and write
RunLoyal publishes Partner API documentation at api.runloyal.com. Its endpoints follow the pet owner booking flow: sign-in, pets, immunizations, appointments, invoices, gift cards and rewards. How a business gets credentials is not stated, and no RunLoyal MCP server or official ChatGPT or Claude connector was found.
| What you need | Partner API | By hand | Cotlet |
|---|---|---|---|
| Book stays and manage pet profiles | Pet owner side, partner access | At the desk | Writes after your OK |
| Check-ins, report cards and messages | Not in the API | One pet at a time | Drafted, sent after your OK |
| Paw Metrics, timesheets and settings | Not in the API | Screen by screen | 40 tools in all |
| Ask ChatGPT or Claude to do the work | No MCP server found | Copy and paste | Hosted MCP server |
Checked 17 Nov 2026. Sources: RunLoyal Partner APIs · RunLoyal FAQ · RunLoyal knowledge base · KB: Using the Pet Count Dashboard · KB: Sending Report Cards · KB: Creating and Managing Appointments · KB: View estimate · KB: Vax Verify in Business Portal · KB: Push Marketing · KB: Membership Reporting
Once, in a browser we host for you.
One address in its settings.
Quote a stay, then approve the booking.
Your agent works in your own signed-in Cloud Browser. Anything a pet owner receives or pays waits for your OK. Who can see your session
Sign in to RunLoyal in a Cloud Browser. Open your RunLoyal Business Portal in your Cotlet Cloud Browser and sign in with your own staff user.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
RunLoyal is served from the shared address https://cotlet.dev/mcp/v1, the same one as every other app you turn on. Added RunLoyal later? Refresh the connector to pick up its 40 tools.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: runloyal_read One tool per workflow in the RunLoyal knowledge base. Dashboards, reports and links only read; everything else writes and asks first.
Pet counts by service, the calendar with lodging rooms, run cards from the To-Do tab and the Digital Wall queue.
Returns the pets per service for the day. Switch days to compare.
MCP callrunloyal_read → view_pet_count
REST endpointGET https://cotlet.dev/api/v1/runloyal/pet-counts/view
| Name | Type | Description |
|---|---|---|
| date string | string | ISO date. Defaults to today. |
| service string | string | Isolate one service, for example Daycare. |
{
"date": "2026-11-18",
"counts": [
{
"service": "Boarding",
"pets": 34
},
{
"service": "Daycare",
"pets": 41
},
{
"service": "Grooming",
"pets": 9
}
]
} Lodging shows incoming and outgoing dogs per room, so you can see where a room frees up.
MCP callrunloyal_read → view_calendar
REST endpointGET https://cotlet.dev/api/v1/runloyal/calendars/view
| Name | Type | Description |
|---|---|---|
| section string required | string | One of `capacity`, `lodging`. |
| date string | string | ISO date. Defaults to today. |
| view string | string | Occupied rooms or all rooms. |
{
"section": "section"
} {
"section": "lodging",
"date": "2026-11-18",
"rooms": [
{
"room": "Suite 4",
"pet": "Biscuit",
"out": "2026-11-20"
},
{
"room": "Suite 5",
"pet": null
}
]
} Returns the run cards for printing. It changes nothing.
MCP callrunloyal_read → get_run_cards
REST endpointGET https://cotlet.dev/api/v1/runloyal/run-cards
| Name | Type | Description |
|---|---|---|
| status string | string | One of `all`, `confirmed`, `checked_in`. |
| pets array | array | Only these pets. |
{
"run_cards": 27,
"file": "run-cards-2026-11-18.pdf"
} The same list the front desk sends to the staff TV.
MCP callrunloyal_read → view_digital_wall
REST endpointGET https://cotlet.dev/api/v1/runloyal/digital-walls/view
No parameters.
{
"queue": [
{
"pet": "Biscuit",
"direction": "pickup",
"queued": "17:42"
}
]
} Route Optimizer is a paid add-on enabled by RunLoyal; it maps the route from the kennel to each pet owner's address. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → plan_transport_route
REST endpointPOST https://cotlet.dev/api/v1/runloyal/transport-route/plan
| Name | Type | Description |
|---|---|---|
| date string | string | ISO date. Defaults to today. |
{
"date": "2026-11-18",
"stops": 5,
"order": [
"Kennel",
"Example Owner",
"Sample Owner",
"Kennel"
]
} Estimates with the real pricing rules, appointments, check-in and out, room moves, feeding and medication, staff notes and incidents.
Uses the same pricing rules as the final invoice: multi-night discounts, holiday and weekend surcharges, breed-based pricing and taxes. If details change, the invoice can differ.
MCP callrunloyal_read → view_estimate
REST endpointGET https://cotlet.dev/api/v1/runloyal/estimates/view
| Name | Type | Description |
|---|---|---|
| owner string required | string | Pet owner name, email or phone. |
| pets array required | array | Pets. |
| service string required | string | Service. |
| start string required | string | ISO date. |
| end string | string | ISO date. |
{
"owner": "owner",
"pets": "pets",
"service": "service",
"start": "start"
} {
"service": "Overnight Boarding Standard Suite",
"nights": 4,
"estimate": 286,
"tax": 22.88,
"total": 308.88
} Bookings reach the pet owner and use capacity, so the agent shows service, dates and pets first. Run view_estimate to show the price. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_appointments
REST endpointPOST https://cotlet.dev/api/v1/runloyal/appointments/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `cancel`. `list` and `get` only read. |
| owner string | string | Pet owner. |
| pets array | array | Pets of that owner. |
| service string | string | Boarding, daycare, grooming or another configured service. |
| start string | string | ISO date and time. |
| end string | string | ISO date and time. |
| add_ons array | array | Add-ons such as an exit bath. |
| repeat object | object | Recurrence for repeating appointments. |
{
"action": "create",
"owner": "Example Owner",
"pets": [
"Biscuit"
],
"service": "Overnight Boarding Standard Suite",
"start": "2026-11-21",
"end": "2026-11-25",
"add_ons": [
"Exit bath"
]
} {
"appointment": "APT-48211",
"owner": "Example Owner",
"pets": [
"Biscuit"
],
"service": "Overnight Boarding Standard Suite",
"start": "2026-11-21",
"end": "2026-11-25",
"status": "Confirmed"
} Only a Confirmed appointment can be checked in. Check-out leads to the invoice. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → check_in_out
REST endpointPOST https://cotlet.dev/api/v1/runloyal/out/check
| Name | Type | Description |
|---|---|---|
| appointment string required | string | Appointment, as manage_appointments `list` returns it. |
| direction string required | string | One of `in`, `out`. |
| belongings string | string | What the pet arrived with. |
| notes string | string | Appointment notes. |
{
"appointment": "appointment",
"direction": "direction"
} {
"appointment": "APT-48211",
"pet": "Biscuit",
"status": "Checked In",
"belongings": "Blue leash, own food"
} A different room can change the price, so the agent asks whether to update the invoice. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → move_room
REST endpointPOST https://cotlet.dev/api/v1/runloyal/room/move
| Name | Type | Description |
|---|---|---|
| appointment string required | string | Appointment, as manage_appointments `list` returns it. |
| room string required | string | Target room. |
| days string | string | One of `today`, `all_future`. |
| update_invoice boolean | boolean | Update the invoice to the new room's price. |
{
"appointment": "appointment",
"room": "room"
} {
"appointment": "APT-48211",
"room": "Suite 5",
"invoice_updated": false
} Staff follow this during the stay, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → record_feeding_medication
REST endpointPOST https://cotlet.dev/api/v1/runloyal/feeding-medications
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `update`. `list` and `get` only read. |
| pet string required | string | Pet name with owner, as manage_pets `list` returns it. |
| feeding array | array | Type (AM, midday, PM), amount and unit (cup, scoop, bag, can). |
| medication array | array | Name, dose and times. |
{
"action": "action",
"pet": "pet"
} {
"pet": "Biscuit",
"feeding": [
{
"type": "AM",
"amount": 1,
"unit": "cup"
},
{
"type": "PM",
"amount": 1,
"unit": "cup"
}
]
} Staff notes are internal and not visible to the pet owner. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → add_staff_note
REST endpointPOST https://cotlet.dev/api/v1/runloyal/staff-notes
| Name | Type | Description |
|---|---|---|
| appointment string required | string | Appointment, as manage_appointments `list` returns it. |
| text string required | string | The note. |
| pin boolean | boolean | Pin it. |
{
"appointment": "appointment",
"text": "text"
} {
"appointment": "APT-48211",
"note": "Eats slowly, give 20 minutes.",
"pinned": true
} An incident is a lasting record on the pet, so the agent writes only what you tell it. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → record_incident
REST endpointPOST https://cotlet.dev/api/v1/runloyal/incidents
| Name | Type | Description |
|---|---|---|
| pet string required | string | Pet name with owner, as manage_pets `list` returns it. |
| type string required | string | Incident type from Settings > Operations > Pet Incidents. |
| details object required | object | Answers to the type's headings. |
{
"pet": "pet",
"type": "type",
"details": "details"
} {
"pet": "Biscuit",
"type": "Minor scuffle",
"saved": true
} Pet and owner profiles, Vax Verify review, agreement requests, tags with alerts and training homework.
Removing a pet is named before it happens. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_pets
REST endpointPOST https://cotlet.dev/api/v1/runloyal/pets/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `remove`. `list` and `get` only read. |
| owner string | string | Pet owner. |
| pet string | string | Pet, for `get`, `update`, `remove`. |
| fields object | object | Name, breed, size and other pet details. |
{
"action": "action"
} {
"owner": "Example Owner",
"pet": "Biscuit",
"breed": "Beagle",
"saved": true
} Run `list` first so the same family is not added twice. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_pet_owners
REST endpointPOST https://cotlet.dev/api/v1/runloyal/pet-owners/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `block`. `list` and `get` only read. |
| owner string | string | Pet owner, for `get`, `update`, `block`. |
| fields object | object | First and last name, email or phone, other details. |
{
"action": "action"
} {
"owner": "Example Owner",
"email": "owner@example.com",
"saved": true
} Vax Verify is a paid add-on. Where a vaccine name did not match, staff must review it; the agent shows those first. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → verify_vaccinations
REST endpointPOST https://cotlet.dev/api/v1/runloyal/vaccinations/verify
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `confirm`, `update`. `list` and `get` only read. |
| pet string | string | Pet. |
| vaccines array | array | Vaccine and expiry date, for `update`. |
{
"action": "action"
} {
"pending": [
{
"pet": "Biscuit",
"vaccine": "Rabies",
"expires": "2027-03-02",
"needs_review": false
}
]
} The owner gets it in the app or by email to sign. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → send_agreement_request
REST endpointPOST https://cotlet.dev/api/v1/runloyal/agreement-requests
| Name | Type | Description |
|---|---|---|
| owner string required | string | Pet owner name, email or phone. |
| agreements array required | array | Agreements to request. |
{
"owner": "owner",
"agreements": "agreements"
} {
"owner": "Example Owner",
"agreements": [
"Boarding Agreement"
],
"requested": true
} Pet owners see the homework in the app. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_curriculum
REST endpointPOST https://cotlet.dev/api/v1/runloyal/curriculum/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `add_homework`. `list` and `get` only read. |
| lesson string | string | Lesson name, for example Introduction & Socialization. |
| homework object | object | Name and whether owners upload photos or videos. |
{
"action": "action"
} {
"lesson": "Loose leash walking",
"homework": "Two 5 minute walks a day",
"media_upload": true,
"saved": true
} Report cards, Message Hub, Push Marketing campaigns, review requests, booking links and the rewards program.
Report cards reach pet owners, so the agent shows each one before sending. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → send_report_card
REST endpointPOST https://cotlet.dev/api/v1/runloyal/report-cards
| Name | Type | Description |
|---|---|---|
| pets array required | array | Pets with appointments today. |
| notes string required | string | Activities, energy level, favorite playmates and so on. |
| photos array | array | Photo links. |
{
"pets": "pets",
"notes": "notes"
} {
"sent": 1,
"pet": "Biscuit",
"owner": "Example Owner"
} By default messages go through the app, or email if the owner has no app notifications. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → send_message
REST endpointPOST https://cotlet.dev/api/v1/runloyal/messages
| Name | Type | Description |
|---|---|---|
| owner string required | string | Pet owner name, email or phone. |
| text string required | string | The message. |
| channel string | string | One of `app`, `sms`. SMS needs the SMS add-on. |
{
"owner": "owner",
"text": "text"
} {
"owner": "Example Owner",
"channel": "app",
"sent": true
} A campaign reaches many customers at once, so the agent shows segment, count and text first. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → send_campaign
REST endpointPOST https://cotlet.dev/api/v1/runloyal/campaigns
| Name | Type | Description |
|---|---|---|
| segment string required | string | All pet owners, visited in the last 3 months, a service type, birthdays this month and so on. |
| channels array required | array | `email`, `app`, `sms`. |
| subject string | string | Subject. |
| text string required | string | Message. |
{
"segment": "segment",
"channels": "channels",
"text": "text"
} {
"segment": "Birthdays this month",
"recipients": 58,
"channels": [
"email",
"app"
],
"sent": true
} The request reaches the pet owner after checkout. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_reviews
REST endpointPOST https://cotlet.dev/api/v1/runloyal/reviews/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `request`. `list` and `get` only read. |
| appointment string | string | For `request`. |
{
"action": "action"
} {
"reviews": [
{
"owner": "Example Owner",
"rating": 5,
"text": "Biscuit came home happy."
}
]
} From Settings > Promotion > Web Links. It changes nothing.
MCP callrunloyal_read → get_web_links
REST endpointGET https://cotlet.dev/api/v1/runloyal/web-links
No parameters.
{
"booking_link": "https://example.com/book",
"app_link": "https://example.com/app",
"qr_code": "https://example.com/qr.png"
} Points come from invoice payments and lower future bills, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_rewards
REST endpointPOST https://cotlet.dev/api/v1/runloyal/rewards/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `list` and `get` only read. |
| earning object | object | By spend ranges or by item type. |
| redemption object | object | Points per discount. |
{
"action": "action"
} {
"earning": {
"per_dollar": 1
},
"redemption": {
"points": 500,
"discount": 10
}
} Open invoices, refunds, tips, coupons, packages, memberships, e-gift cards and retail products. Everything here changes what owners pay.
Open Invoice lists every unpaid invoice. Changes go through the payment, coupon and refund tools.
MCP callrunloyal_read → view_open_invoices
REST endpointGET https://cotlet.dev/api/v1/runloyal/open-invoices/view
| Name | Type | Description |
|---|---|---|
| invoice string | string | Invoice number. Leave empty to list all open invoices. |
{
"open_invoices": [
{
"invoice": "INV-9-8552",
"owner": "Example Owner",
"total": 312.5
}
]
} A refund returns money to the customer and cannot be undone by the agent. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → refund_invoice
REST endpointPOST https://cotlet.dev/api/v1/runloyal/invoice/refund
| Name | Type | Description |
|---|---|---|
| invoice string required | string | Invoice number. |
| type string required | string | One of `items_and_payment`, `payment_only`. |
| items array | array | Items to refund. |
| clear_balance boolean | boolean | For `payment_only`: clear the balance or leave it due. |
{
"invoice": "invoice",
"type": "type"
} {
"invoice": "INV-9-8552",
"refunded": 45,
"balance_due": 0
} Needs permission to manage Pricing. Tip choices show on terminals and checkout. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_tips
REST endpointPOST https://cotlet.dev/api/v1/runloyal/tips/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `list` and `get` only read. |
| settings object | object | Tip type, quick-pick percentages and how tips are calculated. |
{
"action": "action"
} {
"type": "percent",
"quick_picks": [
15,
18,
20
]
} Coupons can cover services, packages, memberships and products, once or recurring. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_coupons
REST endpointPOST https://cotlet.dev/api/v1/runloyal/coupons/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `apply`. `list` and `get` only read. |
| name string | string | Coupon name. |
| code string | string | Code. |
| discount string | string | Percent or amount. |
| expires string | string | ISO date. |
| invoice string | string | For `apply`. |
{
"action": "action"
} {
"coupon": "Weekday daycare",
"code": "WEEKDAY10",
"discount": "10%",
"saved": true
} Settings > Retail > Packages. Customers buy them, so price changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_packages
REST endpointPOST https://cotlet.dev/api/v1/runloyal/packages/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| name string | string | Package name. |
| credits array | array | Service and number of credits. |
| price number | number | Price. |
{
"action": "action"
} {
"package": "10 Day Daycare Pack",
"credits": [
{
"service": "Daycare",
"credits": 10
}
],
"price": 320,
"saved": true
} Memberships are a paid add-on and charge the owner, so each change waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_memberships
REST endpointPOST https://cotlet.dev/api/v1/runloyal/memberships/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `enroll`, `pause`, `cancel`. `list` and `get` only read. |
| owner string required | string | Pet owner name, email or phone. |
| membership string | string | Membership. |
{
"action": "action",
"owner": "owner"
} {
"owner": "Example Owner",
"membership": "Monthly Park Pass",
"status": "Active",
"auto_renew": true
} This moves money on the owner's account, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_gift_cards
REST endpointPOST https://cotlet.dev/api/v1/runloyal/gift-cards/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `sell`, `apply`. `list` and `get` only read. |
| owner string required | string | Pet owner name, email or phone. |
| amount number | number | Amount, for `sell`. |
| invoice string | string | For `apply`. |
{
"action": "action",
"owner": "owner"
} {
"owner": "Example Owner",
"gift_card": 50,
"balance": 50
} Products added at Organization level are available at every location; a SKU is generated. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_retail_products
REST endpointPOST https://cotlet.dev/api/v1/runloyal/retail-products/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `sell`. `list` and `get` only read. |
| name string | string | Product name. |
| upc string | string | UPC. |
| owner string | string | For `sell`: the customer. |
{
"action": "action"
} {
"product": "Salmon training treats",
"upc": "000000000001",
"sku": "SKU-1042",
"saved": true
} Paw Metrics, membership and owner reports, timesheets, services, Dynamic Pricing, staff groups and business hours.
Which reports exist for the signed-in user follows its staff group settings.
MCP callrunloyal_read → run_paw_metrics_report
REST endpointGET https://cotlet.dev/api/v1/runloyal/paw-metrics-reports/run
| Name | Type | Description |
|---|---|---|
| report string required | string | Report name, as Paw Metrics lists it. |
| from string required | string | ISO start date. |
| to string required | string | ISO end date. |
{
"report": "report",
"from": "from",
"to": "to"
} {
"report": "Revenue by Service",
"rows": [
{
"service": "Boarding",
"revenue": 18420
},
{
"service": "Daycare",
"revenue": 12960
}
]
} Returns each member with membership type and auto renewal.
MCP callrunloyal_read → view_membership_report
REST endpointGET https://cotlet.dev/api/v1/runloyal/membership-reports/view
| Name | Type | Description |
|---|---|---|
| membership_type string | string | Monthly or annual membership type. |
| auto_renew boolean | boolean | Filter by auto renewal. |
{
"members": [
{
"owner": "Example Owner",
"membership": "Monthly Park Pass",
"auto_renew": false
}
]
} A contact export for the date range. Handle it as your customers' personal data.
MCP callrunloyal_read → export_pet_owner_details
REST endpointGET https://cotlet.dev/api/v1/runloyal/pet-owner-details/export
| Name | Type | Description |
|---|---|---|
| from string required | string | ISO start date. |
| to string required | string | ISO end date. |
| format string | string | One of `csv`, `excel`, `pdf`. |
{
"from": "from",
"to": "to"
} {
"report": "Pet Owner Details",
"rows": 612,
"file": "pet-owner-details.csv"
} Corrections change paid hours, so they wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → edit_timesheets
REST endpointPATCH https://cotlet.dev/api/v1/runloyal/timesheets
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `update`. `list` and `get` only read. |
| staff string | string | Staff member. |
| facility string | string | Facility. |
| entry object | object | For `update`: date, clock in and clock out. |
{
"action": "action"
} {
"staff": "Kennel tech A",
"date": "2026-11-17",
"clock_in": "06:58",
"clock_out": "15:04",
"hours": 7.6
} Lodging availability comes from the number of runs, or spots for cage-free boarding. Services show in booking for your customers. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_services
REST endpointPOST https://cotlet.dev/api/v1/runloyal/services/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| category string | string | Service category, for example Overnight Boarding. |
| service object | object | Name, runs or spots, price and optional add-ons. |
{
"action": "action"
} {
"category": "Overnight Boarding",
"service": "Overnight Boarding Luxury Suite",
"saved": true
} Dynamic Pricing is an add-on. Rules change what customers pay, so they wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_dynamic_pricing
REST endpointPOST https://cotlet.dev/api/v1/runloyal/dynamic-pricing/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| rule string | string | Rule name, for example Boarding Discount for Weekdays. |
| services array | array | Services it applies to. |
| booking_days object | object | Booking day range. |
| capacity object | object | Capacity threshold and price change. |
{
"action": "action"
} {
"rule": "Daycare Price Increase for Full Capacity",
"capacity_over": "85%",
"change": "+10%",
"saved": true
} Admin and Staff are default groups and cannot be edited. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_staff_groups
REST endpointPOST https://cotlet.dev/api/v1/runloyal/staff-groups/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| group string | string | Group name, for example Manager. |
| permissions array | array | Sections, actions and reports allowed. |
{
"action": "action"
} {
"group": "Manager",
"permissions": 24,
"saved": true
} Hours set the earliest drop-off and latest pickup in both portals. By default you confirm each call; you can switch that off for this tool.
MCP callrunloyal_write → manage_business_hours
REST endpointPOST https://cotlet.dev/api/v1/runloyal/business-hours/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`. `list` and `get` only read. |
| hours array | array | Days or date ranges with open and close times. |
| closed array | array | Closed dates or weekdays. |
{
"action": "action"
} {
"hours": [
{
"days": "Mon-Fri",
"open": "07:00",
"close": "19:00"
}
],
"closed": [
"2026-12-25"
]
} Your signed-in RunLoyal browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 40 RunLoyal tools. The session cookie stays in the Cloud Browser.
The pets, owners, bookings and reports your staff group may open.
Payment processing and card terminals, your RunLoyal subscription and add-ons, the Zapier and Mailchimp connections, staff users.
You sign in again yourself, in the same Cloud Browser.
Disable RunLoyal for agents, reset the browser, or change your RunLoyal password.
Cotlet never sees or stores your password: you type it in yourself, and from then on the agent uses only the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Appointment dates or room | Call manage_appointments or move_room again with the right values |
| Pet details, tags, feeding | Update them again with the same tool |
| Report card, message or campaign | Already delivered: follow up with the owners |
| Refund | Money is back with the owner: charge again only with their agreement |
All 30 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 10 read tools, counts, calendar, reports and links, run at once.
{
"name": "manage_appointments",
"arguments": {
"action": "create",
"owner": "Example Owner",
"pets": [
"Biscuit"
],
"service": "Overnight Boarding Standard Suite",
"start": "2026-11-21",
"end": "2026-11-25",
"add_ons": [
"Exit bath"
]
}
} curl -X POST https://cotlet.dev/api/v1/runloyal/appointments/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","owner":"Example Owner","pets":["Biscuit"],"service":"Overnight Boarding Standard Suite","start":"2026-11-21","end":"2026-11-25","add_ons":["Exit bath"]}' {
"appointment": "APT-48211",
"owner": "Example Owner",
"pets": [
"Biscuit"
],
"service": "Overnight Boarding Standard Suite",
"start": "2026-11-21",
"end": "2026-11-25",
"status": "Confirmed"
} The example books Biscuit into a standard suite from 21 to 25 November with an exit bath. A cron job or n8n flow can make the same call over REST at /api/v1/runloyal with the same key and price, in JSON. Failed calls are free.
About $21 a monthfor a pet resort with boarding, daycare and grooming, 3,620 credits. Your RunLoyal plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Evening pet count and free rooms | 2 × 30 | 600 |
| Daycare report cards, sent in bulk | 2 × 22 | 440 |
| Stays quoted and booked | 2 × 40 | 800 |
| Vaccination review and owner messages | 6 × 4 | 240 |
| Membership and birthday campaigns | 4 × 1 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 212 calls | 3,620 |
The smallest pack, 5,000 credits for $29, covers this month. Holiday season brings more stays and more calls.
Credit packs are paid once, not monthly. The month above is our own estimate of a resort's workload, not measured usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| RunLoyal Partner APIs | Pet owner sign-in, pets, bookings, invoices, gift cards and rewards. | No front desk, report card, messaging or reporting endpoints; credentials through RunLoyal. |
| Zapier integration | Connects RunLoyal to other tools, set up per RunLoyal's knowledge base. | Whatever triggers and actions the Zapier app offers. |
| Mailchimp integration | More advanced campaign work in Mailchimp. | Marketing only. |
| Scout AI | RunLoyal's built-in AI for notes, messages and photos. | Inside RunLoyal, not your ChatGPT or Claude. |
If you build a booking app as a RunLoyal partner, the Partner APIs are the route. Cotlet fits when ChatGPT, Claude or a script should do the front desk and owner work in RunLoyal, from your own login, with nothing to host.
Cotlet is a product of Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, with Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing) as founders. Questions about the RunLoyal tools: contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=runloyal, turn on RunLoyal under Integrations in the console and sign in to your RunLoyal Business Portal in your Cloud Browser. Then connect your AI agent and ask for tomorrow's pet count. The trial needs no card.
RunLoyal publishes Partner API documentation at api.runloyal.com; it covers the pet owner booking flow, and how a business gets credentials is not stated. RunLoyal also connects to Zapier and Mailchimp. No RunLoyal MCP server or official ChatGPT or Claude connector was found (checked 17 Nov 2026). Cotlet works in your own signed-in Business Portal instead.
Scout AI is RunLoyal's own AI inside the platform: report card notes and messages, photo enhancement and scheduling trends, with Vax Verify as a paid add-on. Cotlet lets ChatGPT, Claude or your script work across the Business Portal with the same tools over MCP or REST.
Only if your RunLoyal account has them. Memberships, Dynamic Pricing, Vax Verify, Route Optimizer and SMS are add-ons; their tools work only when RunLoyal has enabled them for you.
A staff user in the group whose work the agent should do. Staff groups decide which sections, actions and reports a user sees, and the agent sees the same. Admin and Staff are RunLoyal's default groups.
Only in how it is called. Both carry the same 40 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with RunLoyal.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy