Local services & SaaS
Faire
Orders, inventory, reorders and messages for wholesale brands.
12 endpoints
Your AI agent books services from calls, moves rain days, logs notes from callers and chases past-due invoices. Sign in to PestPac once in your own Cloud Browser. No API fee, no developer.
6 tools Read and write
PestPac has no MCP server, no ChatGPT or Claude app and no Zapier app. Its REST API comes through the WorkWave developer portal with "a one-time setup fee" and costs per data access and daily calls (PestPac, checked 9 Nov 2026). Cotlet runs 6 PestPac tools hosted, over MCP for agents and REST for scripts, in your own PestPac login.
| What you need | PestPac API | By hand | Cotlet |
|---|---|---|---|
| Customers and service orders | Setup fee | Yes, one by one | Yes |
| Schedule or move | Setup fee | Yes, one by one | Yes, after your OK |
| Past-due invoices | Setup fee | Report | Yes |
| Ask in ChatGPT or Claude | No | No | Yes |
| Developer needed | Yes | No | No |
Checked 8 Nov 2026. Sources: PestPac API and integrations · WorkWave developer portal · WorkWave product login
Once, in a browser we host for you.
One address in its settings.
It drafts the work, you OK what customers get.
We never keep your PestPac password, and no service is scheduled or moved until you approve it. Who can see your session
Sign in to PestPac in a Cloud Browser. Create a Cotlet account, open PestPac in its Cloud Browser, sign in with your PestPac login and press Enable for agents.
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.
PestPac shares the address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned PestPac on after connecting? Refresh the connector and the 6 tools appear.
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" Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth // ~/.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: pestpac_read Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: pestpac_write Search by name, address and phone. Notes reach no customer, so they run at once.
Returns customers with ID, location, active services and balance.
MCP callpestpac_read → list_customers
REST endpointGET https://cotlet.dev/api/v1/pestpac/customers
| Name | Type | Description |
|---|---|---|
| query string | string | Name, address or phone. |
| page integer | integer | Page number. Default: 1. |
{
"customers": [
{
"customer_id": "PP-40912",
"name": "Karen Delgado",
"location": "3021 Bayshore Blvd, Tampa, FL",
"services": [
"Quarterly pest"
],
"balance": "0.00"
}
],
"page": 1
} Appends a note such as a gate code. Reaches no customer, so it runs at once.
MCP callpestpac_write → add_customer_note
REST endpointPOST https://cotlet.dev/api/v1/pestpac/customers/{customer_id}/note
| Name | Type | Description |
|---|---|---|
| customer_id string required | string | Customer ID from list_customers. |
| note string required | string | Note text. |
{
"customer_id": "customer_8c41d2",
"note": "note"
} {
"customer_id": "PP-40912",
"note_added": "Gate code 2211, dog in yard"
} New and moved service orders wait for your OK.
Returns service orders with customer, service, technician, date and status.
MCP callpestpac_read → list_service_orders
REST endpointGET https://cotlet.dev/api/v1/pestpac/service-orders
| Name | Type | Description |
|---|---|---|
| date_from string required | string | ISO date. |
| date_to string | string | ISO date. Default: date_from. |
| tech string | string | Technician. |
| page integer | integer | Page number. Default: 1. |
{
"date_from": "date from"
} {
"orders": [
{
"order_id": "SO-77120",
"customer": "Mike Sullivan",
"service": "Termite inspection",
"tech": "Andre",
"date": "2026-11-10",
"status": "Scheduled"
}
],
"page": 1
} Puts the service on the schedule for the technician and date. Your settings decide whether the customer is notified. By default you confirm each call; you can switch that off for this tool.
MCP callpestpac_write → schedule_service_order
REST endpointPOST https://cotlet.dev/api/v1/pestpac/customers/{customer_id}/service-order/schedule
| Name | Type | Description |
|---|---|---|
| customer_id string required | string | Customer ID from list_customers. |
| service string required | string | Service type. |
| date string required | string | ISO date. |
| tech string | string | Technician. |
{
"customer_id": "PP-40912",
"service": "Re-service",
"date": "2026-11-11",
"tech": "Andre"
} {
"order_id": "SO-77188",
"customer": "Karen Delgado",
"service": "Re-service",
"tech": "Andre",
"date": "2026-11-11",
"status": "Scheduled"
} Moves the order, for example off a rained-out day. Your settings decide whether the customer is notified. By default you confirm each call; you can switch that off for this tool.
MCP callpestpac_write → reschedule_service_order
REST endpointPOST https://cotlet.dev/api/v1/pestpac/orders/{order_id}/service-order/reschedule
| Name | Type | Description |
|---|---|---|
| order_id string required | string | Service order ID from list_service_orders. |
| date string required | string | New ISO date. |
| tech string | string | New technician. |
{
"order_id": "order_8c41d2",
"date": "date"
} {
"order_id": "SO-77120",
"date": "2026-11-12",
"tech": "Andre",
"status": "Scheduled"
} Past-due invoices by age. Payments stay in PestPac.
Returns open invoices with customer, balance and days past due.
MCP callpestpac_read → list_unpaid_invoices
REST endpointGET https://cotlet.dev/api/v1/pestpac/unpaid-invoices
| Name | Type | Description |
|---|---|---|
| min_days_past_due integer | integer | Only invoices at least this many days past due. |
{
"invoices": [
{
"invoice_id": "PI-55102",
"customer": "Linda Cho",
"balance": "149.00",
"days_past_due": 31
}
]
} Your signed-in PestPac profile, AES-256-GCM encrypted, in Finland. No password.
The 6 PestPac tools, never the session cookie.
What your login sees: customers, locations, service orders, invoices.
Payments, routing optimization, chemical records, settings, deletes.
You sign in again yourself, in the same Cloud Browser.
Disable for agents, reset the browser, or change your PestPac password.
Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
When PestPac moves a button on the schedule or renames a customer tab, we fix the tool and your agent calls it the same way. status.cotlet.dev checks the site, console and API every 3 minutes.
| Action | Undo |
|---|---|
| Schedule or move a service order | Yes, move it back; a notice already sent stays sent |
| Add a note | Yes, edit it in PestPac |
2 of 6 tools ask first: schedule_service_order, reschedule_service_order. Customer notes reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine.
{
"name": "schedule_service_order",
"arguments": {
"customer_id": "PP-40912",
"service": "Re-service",
"date": "2026-11-11",
"tech": "Andre"
}
} curl -X POST https://cotlet.dev/api/v1/pestpac/customers/PP-40912/service-order/schedule \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"service":"Re-service","date":"2026-11-11","tech":"Andre"}' {
"order_id": "SO-77188",
"customer": "Karen Delgado",
"service": "Re-service",
"tech": "Andre",
"date": "2026-11-11",
"status": "Scheduled"
} A cron job or n8n flow can call the same tools over REST at /api/v1/pestpac with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path.
About $28 a monthfor a pest control company with 6 technicians, 4,750 credits. Your PestPac plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Service booked from a call | 2 × 80 | 1,600 |
| Rain day moved | 13 × 3 | 390 |
| Customer note logged | 2 × 50 | 1,000 |
| Past-due invoices, weekly | 1 × 4 | 40 |
| Tomorrow checked, daily | 1 × 22 | 220 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 4,750 |
PestPac publishes no stop counts, so the month is our example. Dollars at the $29 pack rate.
| 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 |
|---|---|---|
| PestPac API | Customers, service orders, billing and payments for your own developer. | Setup fee plus usage costs; you build and host the code. |
| Wavelytics | WorkWave's in-app analytics for churn and services per tech. | Reports inside PestPac; not your ChatGPT or Claude. |
| By hand | Every screen of PestPac, one stop at a time. | Your office's time. |
If you already pay for the WorkWave API and have a developer, building on it is cheaper for syncing data. To schedule, move rain days and chase invoices from ChatGPT or Claude this week, Cotlet works in the PestPac account you already have.
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the PestPac tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev, open PestPac under Integrations in the console and sign in to PestPac in its Cloud Browser. The trial starts with your first app and asks for no card.
Sign up at cotlet.dev, log in to PestPac once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your PestPac account through Cotlet, in their phone apps too.
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in PestPac: book re-services from calls; move a rain day; log what the caller said. You ask in plain words, and anything that reaches other people waits for your OK first.
No. PestPac has no ChatGPT or Claude connector of its own and PestPac has no official MCP server (checked 9 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.
Yes, with Cotlet. ChatGPT books re-services and new services with the technician and date you name, after your OK.
Yes, with Cotlet. ChatGPT moves a technician's exterior services to another day, after your OK, and lists what does not fit.
Yes, with Cotlet. ChatGPT lists open invoices by days past due, so the office knows whom to call.
PestPac is WorkWave's pest control software. This page covers PestPac; other WorkWave products such as RealGreen or RouteManager are separate apps.
Only in how it is called. Both carry the same 6 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
No. Cotlet is independent and not affiliated with PestPac or its owners WorkWave and IFS.
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