Local services & SaaS
FieldEdge
Work orders, dispatch, customers and invoices in FieldEdge.
10 endpoints
ServiceBox publishes no API and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted ServiceBox MCP server with 21 tools that ChatGPT and Claude use in your own ServiceBox user. Schedules, invoices and payments wait for your OK.
21 tools Read and write
ServiceBox publishes no public API. Its integrations and pricing pages list no developer reference, API key page or API plan, and no ServiceBox MCP server or ChatGPT or Claude connector exists. An MCP registry entry named "servicebox" belongs to an unrelated data service, not to this product.
| What you need | ServiceBox API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No API or MCP server | Copy and paste | Hosted MCP server |
| Work orders, scheduling and units | Not available | One screen at a time | 21 tools, writes after your OK |
| Bulk updates | Not available | Excel export and import | The same Excel route, run by the agent |
| Run from n8n or a script | Not available | Manual only | REST, same key |
Checked 15 Nov 2026. Sources: ServiceBox integrations · ServiceBox pricing · ServiceBox Learn · Learn: Creating Work Orders · Learn: Opening an Existing Work Order · Learn: Advanced Filter Options · Learn: Scheduling a Technician · Learn: Input Time for Multiple Technicians · Learn: Using Inventory in Work Orders · Learn: Service Charge Codes · Learn: Generating P.O's · Learn: Job Costing Work Orders · Learn: Managing Units for Job Sites · Learn: Enhanced Unit List · Learn: Importing/Exporting Units · Learn: Importing/Exporting Job Sites · Learn: Importing/Exporting Work Orders · Learn: Using Quotes for Service Agreements · Learn: Enhanced Invoice List · Learn: Enhanced Invoice Statistics · Learn: Delete or Adjust a Payment · Learn: Email Address Book
Once, in a browser we host for you.
One address in its settings.
It proposes the schedule, you approve it.
Your agent works in your own signed-in Cloud Browser. Schedules, invoices, payments and anything a customer or technician sees wait for your OK. Who can see your session
Sign in to ServiceBox in a Cloud Browser. Open jb.jobboxsoft.com/servicebox in your Cotlet Cloud Browser and sign in with your own ServiceBox 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.
ServiceBox sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned ServiceBox on after connecting? Refresh the connector and the 21 ServiceBox tools appear.
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: servicebox_read One tool per workflow in ServiceBox Learn. Read tools run at once; every write asks first.
Start here: most tools take a work order number. Assigning a work order and scheduling technicians are separate steps, as in ServiceBox.
Administrators see every work order in the list view; basic users see only those assigned to them, and the agent sees what your user sees. Advanced criteria work once "Use Advanced Criteria" is on in the work order list settings. It changes nothing and runs without asking.
MCP callservicebox_read → list_work_orders
REST endpointGET https://cotlet.dev/api/v1/servicebox/work-orders
| Name | Type | Description |
|---|---|---|
| work_order string | string | A work order number to open. Leave empty to list. |
| status string | string | Status as your ServiceBox shows it, for example Unscheduled or Scheduled. |
| assigned_to string | string | User the work orders are assigned to. |
| criteria object | object | Advanced criteria: custom fields marked "Use in Search" in Settings, Work Order, Custom Fields. |
| newest_first boolean | boolean | Sort by Created Date, newest first. Default oldest first, as ServiceBox lists them. |
{
"work_orders": [
{
"number": "WO-3038",
"bill_to": "Example Property Group",
"job_site": "200 Main St",
"status": "Unscheduled",
"assigned_to": "Dispatch"
},
{
"number": "WO-3041",
"bill_to": "Sample Foods",
"job_site": "Plant 2",
"status": "Scheduled",
"assigned_to": "Tech A"
}
]
} ServiceBox requires Bill To, Job Site, Assigned To, Status and Description to save a work order. The assigned user owns the order; scheduling a technician is a separate step in schedule_work_order. A salesperson is recorded through a custom field, as ServiceBox Learn suggests. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → save_work_order
REST endpointPOST https://cotlet.dev/api/v1/servicebox/work-order/save
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `update`. |
| work_order string | string | Work order number, for `update`. |
| bill_to string | string | Customer being billed. Required for `create`. |
| job_site string | string | Job site where the work happens. Required for `create`. |
| assigned_to string | string | User responsible for the work order. Required for `create`. |
| status string | string | Work order status; ServiceBox fills a default on create. |
| description string | string | Summary of the work. Required for `create`. |
| custom_fields object | object | Your company's work order custom fields by label, for example a Salesperson dropdown. |
{
"action": "action"
} {
"work_order": "WO-3042",
"bill_to": "Example Property Group",
"job_site": "200 Main St",
"assigned_to": "Dispatch",
"status": "Unscheduled",
"saved": true
} Assigning a work order does not schedule it: the scheduled users are the ones who go to site. Technicians see the work on their schedule, so each change waits for your OK. Group scheduling is the Schedule tab feature for a full crew. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → schedule_work_order
REST endpointPOST https://cotlet.dev/api/v1/servicebox/work-order/schedule
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as list_work_orders returns it. |
| technicians array | array | Users to schedule. Leave empty when you give `user_group`. |
| user_group string | string | A user group from Settings, Tenant, User Groups, to schedule the whole crew at once. |
| start string | string | ISO date and time. |
| end string | string | ISO date and time. |
| status string | string | Status to set after scheduling, for example Scheduled. |
{
"work_order": "WO-3038",
"technicians": [
"Tech A",
"Tech B"
],
"start": "2026-11-18T08:00",
"end": "2026-11-18T12:00",
"status": "Scheduled"
} {
"work_order": "WO-3038",
"scheduled": [
"Tech A",
"Tech B"
],
"start": "2026-11-18T08:00",
"end": "2026-11-18T12:00",
"status": "Scheduled"
} ServiceBox Learn recommends a checklist when you need a signature every day on one work order: the technician signs the checklist on site and ServiceBox keeps each signature. The agent attaches it; it never signs. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → attach_checklist
REST endpointPOST https://cotlet.dev/api/v1/servicebox/checklist/attach
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as list_work_orders returns it. |
| checklist string required | string | Checklist name, as set up in ServiceBox. |
| unit string | string | The unit the checklist is for, if it is a unit checklist. |
{
"work_order": "work order",
"checklist": "checklist"
} {
"work_order": "WO-3041",
"checklist": "Rooftop unit quarterly",
"unit": "RTU-3",
"attached": true
} What a job used and what it cost: inventory pulled from a location, service charge codes, P.O. numbers, then job costing against the quote.
Needs Inventory turned on in your ServiceBox. Unit cost comes from the item and cannot be edited here. Once added, the quantity leaves the chosen location, so the agent shows the item, location and quantity first. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → add_inventory_to_work_order
REST endpointPOST https://cotlet.dev/api/v1/servicebox/inventory-to-work-orders
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as list_work_orders returns it. |
| action string required | string | One of `availability`, `add`. `availability` only reads. |
| item string required | string | Item number or description. |
| location string | string | Inventory location to pull from. Default: the item's default location. |
| quantity number | number | Quantity used, for `add`. |
{
"work_order": "work order",
"action": "action",
"item": "item"
} {
"work_order": "WO-3041",
"item": "FLT-2020",
"description": "Pleated filter 20x20",
"location": "Main warehouse",
"quantity": 6,
"unit_cost": 7.5,
"added": true
} Needs the Service Charges feature on (Settings, Plan, Features). When the invoice is generated, ServiceBox reads the code, adds the charge to the invoice and can add hours to the technician's timesheet, so the code waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → add_service_charge
REST endpointPOST https://cotlet.dev/api/v1/servicebox/charges/{charge_code}/service-charges
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as list_work_orders returns it. |
| charge_code string required | string | A code set up under Settings, Work Order, Service Charges. |
| technician string | string | The technician whose labour line gets the code. |
{
"work_order": "work order",
"charge_code": "charge code"
} {
"work_order": "WO-3041",
"charge_code": "AFTERHRS",
"technician": "Tech A",
"saved": true
} ServiceBox tracks P.O. numbers in the work order's P.O. category; when the auto-generate setting is on it numbers them itself. To move an auto-generated number, remove it here and add it on the right work order; the setting stays yours to switch. Values flow to accounting with Time and Materials invoices. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → record_purchase_order
REST endpointPOST https://cotlet.dev/api/v1/servicebox/pos/{po_number}/purchase-orders
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as list_work_orders returns it. |
| action string required | string | One of `add`, `remove`. |
| po_number string required | string | For example 3038-1, the work order number with a suffix, as ServiceBox Learn suggests. |
| value number | number | P.O. value for `add`; 0 until you know it. |
| vendor string | string | Who the order is with. |
{
"work_order": "work order",
"action": "action",
"po_number": "po number"
} {
"work_order": "WO-3038",
"po_number": "3038-1",
"vendor": "Example Supply",
"value": 0,
"saved": true
} Reads the Job Costing file ServiceBox builds from a quote with a connected work order: a summary of quoted against actual amounts. Labour cost uses the fixed cost set on each user's profile, so users without one show no labour cost. It changes nothing.
MCP callservicebox_read → get_job_costing
REST endpointGET https://cotlet.dev/api/v1/servicebox/job-costing
| Name | Type | Description |
|---|---|---|
| work_order string required | string | Work order number, as list_work_orders returns it. |
{
"work_order": "work order"
} {
"work_order": "WO-3038",
"quote": "Q-1187",
"quoted": 4200,
"actual": 4710,
"difference": -510,
"lines": [
{
"type": "Labour",
"quoted": 1800,
"actual": 2160
},
{
"type": "Materials",
"quoted": 1900,
"actual": 2050
},
{
"type": "Purchase orders",
"quoted": 500,
"actual": 500
}
]
} Customer equipment by job site, with make, model and serial number, and the Excel route for bulk changes.
Returns the fields your Unit List shows (Settings, Unit), including custom fields marked "Display On Unit List", such as warranty or service interval. It changes nothing.
MCP callservicebox_read → list_units
REST endpointGET https://cotlet.dev/api/v1/servicebox/units
| Name | Type | Description |
|---|---|---|
| job_site string | string | Limit to one job site. |
| search string | string | Any field shown on your Unit List, for example a model or serial number. |
{
"units": [
{
"name": "RTU-3",
"job_site": "Plant 2",
"make": "Example Air",
"model": "XR-90",
"serial": "SN-44821"
},
{
"name": "Furnace 1",
"job_site": "200 Main St",
"make": "Sample Heat",
"model": "F-120",
"serial": "SN-10077"
}
]
} The same as a technician editing the unit from a work order (View Job Site, Details, Equipment). Delete Equipment removes the unit entirely, so the agent names the unit before it deletes. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → manage_units
REST endpointPOST https://cotlet.dev/api/v1/servicebox/units/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `update`, `delete`. |
| job_site string required | string | Job site the unit belongs to. |
| unit string | string | Unit name, for `update` and `delete`. |
| fields object | object | Description, location, make, model, serial number and your unit custom fields. |
{
"action": "action",
"job_site": "job site"
} {
"job_site": "Plant 2",
"unit": "RTU-3",
"fields": {
"make": "Example Air",
"model": "XR-90",
"serial": "SN-44821"
},
"saved": true
} Follows ServiceBox Learn: remove the accounting links of the old customer and the job site, then change the job site's customer and save. Your accounting software picks up the move with the next invoice sync for that job site. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → move_job_site
REST endpointPOST https://cotlet.dev/api/v1/servicebox/job-site/move
| Name | Type | Description |
|---|---|---|
| job_site string required | string | The job site to move. |
| from_customer string required | string | Current parent customer. |
| to_customer string required | string | New parent customer. |
{
"job_site": "job site",
"from_customer": "from customer",
"to_customer": "to customer"
} {
"job_site": "200 Main St",
"from_customer": "Example Holdings",
"to_customer": "Example Property Group",
"accounting_links_removed": 2,
"saved": true
} Rows with an ID update existing records; never change the ID column. Required columns are marked *. Job sites need an existing customer and units an existing job site. Quote items with Delete set to Yes are removed for future use, not from existing quotes; that import takes 10 to 15 minutes and ServiceBox emails the uploader. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → import_export_records
REST endpointPOST https://cotlet.dev/api/v1/servicebox/export-records
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `export`, `import`. `export` only reads. |
| records string required | string | One of `work_orders`, `job_sites`, `units`, `quote_items`. |
| job_site string | string | For `units`: the job site whose units to export or import. |
| file_url string | string | For `import`: the edited .xlsx, as a link the Cloud Browser can download. |
{
"action": "action",
"records": "records"
} {
"records": "units",
"job_site": "Plant 2",
"file": "ServiceBox Units for Plant 2.xlsx",
"rows": 3
} Find quotes by status, including expired ones, and draft service agreements as quotes.
A quote moves to Expired after the "Expire After Months" of its status and drops out of default lists and searches, so ask for `Expired` to find it. It changes nothing.
MCP callservicebox_read → list_quotes
REST endpointGET https://cotlet.dev/api/v1/servicebox/quotes
| Name | Type | Description |
|---|---|---|
| status string | string | Draft, Submitted, Awarded, Not Awarded, Expired or a status of your own. |
| customer string | string | Limit to one customer. |
{
"quotes": [
{
"number": "Q-1187",
"customer": "Example Property Group",
"status": "Awarded",
"total": 4200
},
{
"number": "Q-1192",
"customer": "Sample Foods",
"status": "Submitted",
"total": 2860
}
]
} ServiceBox Learn describes service agreements built as quotes: the customer approves the quote, then you set up the recurring work orders. The agent saves the quote as a draft; sending it stays a step you take. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → create_quote
REST endpointPOST https://cotlet.dev/api/v1/servicebox/quotes
| Name | Type | Description |
|---|---|---|
| bill_to string required | string | Customer. |
| job_site string required | string | Existing job site. |
| quote_information string | string | The agreement text: services and frequency (monthly, quarterly, biannual, yearly). |
| category string | string | Item category from Settings, Quotes, used for agreement lines. |
| items array | array | Description, quantity and price per line. |
{
"bill_to": "bill to",
"job_site": "job site"
} {
"quote": "Q-1193",
"bill_to": "Sample Foods",
"job_site": "Plant 2",
"status": "Draft",
"total": 3600,
"saved": true
} Writes Settings, Quotes, Print Setup, Closing Wording. The text appears on every quote you generate after the change, so the agent shows it to you first. Call again with the earlier text to put it back. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → set_quote_financing_terms
REST endpointPUT https://cotlet.dev/api/v1/servicebox/quote-financing-terms
| Name | Type | Description |
|---|---|---|
| closing_wording string required | string | The financing terms, in your words. |
{
"closing_wording": "closing wording"
} {
"closing_wording": "Financing available on approved credit. Ask us for monthly terms.",
"saved": true
} Invoices come from work orders. Creating and emailing are separate calls; a synced payment is refunded, never deleted.
Covers invoices for customers, job sites and work orders, each with its invoice number. It changes nothing.
MCP callservicebox_read → list_invoices
REST endpointGET https://cotlet.dev/api/v1/servicebox/invoices
| Name | Type | Description |
|---|---|---|
| status string | string | Invoice status, for example On Hold or Submitted. |
| location string | string | Location, when multi-location is on. |
| invoice string | string | An invoice number to open. |
{
"invoices": [
{
"number": "INV-5120",
"customer": "Example Property Group",
"work_order": "WO-3038",
"status": "Submitted",
"total": 4710
},
{
"number": "INV-5117",
"customer": "Sample Foods",
"work_order": "WO-3029",
"status": "On Hold",
"total": 980
}
]
} Open invoices are every status not flagged Paid or Voided in your settings, so a status like "Paid in QuickBooks Online" counts as open until it is flagged. Periods follow the Invoice Date, not the date created or paid.
MCP callservicebox_read → get_invoice_statistics
REST endpointGET https://cotlet.dev/api/v1/servicebox/invoice-statistics
| Name | Type | Description |
|---|---|---|
| from string | string | ISO date, by Invoice Date. |
| to string | string | ISO date, by Invoice Date. |
| work_order string | string | Limit to one work order. |
{
"from": "2026-11-01",
"to": "2026-11-15",
"open": {
"count": 14,
"total": 38250
},
"paid": {
"count": 9,
"total": 21400
},
"payments_received": 19800
} ServiceBox only creates invoices from work orders, so recurring service agreements are invoiced from a recurring work order. It has no in-app credit: Learn advises a note on the invoice and a credit memo in QuickBooks or Sage. Creating and sending are separate calls; a sent invoice has reached your customer. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → manage_invoices
REST endpointPOST https://cotlet.dev/api/v1/servicebox/invoices/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `create`, `send`. |
| work_order string required | string | Work order number, as list_work_orders returns it. |
| invoice string | string | Invoice number, for `send`. |
| copy_items_from_quote boolean | boolean | For `create`: copy the quote's line items, when ServiceBox support has turned that feature on. |
| note string | string | A note on the invoice, for example a credit to apply in your accounting software. |
| cover_message string | string | For `send`: the Invoice Email tab cover page, for example a deposit request. |
{
"action": "action",
"work_order": "work order"
} {
"invoice": "INV-5121",
"work_order": "WO-3041",
"total": 2860,
"note": "Deposit of $1,430 requested to order parts.",
"sent": false
} A payment not yet synced to your accounting system can be deleted and entered again. Once synced it cannot be deleted; a full or partial refund sends the reversing entry instead. The agent reads the sync state and picks the allowed action, then waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callservicebox_write → manage_payments
REST endpointPOST https://cotlet.dev/api/v1/servicebox/payments/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `add`, `delete`, `refund`. |
| invoice string required | string | Invoice number. |
| amount number | number | Payment or refund amount. |
| method string | string | Payment method, for `add`. |
{
"action": "action",
"invoice": "invoice"
} {
"invoice": "INV-5117",
"action": "refund",
"amount": 120,
"synced": true,
"saved": true
} Whether customers opened or clicked, and the right address to send to.
Delivery and open status show when your domain is verified with Postmark. An open is logged when the tracking image loads, so a customer whose mail client blocks images can read the email without it showing as opened; a portal click is the firmer signal.
MCP callservicebox_read → get_email_log
REST endpointGET https://cotlet.dev/api/v1/servicebox/email-log
| Name | Type | Description |
|---|---|---|
| customer string | string | Customer to check. |
| from string | string | ISO date. |
{
"customer": "Sample Foods",
"emails": [
{
"subject": "Invoice INV-5117",
"delivered": true,
"opened": false,
"portal_link_clicked": true
}
]
} The same address book ServiceBox opens beside the To, Cc and Bcc fields of its email tabs. Use it before manage_invoices sends, to address the right person. It changes nothing.
MCP callservicebox_read → search_address_book
REST endpointGET https://cotlet.dev/api/v1/servicebox/address-books/search
| Name | Type | Description |
|---|---|---|
| name string required | string | Name to search for. |
| type string | string | One of `customer`, `contact`, `vendor_order`, `user`. |
{
"name": "Jane Doe"
} {
"results": [
{
"name": "Accounts Payable, Sample Foods",
"type": "contact",
"email": "ap@example.com"
}
]
} Your signed-in ServiceBox browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 21 ServiceBox tools. The session cookie stays in the Cloud Browser.
The work orders, quotes and invoices your ServiceBox user can open. A basic user sees only work orders assigned to them.
Users and their costs, ServiceBox settings and features, and the QuickBooks or Sage sync itself.
You sign in again yourself, in the same Cloud Browser.
Disable ServiceBox for agents, reset the browser, or change your ServiceBox password.
Cotlet never sees or stores your password: you type it into ServiceBox yourself, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
ServiceBox Learn documents redesigned unit and invoice list screens and new import and export buttons. Cotlet watches the apps it serves and updates the ServiceBox server when screens like these change, so your agent keeps working without a change on your side.
Some tools depend on features your company turns on: Inventory, Service Charges, Advanced Criteria, and Copy Items from Quote, which ServiceBox support activates. While one is off in your ServiceBox, the tool that needs it cannot do that step.
If ServiceBox signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
| Action | How to put it right |
|---|---|
| Schedule, status, custom fields | Call schedule_work_order or save_work_order again with the earlier values |
| Inventory added to a job | Stock already left the location: transfer or adjust it in ServiceBox |
| Payment not yet synced | Delete it with manage_payments and enter it again |
| Payment already synced | Refund the difference; ServiceBox does not delete it |
| Invoice emailed | Already with your customer: send a corrected one |
All 13 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 8 read tools, from the work order list to the email log, run at once.
{
"name": "schedule_work_order",
"arguments": {
"work_order": "WO-3038",
"technicians": [
"Tech A",
"Tech B"
],
"start": "2026-11-18T08:00",
"end": "2026-11-18T12:00",
"status": "Scheduled"
}
} curl -X POST https://cotlet.dev/api/v1/servicebox/work-order/schedule \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"work_order":"WO-3038","technicians":["Tech A","Tech B"],"start":"2026-11-18T08:00","end":"2026-11-18T12:00","status":"Scheduled"}' {
"work_order": "WO-3038",
"scheduled": [
"Tech A",
"Tech B"
],
"start": "2026-11-18T08:00",
"end": "2026-11-18T12:00",
"status": "Scheduled"
} The example puts two technicians on a four-hour morning job and moves it out of the Unscheduled queue. A cron job or n8n flow can make the same call over REST at /api/v1/servicebox with the same key and price, in JSON. Failed calls are free.
About $25 a monthfor a commercial contractor with a small crew, 4,340 credits. Your ServiceBox plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning dispatch from the unscheduled queue | 5 × 20 | 1,000 |
| Inventory and service charges on jobs | 1 × 60 | 600 |
| Invoices created and emailed | 2 × 30 | 600 |
| Unit records after site visits | 2 × 10 | 200 |
| Friday job costing, six jobs | 6 × 4 | 240 |
| Unopened invoice follow-up | 3 × 4 | 120 |
| Agreement quotes | 1 × 8 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 284 calls | 4,340 |
The smallest pack, 5,000 credits for $29, covers this month. More crews and work orders use more calls.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer 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 |
|---|---|---|
| ServiceBox screens | Everything, signed in as you. | One work order at a time, at the office computer. |
| Excel import and export | Bulk changes to work orders, job sites, units and quote items. | You fill the workbook by hand and keep the ID column intact. |
| QuickBooks and Sage sync | Sends invoices and payments to accounting. | An accounting handoff, not a route for an AI agent. |
| ServiceBox mobile apps | Technicians work their orders in the field. | Field work, not office automation. |
ServiceBox has no API, so no official route lets an agent in. Cotlet fits when you want ChatGPT, Claude or a script to schedule, cost and invoice in ServiceBox from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the ServiceBox tools.
Sign up free at https://cotlet.dev/signup?app=servicebox, turn on ServiceBox under Integrations in the console and sign in at https://jb.jobboxsoft.com/servicebox in your Cloud Browser. Then connect your AI agent and ask it for your unscheduled work orders. The trial needs no card.
ServiceBox publishes no public API: its integrations and pricing pages list no developer reference, API key page or API plan (checked 15 Nov 2026). There is no ServiceBox MCP server and no official ChatGPT or Claude connector. Cotlet does not need one: it works in your own signed-in ServiceBox user.
No. ServiceBox connects to QuickBooks Online, QuickBooks Desktop and Sage 50 Canada itself, and you run the sync in ServiceBox. No tool changes that connection; move_job_site only removes the accounting links ServiceBox Learn says to remove before a move.
An administrator if the agent should see every work order. ServiceBox shows basic users only the work orders assigned to them, and the agent sees exactly what the signed-in user sees.
Through service charge codes: when the invoice is generated, ServiceBox can add the code's hours to the technician's timesheet. The tools do not edit timesheets directly.
Only in how it is called. Both carry the same 21 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 ServiceBox or Jobbox Software.
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