Live

Yardbook API and MCP server

Yardbook has no public API and no developer docs (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Yardbook with 14 endpoints (6 read, 8 write): your AI agent signs in as you and does the work.

Category: Local services & SaaS
Endpoints: 14 6 read, 8 write
Updated: 1d ago October 11, 2026

Request access View as Markdown

Your agent

Claude Code, Codex, Cursor or a script
calls a tool
Cotlet

MCP server and REST API · 14 endpoints

cotlet.dev/mcp/v1
acts as you
Yardbook

Signed in as you on yardbook.com

You sign in once. We never store your password.

Official API

Does Yardbook have an official API?

Yardbook has no public API and no developer docs (checked 11 Oct 2026). Its only connector is Zapier, with 10 triggers and 2 actions: Create Lead and Create AI Event. You cannot schedule jobs, write estimates or invoices, or read invoices from code.

What Yardbook's own tools do compared with Cotlet
Task	Yardbook official	Cotlet
List customers and prospects	Partly Zapier fires when a customer or prospect is created, no search or history	Yes
Add a lead or prospect	Yes Zapier action Create Lead	Yes
Schedule a job	No	Yes
See today's and tomorrow's jobs	Partly Zapier fires when a job is added to today or tomorrow, it cannot list the schedule	Yes
Mark a job completed	No Zapier only fires after a job is completed in Yardbook	Yes
Create and send estimates	No Zapier only fires when an estimate is approved	Yes
Create and send invoices	No	Yes
List unpaid invoices and record payments	No	Yes

Sources: Yardbook on Zapier: triggers and actions · Yardbook: estimates, scheduling, invoices and payments · Yardbook help: Auto payment reminder (Premium Package) · Yardbook help: Automatically generate invoices from jobs · Yardbook help: Smart cloning of estimates and invoices

Common use cases

What can an AI agent do in Yardbook?

Cotlet is best for landscaping owners and office managers who want their AI agent to schedule jobs, send estimates and invoices and chase payments without running or fixing a server.

Chase unpaid invoices Runs: Weekly

Which invoices are unpaid and older than 30 days? Send each customer a reminder. Your agent calls list_invoices and send_invoice.
Add a new customer and schedule recurring lawn jobs Runs: Weekly

New customer: Maria Lopez, 18 Elm Street, 555-0142, side gate code 1234, dog in the yard. Weekly mowing and edging on Tuesdays from next week. Put her with the crew that already works Elm Street. Your agent calls list_customers, create_customer, list_jobs and schedule_job.
Turn site-visit notes into an estimate

Parker property, 7 Ridge Road: spring cleanup of all beds $220, 6 yards hardwood mulch installed at $45 a yard, trim 4 boxwoods $15 each. Draft the estimate and email it to them after I look at it. Your agent calls list_customers, get_customer, create_customer, create_estimate and send_estimate.
Invoice completed jobs Runs: Daily

Mark today's finished jobs as completed and invoice each customer. Your agent calls list_jobs, complete_job, create_invoice and send_invoice.
Record check and cash payments Runs: Weekly

Here are this week's checks from the deposit slip: Johnson $240 #3318, Parker Property $550 #1207, Lee $85 cash, Ortiz $300 #882. Record each against the right invoice, then tell me who still owes from more than 30 days ago. Your agent calls list_invoices, get_invoice and record_payment.
See tomorrow's crew schedule Runs: Daily

What's on the schedule tomorrow, and which crew member has each job? Your agent calls list_jobs.

Endpoints

What is the Yardbook API?

Cotlet's Yardbook API exposes 14 endpoints for your own Yardbook account: list customers, get customer, list jobs, list estimates, list invoices, get invoice, create customer, schedule job, complete job, create estimate, send estimate, create invoice, send invoice and record payment. The list_customers endpoint returns customers and prospects with address, email, phone and balance. Each endpoint takes simple JSON inputs like customer_id, limit or status and works both as an MCP tool for agents and as a REST call for scripts.

All endpoints · 14 total

missing one? request an endpoint

POST

list_customers

Customers and prospects with address, email, phone and balance.

read

Lists customers, prospects or both. Search matches name, address, email and phone. Balance is the amount the customer still owes on open invoices. Pass next_cursor back as cursor for the next page.

POST /api/v1/yardbook/list_customers

Input

Input: list_customers
Parameter	Type	Description
type	enum	customer, prospect or all. Default: customer.
search	string	Match on name, address, email or phone.
limit	integer	1 to 200. Default: 50.
cursor	string	Next page cursor from the previous call.

Example response

{
  "customers": [
    {
      "customer_id": "284117",
      "name": "Maria Lopez",
      "type": "customer",
      "address": "18 Elm Street",
      "email": "maria@example.com",
      "phone": "555-0142",
      "balance": "0.00"
    },
    {
      "customer_id": "284230",
      "name": "Parker Property",
      "type": "customer",
      "address": "7 Ridge Road",
      "email": "office@parker.example.com",
      "phone": "555-0177",
      "balance": "240.00"
    }
  ],
  "next_cursor": null
}

POST
get_customer

One customer with contact details, notes, upcoming jobs, open estimates and invoices.
read
Returns one customer with contact details and property notes, plus their upcoming jobs, open estimates and unpaid invoices. Use it before scheduling or billing so your agent sees what is already there.

POST /api/v1/yardbook/get_customer

Input

Input: get_customer

Parameter Type Description

customer_id required string Customer ID from list_customers.

Example response
```
{
  "customer_id": "284117",
  "name": "Maria Lopez",
  "type": "customer",
  "address": "18 Elm Street",
  "notes": "Side gate code 1234. Dog in yard.",
  "upcoming_jobs": [
    {
      "job_id": "9930412",
      "date": "2026-10-13",
      "services": [
        "Mowing",
        "Edging"
      ]
    }
  ],
  "open_estimates": [],
  "unpaid_invoices": []
}
```

POST

list_jobs

Scheduled and completed jobs in a date range, with customer, services and assigned crew member.

read

Lists jobs between two dates, oldest first, with customer, services and the crew member each job is assigned to. Filter by status, crew member or customer. Recurring jobs appear as one entry per visit in the range.

POST /api/v1/yardbook/list_jobs

Input

Input: list_jobs
Parameter	Type	Description
from required	date	First day of the range.
to required	date	Last day of the range.
status	enum	scheduled, completed or all. Default: all.
assignee_id	string	Only jobs assigned to this crew member.
customer_id	string	Only jobs for this customer.

Example response

{
  "jobs": [
    {
      "job_id": "9930412",
      "date": "2026-10-13",
      "customer_id": "284117",
      "customer": "Maria Lopez",
      "services": [
        "Mowing",
        "Edging"
      ],
      "status": "scheduled",
      "assignee": "Crew 1"
    },
    {
      "job_id": "9930455",
      "date": "2026-10-13",
      "customer_id": "284230",
      "customer": "Parker Property",
      "services": [
        "Spring cleanup"
      ],
      "status": "scheduled",
      "assignee": "Crew 2"
    }
  ]
}

POST

list_estimates

Estimates with customer, total and status, newest first.

read

Lists estimates newest first with customer, total and status. Draft estimates have not been sent. Approved estimates can be turned into an invoice with create_invoice.

POST /api/v1/yardbook/list_estimates

Input

Input: list_estimates
Parameter	Type	Description
status	enum	draft, sent, approved or all. Default: all.
customer_id	string	Only estimates for this customer.
limit	integer	1 to 100. Default: 50.

Example response

{
  "estimates": [
    {
      "estimate_id": "51802",
      "customer_id": "284230",
      "customer": "Parker Property",
      "total": "490.00",
      "status": "draft",
      "created_at": "2026-10-09"
    }
  ]
}

POST

list_invoices

Invoices with customer, total, amount due, due date and status.

read

Lists invoices newest first. Status defaults to unpaid. Amount due is the total minus the payments recorded. older_than_days keeps invoices issued at least that many days ago, which is how you find overdue ones.

POST /api/v1/yardbook/list_invoices

Input

Input: list_invoices
Parameter	Type	Description
status	enum	unpaid, paid or all. Default: unpaid.
customer_id	string	Only invoices for this customer.
older_than_days	integer	Only invoices issued at least this many days ago.
limit	integer	1 to 100. Default: 50.

Example response

{
  "invoices": [
    {
      "invoice_id": "73194",
      "customer_id": "284230",
      "customer": "Parker Property",
      "issued_at": "2026-09-02",
      "due_date": "2026-09-16",
      "total": "240.00",
      "amount_due": "240.00",
      "status": "unpaid"
    }
  ]
}

POST
get_invoice

Full invoice: line items, payments recorded and amount due.
read
Returns one invoice with every line item, the payments recorded against it and the amount due. Use it to check an invoice before sending it or recording a payment.

POST /api/v1/yardbook/get_invoice

Input

Input: get_invoice

Parameter Type Description

invoice_id required string Invoice ID from list_invoices.

Example response
```
{
  "invoice_id": "73194",
  "customer": "Parker Property",
  "status": "unpaid",
  "line_items": [
    {
      "service": "Mowing",
      "description": "Weekly mowing, September",
      "quantity": 4,
      "unit_price": "60.00"
    }
  ],
  "total": "240.00",
  "payments": [],
  "amount_due": "240.00"
}
```

POST

create_customer

Add a customer or prospect with contact details and service address.

write

Adds a customer, or a prospect if type is prospect, with the service address and contact details. It reaches no one and changes only your customer list, so it runs without asking for your OK.

POST /api/v1/yardbook/create_customer

Input

Input: create_customer
Parameter	Type	Description
name required	string	Customer or company name.
address required	string	Service address.
email	string	Email for estimates and invoices.
phone	string	Phone number.
type	enum	customer or prospect. Default: customer.
notes	string	Gate codes, pets, property notes.

Example response

{
  "customer_id": "284117",
  "name": "Maria Lopez",
  "type": "customer",
  "address": "18 Elm Street"
}

POST

schedule_job

Add a one-time or recurring job to the schedule, optionally assigned to a crew member.

write

Adds a job for a customer on the date of the first visit. With repeat set to weekly or biweekly it creates a recurring job. Services are names from your product and service catalog. It sends nothing to the customer, so it runs without asking for your OK.

POST /api/v1/yardbook/schedule_job

Input

Input: schedule_job
Parameter	Type	Description
customer_id required	string	Customer ID from list_customers.
date required	date	Date of the first visit.
services required	string[]	Services from your product catalog, e.g. Mowing.
repeat	enum	none, weekly or biweekly. Default: none.
assignee_id	string	Crew member to assign.
notes	string	Instructions for the crew.

Example response

{
  "job_id": "9930412",
  "customer_id": "284117",
  "date": "2026-10-13",
  "repeat": "weekly",
  "status": "scheduled",
  "services": [
    "Mowing",
    "Edging"
  ],
  "assignee": "Crew 1"
}

POST
complete_job

Mark a job as completed, so it can be invoiced.
write
Marks one job completed, with optional notes on what was done. A completed job can be passed to create_invoice. It sends nothing to the customer, so it runs without asking for your OK.

POST /api/v1/yardbook/complete_job

Input

Input: complete_job

Parameter Type Description

job_id required string Job ID from list_jobs.
notes string What was done on site.

Example response
```
{
  "job_id": "9930412",
  "status": "completed",
  "notes": "Mowed and edged, bagged clippings."
}
```

Input: complete_job
Parameter	Type	Description
job_id required	string	Job ID from list_jobs.
notes	string	What was done on site.

POST

create_estimate

Draft estimate for a customer or prospect. Nothing is sent until you call send_estimate.

write

Saves a draft estimate with your line items. The total is the sum of quantity times unit_price over all lines. Nothing is sent to the customer until send_estimate, so the draft runs without asking for your OK.

POST /api/v1/yardbook/create_estimate

Input

Input: create_estimate
Parameter	Type	Description
customer_id required	string	Customer ID from list_customers.
line_items required	object[]	List of { service, description, quantity, unit_price }.
description	string	Scope of work shown on the estimate.

Example response

{
  "estimate_id": "51802",
  "customer_id": "284117",
  "status": "draft",
  "line_items": [
    {
      "service": "Spring cleanup",
      "quantity": 1,
      "unit_price": "220.00",
      "amount": "220.00"
    },
    {
      "service": "Mulch",
      "quantity": 6,
      "unit_price": "45.00",
      "amount": "270.00"
    }
  ],
  "total": "490.00"
}

POST
send_estimate

Email an estimate to the customer with a link to approve it online.
asks first write
Emails a draft estimate to the customer, with your optional note and a link to approve it online. The customer needs an email address on file. By default you confirm each call; you can switch that off for this tool.

POST /api/v1/yardbook/send_estimate

Input

Input: send_estimate

Parameter Type Description

estimate_id required string Estimate ID from list_estimates.
message string Note added to the email.

Example response
```
{
  "estimate_id": "51802",
  "status": "sent",
  "sent_to": "maria@example.com"
}
```

Input: send_estimate
Parameter	Type	Description
estimate_id required	string	Estimate ID from list_estimates.
message	string	Note added to the email.

POST

create_invoice

Invoice from a completed job or an approved estimate, or with your own line items. Not sent yet.

write

Creates an invoice from a completed job, from an approved estimate, or from line items you pass. It is saved unsent; send_invoice emails it. It reaches no one, so it runs without asking for your OK.

POST /api/v1/yardbook/create_invoice

Input

Input: create_invoice
Parameter	Type	Description
customer_id required	string	Customer ID from list_customers.
job_id	string	Completed job to invoice.
estimate_id	string	Approved estimate to convert.
line_items	object[]	List of { service, description, quantity, unit_price }, when there is no job or estimate.
due_date	date	Payment due date.

Example response

{
  "invoice_id": "73210",
  "customer_id": "284117",
  "job_id": "9930412",
  "status": "unpaid",
  "sent": false,
  "total": "85.00",
  "amount_due": "85.00",
  "due_date": "2026-10-27"
}

POST
send_invoice

Email an invoice to the customer with a link to view it.
asks first write
Emails an invoice to the customer, with your optional note, for example a reminder on an overdue one. The customer needs an email address on file. By default you confirm each call; you can switch that off for this tool.

POST /api/v1/yardbook/send_invoice

Input

Input: send_invoice

Parameter Type Description

invoice_id required string Invoice ID from list_invoices.
message string Note added to the email, e.g. a reminder.

Example response
```
{
  "invoice_id": "73194",
  "status": "unpaid",
  "sent_to": "office@parker.example.com"
}
```

POST

record_payment

Record a cash, check or other payment received against an invoice.

asks first write

Records a payment you received against one invoice. The amount due goes down by the amount; an invoice paid in full becomes paid. It moves no money and charges no card. By default you confirm each call; you can switch that off for this tool.

POST /api/v1/yardbook/record_payment

Input

Input: record_payment
Parameter	Type	Description
invoice_id required	string	Invoice ID from list_invoices.
amount required	string	Amount received, e.g. 240.00.
method required	string	How it was paid, e.g. Check or Cash.
date	date	Date received. Default: today.
reference	string	Check number or note.

Example response

{
  "invoice_id": "73194",
  "payment": {
    "amount": "240.00",
    "method": "Check",
    "date": "2026-10-11",
    "reference": "Check 3318"
  },
  "amount_due": "0.00",
  "status": "paid"
}

Setup

How do I connect Yardbook to Claude Code, Codex or Cursor?

Connecting Yardbook takes three steps: request access, sign in to Yardbook once, then add one MCP server or call the REST API with the same key.

MCP REST API

1
Create an account

Sign up and add Yardbook in the console. Your API key is there too.
2
Sign in to Yardbook once

Open the connect page from the console and sign in to Yardbook the way you always do. We keep the session, never your password, and you can revoke it anytime.
3
Add Cotlet to your agent
Claude Code Cursor Codex
Claude Code
```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```
Cursor
```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```
Codex
```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```
Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
4
Ask your agent
Prompt
```
Which invoices are unpaid and older than 30 days? Send each customer a reminder.
```
Ask in plain words. Your agent finds the Yardbook tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

1
Export your API key
Shell
```
export COTLET_API_KEY="cotlet_..."
```
Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

Call a tool

curl

curl https://cotlet.dev/api/v1/yardbook/schedule_job \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"customer_id":"284117","date":"2026-10-13","services":["Mowing","Edging"],"repeat":"weekly","assignee_id":"5521","notes":"Side gate code 1234. Bag clippings."}'

Every tool is a POST endpoint at /api/v1/yardbook/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

Read the result

Example response · schedule_job

{
  "job_id": "9930412",
  "customer_id": "284117",
  "date": "2026-10-13",
  "repeat": "weekly",
  "status": "scheduled",
  "services": [
    "Mowing",
    "Edging"
  ],
  "assignee": "Crew 1"
}

You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for Yardbook? Hosted, safe and kept working.

Built for agents
- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.
Your login stays yours
- You sign in to Yardbook yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.
You stay in control
- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.
Kept working for you
- We test every integration daily.
- When Yardbook changes, the tool pauses until we fix it.
- Failed calls cost nothing.

Alternatives

Is there a Yardbook MCP server on GitHub?

Zapier is the only connector Yardbook offers. It reacts to new customers, leads, jobs and approved estimates, but it can only create leads and AI events. We found no open-source Yardbook server, so the realistic choices are Zapier or doing the work by hand in the app.

Cotlet compared with a Zapier
	Zapier	Cotlet
Setup	Connect Yardbook in Zapier and build a Zap per task	Request access, sign in to Yardbook once, add one MCP server or API key
Write actions	Create lead, create AI event	Customers, jobs, estimates, invoices and payments
Reading data	Only new events as they happen, no search	Search customers, jobs, estimates and invoices any time
When Yardbook changes	Zapier maintains its connector; new actions depend on Yardbook	Our team tests it daily and fixes it for you; failed calls are free
Your Yardbook session	Zapier holds the connection	Encrypted in an EU vault, limited to the actions you allow, revoked in one click
When the session expires	Reconnect in Zapier	Your agent gets a link to sign in again
Price	Free Zapier plan for simple Zaps, paid for more tasks	Free 7-day trial with 5,000 credits, then credits per call

Which one fits you

Pick Cotlet if

you are not a developer, or you do not want to maintain a server
you need it to keep working when Yardbook changes, without checking it yourself
your agent or a script should run it on a schedule, also while your computer is off

Pick an open-source server if

you are comfortable installing, updating and fixing it yourself
you want the session to stay on your own computer
you only need it now and then, from one MCP client

For AI agents

Cotlet for Yardbook in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

list_customers passing
get_customer passing
list_jobs passing
list_estimates passing
list_invoices passing

+ 9 more endpoints

14/14 passing latest check self-healing

yardbook.txt

Yardbook has no public API and no developer docs (checked 11 Oct 2026). Its only connector is Zapier, with 10 triggers and 2 actions: Create Lead and Create AI Event. You cannot schedule jobs, write estimates or invoices, or read invoices from code.
Cotlet provides a hosted MCP server and REST API for Yardbook: 14 tools (6 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=yardbook; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/yardbook
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_customers, get_customer, list_jobs, list_estimates, list_invoices, get_invoice, create_customer, schedule_job, complete_job, create_estimate, send_estimate, create_invoice, send_invoice, record_payment
Confirm      send_estimate, send_invoice, record_payment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/yardbook-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=yardbook (Yardbook is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Yardbook once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Yardbook server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Yardbook in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Yardbook's terms; Cotlet is not affiliated with Yardbook.

Full page as Markdown

Automations

Can Yardbook automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Yardbook connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to chase unpaid invoices, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

Where to run Yardbook automations through Cotlet, and how to schedule them
Where	How to connect	How to schedule
Your AI agent	Add https://cotlet.dev/mcp/v1 with your API key.	A scheduled agent run, for example a Claude Code routine.
n8n	MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/yardbook/{tool}.	Schedule Trigger node.
Make	HTTP module: POST https://cotlet.dev/api/v1/yardbook/{tool} with an Authorization: Bearer header and a JSON body.	Scenario schedule.
Zapier	Webhooks by Zapier: POST https://cotlet.dev/api/v1/yardbook/{tool} with the same header and body.	Schedule by Zapier trigger.
Your own script	POST https://cotlet.dev/api/v1/yardbook/{tool} with your API key.	cron or GitHub Actions.

Pricing & limits

How much does the Yardbook API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Yardbook API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

See full pricing

Cotlet plan sizes: price, monthly credits and price per credit
Size	Price	Credits / month	Per credit
Solo	$29/mo	3,000	about $0.0097
Pro	$99/mo	12,000	about $0.0083
Agency	$299/mo	40,000	$0.0075

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.

About Cotlet

How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Yardbook account.

Company details: The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session: You sign in to Yardbook yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Yardbook tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access: Disconnect Yardbook in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do: Store passwords, solve CAPTCHAs or bypass MFA.
Yardbook's terms: You use your own Yardbook account and stay responsible for following Yardbook's terms. Cotlet is independent and not affiliated with Yardbook. Terms
Contact: Questions about the company, security or an app: contact@cotlet.dev

About Cotlet

Frequently asked questions

How do I get access?

Request access and pick Yardbook. Cotlet reviews each request and emails you your API key.

Do I need to be technical?

No. You sign in to Yardbook once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

Is a hosted server safe? My Yardbook session would leave my computer.

Cotlet keeps your Yardbook session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

Does Yardbook have a Zapier action for invoices or jobs?

No. The Zapier app has 10 triggers and two actions, Create Lead and Create AI Event (checked 11 Oct 2026). Scheduling jobs, estimates, invoices and payments are not available there, which is what Cotlet adds.

Do I need a paid Yardbook plan?

Cotlet works in your own Yardbook account and does not use Zapier. We could not open Yardbook's pricing page, so check on yardbook.com which features your plan includes; a tool fails if your account cannot do that action in the app.

Can my agent post or send messages in Yardbook without asking me?

No. Every call to send_estimate, send_invoice or record_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_customer, schedule_job, complete_job, create_estimate, create_invoice runs without asking, because it sends nothing to anyone and one call undoes it.

Can I use the Yardbook API in n8n?

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/yardbook/{tool} from the HTTP Request node.

Give your agent access to Yardbook.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.

Request access

Does Yardbook have an official API?

What can an AI agent do in Yardbook?

Chase unpaid invoices Runs: Weekly

Add a new customer and schedule recurring lawn jobs Runs: Weekly

Turn site-visit notes into an estimate

Invoice completed jobs Runs: Daily

Record check and cash payments Runs: Weekly

See tomorrow's crew schedule Runs: Daily

What is the Yardbook API?

list_customers

get_customer

list_jobs

list_estimates

list_invoices

get_invoice

create_customer

schedule_job

complete_job

create_estimate

send_estimate

create_invoice

send_invoice

record_payment

How do I connect Yardbook to Claude Code, Codex or Cursor?

Connect Yardbook over MCP

Create an account

Sign in to Yardbook once

Add Cotlet to your agent

Ask your agent

Call Yardbook over REST

Export your API key

Call a tool

Read the result

Why use Cotlet for Yardbook? Hosted, safe and kept working.

Built for agents

Your login stays yours

You stay in control

Kept working for you

Is there a Yardbook MCP server on GitHub?

Which one fits you

Cotlet for Yardbook in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Can Yardbook automations run on a schedule in n8n, Make or Zapier?

How much does the Yardbook API cost?

How Cotlet holds your access

Frequently asked questions

How do I get access?

Do I need to be technical?

Is a hosted server safe? My Yardbook session would leave my computer.

Does Yardbook have a Zapier action for invoices or jobs?

Do I need a paid Yardbook plan?

Can my agent post or send messages in Yardbook without asking me?

Can I use the Yardbook API in n8n?

Related integrations

Faire

Booksy

Vagaro

Give your agent access to Yardbook.

Analytics cookies