Local services & SaaS
Buildertrend
Schedules, daily logs, change orders and selections for builders.
12 endpoints
Billdr documents an API key only for its Zapier integration, on the Titanium plan, and no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Billdr MCP server with 18 tools that ChatGPT and Claude use in your own contractor account. Quotes, change orders, invoices and anything that reaches a client, a sub or your crew wait for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Billdr. Billdr is a trademark of its owner. If Billdr's own integrations cover what you need, use them first.
18 tools Read and write
Billdr publishes no public API documentation. Its help center documents one API key, made under Settings > App Integration > Zapier and only on the Titanium plan, to connect Billdr's Zapier integration. No Billdr MCP server and no official ChatGPT or Claude connector was found.
| What you need | Billdr API key | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server found | Copy and paste | Hosted MCP server |
| Start today on any Billdr plan | Titanium plan only | Your login | Your login, once |
| Change orders, budgets, timesheets, daily logs | Not among the Zapier actions | One screen at a time | 18 tools, writes after your OK |
| Run from n8n or a script | Zapier only, no endpoint docs | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: Billdr help: Zapier Integration · Billdr pricing · Billdr llms.txt · Billdr PRO help center · Help: Create a project · Help: Create a quote · Help: Send a revised quote · Help: Create and send a change order · Help: Submit invoices and receive payments · Help: Budget, forecast vs actuals · Help: Bid requests · Help: Track employees' labor time · Help: Client dashboard
Once, in a browser we host for you.
One address in its settings.
It drafts the quote, you approve it.
Your agent works in your own logged-in Cloud Browser. Writes, and anything that reaches a client, a sub or your crew, wait for your OK. Who can see your session
Log in to Billdr in a Cloud Browser. Open app.billdr.co in your Cotlet Cloud Browser and log in with your email and the 6-digit code Billdr sends you.
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.
Billdr uses the same address, https://cotlet.dev/mcp/v1, as every other app you switch on, so a single connector serves them all. Switched Billdr on after you connected? Refresh the connector and the 18 Billdr 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: view_project_budget One tool per owner workflow in the Billdr PRO help center. Most take an `action`: `list` and `get` only read, the other actions write and ask first.
Every job starts as a project. The client dashboard, shared files and reports are where your homeowner follows it.
Follows My Projects > Add a New Project. The manual form takes the project name, an address picked from the suggestions and a client; the project lands on your board with status Lead, ready for a quote. `magic_link` only returns your unique Magic Link: prospects who fill in its form become new projects on their own, and Billdr texts you an alert. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_projects
REST endpointPOST https://cotlet.dev/api/v1/billdr/projects/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `magic_link`. `list` and `get` only read. |
| project string | string | Project name or ID, for `get`. |
| status string | string | For `list`: a board status such as Lead or In construction. Leave empty for all. |
| fields object | object | For `create`: Project Name, Project Address, and an existing client or a new one with name, phone and email. |
{
"action": "action"
} {
"status": "In construction",
"projects": [
{
"project": "Garage conversion",
"client": "Example Family",
"contract_value": 86400
},
{
"project": "Kitchen renovation",
"client": "Sample Homeowner",
"contract_value": 45900
},
{
"project": "Basement finish",
"client": "Example Client",
"contract_value": 38200
}
]
} Billdr makes a dashboard for every project, with no client account needed: the client signs quotes and change orders, pays invoices, and sees the contract balance, schedule, files, reports and logs you share. `get` returns the View Client Dashboard link. `add_client` adds a second client on the Summary tab so both get the emails. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_client_dashboard
REST endpointPOST https://cotlet.dev/api/v1/billdr/client-dashboard/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `add_client`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| client object | object | For `add_client`: name and email of the second client. |
{
"action": "action",
"project": "project"
} {
"project": "Kitchen renovation",
"dashboard_url": "https://app.billdr.co/client/example",
"clients": [
"Sample Homeowner"
]
} The project's Reports section. A report stays internal unless you share it; a shared report appears in the client dashboard, where your client can open it any time. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → create_client_reports
REST endpointPOST https://cotlet.dev/api/v1/billdr/client-reports
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| title string | string | For `create`: for example Weekly Progress Report. |
| notes string | string | Summary of the work done. |
| photos array | array | Photo links, for example from daily logs. |
| share boolean | boolean | True to show it in the client dashboard. |
{
"action": "action",
"project": "project"
} {
"project": "Garage conversion",
"report": "Weekly Progress Report",
"photos": 6,
"shared": false
} Your cost catalog, quotes and their revisions, bid requests to subs, and the finishes the client picks.
Templates and Costs > Cost-Catalog > Import. The agent shows you the rows first, because the import adds them all at once. Billdr has no client import: clients come in with their projects. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → import_cost_catalog
REST endpointPOST https://cotlet.dev/api/v1/billdr/cost-catalogs
| Name | Type | Description |
|---|---|---|
| file_url string required | string | Link to a .csv laid out like Billdr's Cost-Catalog Template: Categories, Task, Material, Labor. |
| default_markup number | number | Default markup %, if you want one. |
{
"file_url": "https://example.com"
} {
"file": "price-book-2026.csv",
"categories": 14,
"tasks": 212,
"imported": true
} Works in the project's Quotes tab. Builder catalog tasks include the Home Depot catalog at your local store's prices, refreshed about every two weeks. The side panel applies the mark-up, discount and tax, and the Cost Breakdown sums materials, labor and crew hours. `create` saves the quote unsent; `send` runs Send Quote and reaches your client. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_quotes
REST endpointPOST https://cotlet.dev/api/v1/billdr/quotes/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `send`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| quote string | string | Quote number, for `get` and `send`. |
| start_from string | string | For `create`: a Billdr Pro template, one of your templates, a quote sent before, or `blank`. |
| categories array | array | For `create`: categories with tasks from the Builder catalog or My Catalog, or custom tasks with material and labor cost. |
| markup_percent number | number | Global Mark-up % applied to every line. |
| discount object | object | Discount name and value, fixed or %. |
| tax_rate number | number | Tax rate. Default the one in your settings. |
| details object | object | Payment schedule, construction schedule, quote validity, terms and conditions. |
| hide_line_details boolean | boolean | True to show the client only the grand total. |
| email object | object | For `send`: subject, message and CCs. |
{
"action": "create",
"project": "Example Family bathroom",
"start_from": "blank",
"categories": [
{
"category": "Demolition",
"material": 300,
"labor": 1700
},
{
"category": "Tile and waterproofing",
"material": 3100,
"labor": 2900
},
{
"category": "Plumbing fixtures",
"material": 2200,
"labor": 1800
}
],
"markup_percent": 20
} {
"project": "Example Family bathroom",
"quote": "Q-1027",
"categories": [
{
"category": "Demolition",
"material": 300,
"labor": 1700,
"total": 2000
},
{
"category": "Tile and waterproofing",
"material": 3100,
"labor": 2900,
"total": 6000
},
{
"category": "Plumbing fixtures",
"material": 2200,
"labor": 1800,
"total": 4000
}
],
"subtotal": 12000,
"markup_percent": 20,
"markup": 2400,
"total_before_tax": 14400,
"sent": false
} Editing in place overwrites the version your client received, so the tool duplicates unless you ask for `edit`. Billdr lets a client sign only one quote per project; after a duplicate the agent asks whether to cancel the first one. The revision goes out with manage_quotes `send`. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → revise_quotes
REST endpointPOST https://cotlet.dev/api/v1/billdr/quotes/revise
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| quote string required | string | The quote you sent. |
| mode string | string | `duplicate` (default), `edit` or `save_as_template`. |
| changes object | object | Categories or tasks to remove, change or add, with new quantities, rates or mark-up. |
| template_name string | string | For `save_as_template`: the template name. |
{
"project": "project",
"quote": "quote"
} {
"project": "Example Family bathroom",
"from_quote": "Q-1027",
"new_quote": "Q-1031",
"mode": "duplicate",
"removed": [
"Painting"
],
"sent": false
} Each sub gets an email with View Bid Details and answers without a Billdr account: they upload a price, add notes or decline. `list` shows the requests per estimate with division, due date and status (pending, submitted, declined). `create_po` makes a purchase order from the chosen bid with its documents and contract amount. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → send_bid_requests
REST endpointPOST https://cotlet.dev/api/v1/billdr/bid-requests
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `create_po`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| division string | string | For `create`: a division such as Plumbing, or `all` for the whole scope. |
| due_date string | string | Bid due date, ISO. |
| start_date string | string | Expected work start date, ISO. |
| reminder boolean | boolean | Automatic reminder 48 hours before the due date. |
| subcontractors array | array | Subs to invite, found by trade. |
| files array | array | Documents or a Files & Folders link. |
| bid string | string | For `create_po`: the bid you chose. |
{
"action": "action",
"project": "project"
} {
"project": "Basement finish",
"division": "Plumbing",
"requests": [
{
"subcontractor": "Example Plumbing",
"status": "submitted",
"amount": 7200
},
{
"subcontractor": "Sample Pipe Works",
"status": "pending"
}
]
} Three levels: a section such as Kitchen, groups such as Faucets, and product options in each group. Clients choose in their dashboard and see what is required and by when. Billdr's AI fills a product from its page only when that page is public; behind a login the agent enters the details itself. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_material_selections
REST endpointPOST https://cotlet.dev/api/v1/billdr/material-selections/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| sections array | array | For `create` and `update`: sections with groups, each group with product options, photos or product links, mandatory or optional, and a due date. |
{
"action": "action",
"project": "project"
} {
"project": "Kitchen renovation",
"sections": [
{
"section": "Kitchen",
"groups": [
{
"group": "Faucets",
"options": 3,
"mandatory": true,
"due": "2026-11-28",
"chosen": null
}
]
}
]
} Everything here changes what the client owes. A change order needs a signed quote, and sending is always its own call.
Needs a signed quote: change orders sit in the project's Contract tab because they amend it. Extra lines add to the contract total, Credit lines subtract. With auto invoicing, Billdr issues an invoice for the net change as soon as the client signs. The client accepts and e-signs from the email; the status moves from Submitted to Signed and the contract value updates. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_change_orders
REST endpointPOST https://cotlet.dev/api/v1/billdr/change-orders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `send`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| change_order string | string | Change order, for `get` and `send`. |
| cause string | string | For `create`: the Cause, such as Client request or Scope expansion. |
| lines array | array | For `create`: description, amount and `extra` or `credit` for each line. |
| tax boolean | boolean | False when the amounts already include tax. |
| auto_invoice boolean | boolean | Auto-send invoice upon acceptance. |
| email object | object | For `send`: subject, message and CCs. |
{
"action": "action",
"project": "project"
} {
"project": "Garage conversion",
"change_order": "CO-3",
"cause": "Client request",
"lines": [
{
"description": "Install wider baseboard trim",
"type": "extra",
"amount": 1450
}
],
"net_change": 1450,
"status": "Draft"
} The project's Invoices tab: New > Invoice, by hand or from expenses, payment schedule milestones, signed contract lines or a change order. `send` runs Preview & Send and emails your client a link to their dashboard; sending again works as a reminder. Online card and bank payments need your Stripe account. `record_payment` is Receive Payment; Billdr emails a receipt only for payments made online. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_invoices
REST endpointPOST https://cotlet.dev/api/v1/billdr/invoices/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `send`, `record_payment`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| invoice string | string | Invoice number, for `get`, `send` and `record_payment`. |
| add_from string | string | For `create`: `manual`, `expenses`, `payment_schedule`, `contract_lines` or `change_order`. |
| lines array | array | Line items with description, quantity and unit price, or the items to take over. |
| due_date string | string | ISO date. |
| note string | string | Note to the client. |
| hide array | array | For `send`: `quantities` or `unit_prices` to hide. |
| amount number | number | For `record_payment`: the full or partial amount received. |
{
"action": "action",
"project": "project"
} {
"project": "Kitchen renovation",
"invoices": [
{
"invoice": "INV-214",
"due": "2026-11-02",
"total": 9800,
"status": "Opened"
},
{
"invoice": "INV-219",
"due": "2026-11-20",
"total": 6400,
"status": "Submitted"
}
]
} Receipts, purchase orders and the budget table that sets them against the signed contract.
Expenses section of a project. With a receipt attached, Billdr's AI reads it and fills in the fields. Expenses stay internal, never shown to clients. `list` also returns total contract value, total expenses and remaining profit. An expense with a cost code joins the budget table once approved. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_expenses
REST endpointPOST https://cotlet.dev/api/v1/billdr/expenses/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| expense object | object | For `add`: name, amount, category (labor, material, subcontractor and so on), cost code and receipt. |
{
"action": "action",
"project": "project"
} {
"project": "Garage conversion",
"contract_value": 86400,
"expenses": 51250,
"profit": 35150
} Purchase Orders in the main menu. A PO is Draft, Sent, Approved or Completed, and only drafts can be edited. Once submitted it is shared with your admins, or the vendor depending on permissions, and admins are notified. Approving or rejecting is an admin step, logged in the PO history. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_purchase_orders
REST endpointPOST https://cotlet.dev/api/v1/billdr/purchase-orders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `approve`, `reject`. `list` and `get` only read. |
| project string | string | Project, for `create` and to filter `list`. |
| purchase_order string | string | The PO, for `get`, `update`, `approve` and `reject`. |
| vendor string | string | For `create`: an existing vendor or a new one. |
| lines array | array | Description, quantity and unit price per line. |
| files array | array | Links to invoices, receipts or other documents to attach. |
{
"action": "action"
} {
"purchase_order": "PO-0458",
"project": "Basement finish",
"vendor": "Example Lumber Co",
"lines": [
{
"description": "2x4 studs, 8 ft",
"quantity": 120,
"unit_price": 4.5
}
],
"total": 540,
"status": "Draft"
} The budget table fills once a quote with cost codes is signed: forecast costs, expected profit and invoice amounts from the contract, against actuals from purchase orders, expenses and invoices. Uncategorized expenses stay out until they get a cost code. It changes nothing and runs without asking.
MCP callbilldr_read → view_project_budget
REST endpointGET https://cotlet.dev/api/v1/billdr/project-budgets/view
| Name | Type | Description |
|---|---|---|
| project string required | string | Project name or ID, as manage_projects returns it. |
| division string | string | One division, such as Electrical. Leave empty for all. |
{
"project": "project"
} {
"project": "Garage conversion",
"divisions": [
{
"division": "Electrical",
"budget": 9200,
"actual": 9200,
"remaining": 0
},
{
"division": "Painting",
"budget": 4100,
"actual": 3780,
"remaining": 320
}
]
} Gantt items, tasks texted to employees, daily logs from site and approved shifts.
The project's Schedule section, in list or Gantt view. Items such as Framing or Plumbing can sit in groups and link Finish to start, Start to start or Finish to finish. You can assign them to yourself or your employees, not to a sub outside your organisation. Clients see the schedule in their dashboard; `share` returns the public link. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_schedule
REST endpointPOST https://cotlet.dev/api/v1/billdr/schedule/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `update`, `share`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| items array | array | For `add` and `update`: title, start and end date, notes, group, link type and assignee. |
{
"action": "action",
"project": "project"
} {
"project": "Basement finish",
"items": [
{
"title": "Framing",
"start": "2026-11-23",
"end": "2026-11-27"
},
{
"title": "Plumbing rough-in",
"start": "2026-11-30",
"end": "2026-12-02",
"link": "finish_to_start"
}
]
} Tasks belong to one project. Billdr recommends a due date on every task. Assigning uses Send Notifications by SMS, so the employee gets a text with a link to the task in the Employee Portal. `list` shows the field updates: In Progress, Completed with its date, and notes from the crew. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → assign_tasks
REST endpointPOST https://cotlet.dev/api/v1/billdr/tasks/assign
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `assign`. `list` and `get` only read. |
| project string required | string | Project name or ID, as manage_projects returns it. |
| tasks array | array | For `create`: name, due date and optional start date. |
| from_schedule boolean | boolean | For `create`: generate the tasks from the schedule. |
| task string | string | For `assign`: the task. |
| employee string | string | For `assign`: the employee. |
{
"action": "action",
"project": "project"
} {
"project": "Kitchen renovation",
"tasks": [
{
"task": "Demo the floor",
"assignee": "Crew member A",
"due": "2026-11-18",
"status": "In Progress"
},
{
"task": "Hang upper cabinets",
"assignee": "Crew member B",
"due": "2026-11-21",
"status": "Not started"
}
]
} The questions come from your daily log settings. Logs stay internal until you toggle one on for the client; then it shows in their dashboard. `list` filters by project, date or who submitted it, including logs your crew sends from the mobile app. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_daily_logs
REST endpointPOST https://cotlet.dev/api/v1/billdr/daily-logs/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `share`. `list` and `get` only read. |
| project string | string | Project, for `create` and to filter `list`. |
| date string | string | ISO date of the log, or the day to filter. |
| answers object | object | For `create`: answers to your daily log questions. |
| notes string | string | Work done, weather, crew on site, issues. |
| photos array | array | Links to photos or documents. |
| log string | string | For `share`: the log to show the client. |
{
"action": "action"
} {
"project": "Garage conversion",
"logs": [
{
"date": "2026-11-13",
"submitted_by": "Crew member A",
"notes": "Drywall hung on north wall, inspection booked",
"photos": 4,
"shared": false
}
]
} Admin Timesheets. `list` shows who is clocked in, on which project, and the location status: on site, not on site, or not collected (usual for shifts an admin created). `labor_cost` reads total hours and labor cost for a project and period. `convert_to_expense` books the time at internal cost, without your margin. By default you confirm each call; you can switch that off for this tool.
MCP callbilldr_write → manage_timesheets
REST endpointPOST https://cotlet.dev/api/v1/billdr/timesheets/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `labor_cost`, `create_shift`, `edit_shift`, `approve`, `reject`, `convert_to_expense`. `list` and `get` only read. |
| project string | string | Project, for `labor_cost`, `create_shift` and `convert_to_expense`. |
| employee string | string | Employee to filter on or create a shift for. |
| period string | string | `current_week`, `last_two_weeks`, or a from and to date. |
| shift string | string | For `edit_shift`, `approve` and `reject`. Leave empty with `approve` to run Approve All. |
| times object | object | Start and end time for `create_shift` and `edit_shift`. |
{
"action": "action"
} {
"project": "Garage conversion",
"period": "current_week",
"hours": 112,
"labor_cost": 4480,
"pending_approval": 6
} Your logged-in Billdr browser profile, AES-256-GCM encrypted, in Finland. Never a password or a login code.
The 18 Billdr tools. The session cookie stays in the Cloud Browser.
The projects and money records your Billdr user can open. In Billdr every administrator has the account owner's access.
Billdr Settings, My Team and its roles, the QuickBooks Online link, your Stripe account and the Zapier API key.
You log in again yourself, in the same Cloud Browser, with a fresh 6-digit code.
Disable Billdr for agents, reset the browser, or log out of Billdr in it.
Cotlet never sees or stores your password: Billdr logs you in with your email and a code you type yourself, and the agent only uses the session that login leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
send action is a separate call. | Action | How to put it right |
|---|---|
| Project details, schedule items, tasks | Call the same tool again with the earlier values |
| Quote edited in place | Billdr keeps no copy of the sent version; revise_quotes duplicates by default for that reason |
| Quote, change order or invoice sent | Already with your client: talk to them before you change it |
| Bid request sent | Already with your subs: follow up with them directly |
All 17 write tools ask first: by default you confirm each call, and you can switch that off per tool. The one read tool, the budget table, runs at once.
{
"name": "manage_quotes",
"arguments": {
"action": "create",
"project": "Example Family bathroom",
"start_from": "blank",
"categories": [
{
"category": "Demolition",
"material": 300,
"labor": 1700
},
{
"category": "Tile and waterproofing",
"material": 3100,
"labor": 2900
},
{
"category": "Plumbing fixtures",
"material": 2200,
"labor": 1800
}
],
"markup_percent": 20
}
} curl -X POST https://cotlet.dev/api/v1/billdr/quotes/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","project":"Example Family bathroom","start_from":"blank","categories":[{"category":"Demolition","material":300,"labor":1700},{"category":"Tile and waterproofing","material":3100,"labor":2900},{"category":"Plumbing fixtures","material":2200,"labor":1800}],"markup_percent":20}' {
"project": "Example Family bathroom",
"quote": "Q-1027",
"categories": [
{
"category": "Demolition",
"material": 300,
"labor": 1700,
"total": 2000
},
{
"category": "Tile and waterproofing",
"material": 3100,
"labor": 2900,
"total": 6000
},
{
"category": "Plumbing fixtures",
"material": 2200,
"labor": 1800,
"total": 4000
}
],
"subtotal": 12000,
"markup_percent": 20,
"markup": 2400,
"total_before_tax": 14400,
"sent": false
} The example quotes demolition at $2,000, tile and waterproofing at $6,000 and plumbing fixtures at $4,000: $12,000, plus the 20% mark-up of $2,400, $14,400 before tax. The homeowner sees nothing until the send action runs. A cron job or n8n flow makes the same call over REST at /api/v1/billdr with the same key and price. Failed calls are free.
About $29 a monthfor a contractor with about five jobs running, 5,000 credits. Your Billdr plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Phone leads turned into projects and quotes | 2 × 12 | 240 |
| Revised quotes and change orders | 2 × 8 | 160 |
| Invoices built, sent and paid | 3 × 15 | 450 |
| Monday check of overdue invoices | 2 × 4 | 80 |
| Receipts entered as expenses | 1 × 90 | 900 |
| Timesheets approved, labor cost read | 3 × 4 | 120 |
| Daily logs and client reports | 1 × 60 | 600 |
| Bid requests and purchase orders | 2 × 10 | 200 |
| Project and budget lookups | 1 × 75 | 750 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 350 calls | 5,000 |
The smallest pack, 5,000 credits for $29, covers this month. A busy building season with more jobs uses more calls.
Credit packs are one-time purchases, not a subscription. The month above comes 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 |
|---|---|---|
| Billdr Zapier integration | Billdr's own integration: creates clients, invoices, projects and quotes, updates clients, searches projects and clients. | API key on the Titanium plan only; no change orders, budgets, timesheets or daily logs among the actions. |
| Bob and Bruno | Billdr's own AI copilot and estimator, inside Billdr. | They work in the Billdr app, not from ChatGPT, Claude or a script. |
| QuickBooks Online integration | Billdr's own link to your books. | Accounting sync, not a route for an AI agent. |
| By hand | Open each project in Billdr and click through. | One screen at a time, only while you are at the desk. |
If Billdr's own Zapier integration already covers your job and you are on Titanium, use it: it is the vendor's route. Cotlet fits when you want ChatGPT, Claude or a script handling quotes, change orders and crew paperwork in Billdr today, on your current plan, with nothing to host.
Take Group sp. z o.o. builds Cotlet. It is registered in Poland, EU (VAT PL6342984273), has been in business since 2019, and is led by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Billdr tools to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=billdr, turn on Billdr under Integrations in the console and log in at https://app.billdr.co/authenticate/login in your Cloud Browser. Then connect your AI agent and ask it about a project. The trial needs no card.
Billdr publishes no public API documentation. Its help center documents an API key under Settings > App Integration > Zapier, available only on the Titanium plan, for its Zapier integration, whose actions create clients, invoices, projects and quotes (checked 16 Nov 2026). No Billdr MCP server and no official ChatGPT or Claude connector was found. Cotlet does not use that key: it works in your own logged-in Billdr account.
Billdr's pricing page puts quotes, invoices, change orders, expenses and the client dashboard in Starter, and scheduling, daily logs, timesheets, to-dos, purchase orders, bid requests, material selections, construction reports and the budget table in Premium and up. The tools follow your plan: they cannot open what your plan does not include.
No. Billdr needs a signed quote before a change order can be created, because change orders amend the contract. Until then, revise the quote with revise_quotes.
No. Your client pays from their dashboard; online card and bank payments run through your own Stripe account. record_payment only records a payment you received, for example a cheque, and Billdr sends no receipt for those on its own.
An administrator whose work the agent should do, usually the owner. Employees in Billdr use the crew portal, so an employee login gives the agent only that view.
Only in how it is called. Both carry the same 18 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 Billdr.
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