AutoLeap API and MCP server Let your AI agent chase estimates in AutoLeap.

Estimates, repair orders, customers and appointments in your AutoLeap shop. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with AutoLeap
AutoLeap logo AutoLeap Cloud Browser

12 tools Read and write

Estimate to repair order

What can you automate in AutoLeap? Use an AI agent, a workflow or a script.

  • Send an estimate for approval

  • Remind customers about open estimates

  • Turn approved estimates into ROs

  • Text a customer a status update

  • Brief you on tomorrow's cars

  • Book declined work back in

Partners only

Does AutoLeap have an MCP server or an API? A Partner API for vendors, nothing a shop can switch on.

AutoLeap has no MCP server, and its REST Partner API gives keys only to approved integration partners, not to shops on Essentials, Pro or Elite (checked 28 Oct 2026). Cotlet runs 12 AutoLeap tools hosted, over MCP for agents and REST for scripts, in your own AutoLeap login.

  • The Partner API covers repair orders, customers, vehicles and appointments, per a public profile of its docs. No estimate or text endpoint is listed, and the docs open only after a sign-in.
  • AutoLeap AIR, the AI receptionist at $99 a month, answers phone calls and adds appointment requests to the calendar. Your own agent cannot call it.
  • Zapier and n8n have no AutoLeap app (both pages answer 404). The official integrations are parts, data, QuickBooks and reviews.
AutoLeap Partner API, AutoLeap AIR and Cotlet compared
What you need Partner APIAutoLeap AIRCotlet
Read repair orders and customers Yes, for partners No Yes
Read estimates and declined work Not listed No Yes
Send an estimate for approval Not listed No Yes, after your OK
Text a customer Not listed Not stated Yes, after your OK
Book an appointment Yes, for partners Requests from calls Yes, after your OK
Who can get it Approved vendors Shops, $99 a month Any AutoLeap login

Checked 28 Oct 2026. Sources: AutoLeap developer portal (Partner API, sign-in required) · API Evangelist: AutoLeap Partner API profile · AutoLeap: Integration partners · AutoLeap AIR

Set up once

How does Cotlet connect to AutoLeap? One account, two ways to connect.

  1. 1Sign in to AutoLeap

    Use your own account in its Cotlet Cloud Browser.

  2. 2Choose MCP or REST

    Connect your agent or create a Cotlet API key.

  3. 3Run your workflow

    Ask your agent or send an HTTP request.

We never keep your AutoLeap password, and no estimate, booking or text reaches a customer until you approve it. Who can see your session

Any MCP client

Connect AutoLeap to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. 1

    Sign in to AutoLeap once. Create a Cotlet account, open AutoLeap in its Cloud Browser, sign in with an Admin or Service Advisor login and press Enable for agents.

  2. 2

    Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the MCP server or connector list of your agent.

  3. 3

    Allow the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts take an API key from the console.

AutoLeap rides on https://cotlet.dev/mcp/v1 together with the other apps on your Cotlet account. Enabled AutoLeap after you connected? Refresh the connector and its 12 tools appear.

Claude
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-autoleap \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-autoleap": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet-autoleap]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: autoleap_read
Make, Zapier
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: autoleap_write
Scripts and HTTP

How to use the AutoLeap REST API

Create your Cotlet API key

Create a Cotlet API key with access to AutoLeap and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect AutoLeap in Cotlet and enable it for agents. Account access: Your own AutoLeap login at app.myautoleap.com. What your agent can open follows the access your login has. You sign in in your own browser and keep any verification AutoLeap asks for.

Make your first AutoLeap API request

REST
curl https://cotlet.dev/api/v1/autoleap/repair-orders \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read repair orders and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt
{
  "status": "success",
  "app": "autoleap",
  "tool": "list_repair_orders",
  "result": {
    "repair_orders": [
      {
        "ro_number": "10482",
        "customer": "Tom Becker",
        "vehicle": "2016 Ford F-150",
        "technician": "Luis",
        "status": "In progress",
        "updated": "2026-10-28"
      },
      {
        "ro_number": "10479",
        "customer": "Priya Nair",
        "vehicle": "2021 Toyota Camry",
        "technician": "Sam",
        "status": "Waiting for parts",
        "updated": "2026-10-27"
      }
    ],
    "next_cursor": null
  }
}

Returns the most recently updated repair orders first, with the RO number, customer, vehicle, assigned technician and the status as the Work Board shows it. Status names are the shop's own.

Use next_cursor to read further pages.

limit: Repair orders per page.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

AutoLeap workflows for agents and automations

AutoLeap workflows you configure
ToolConnect throughExample workflow
n8nHTTP RequestReads one repair order with services, parts, notes and totals. Use get_repair_order in your configured business report.
MakeHTTP > Make a requestLists estimates with customer, vehicle, total and the customer's answer. Use list_estimates in your configured business report.
Python or Node.jsREST APIReads one customer with vehicles, service history and declined services. Use get_customer in your configured business report.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads AutoLeap; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

7 read, 5 write

AutoLeap API endpoints and MCP tools

Estimates4

No tool writes or prices an estimate: send_estimate sends one your advisor built. Only an approved estimate converts; anything else returns an error and nothing is created.

  • list_estimates Lists estimates with customer, vehicle, total and the customer's answer. read

    Returns the newest estimates first, with the estimate ID, customer, vehicle, total, the date it was sent and the customer's answer. The answer is what AutoLeap shows after the customer approves, declines or defers by text or email. Use next_cursor to read further pages.

    MCP callautoleap_read → list_estimates

    REST endpointGET https://cotlet.dev/api/v1/autoleap/estimates

    Parameters

    Parameters: list_estimates
    NameTypeDescription
    status string string Filter by the customer's answer: awaiting, approved, declined or deferred.
    sent_before string string ISO date. Keeps estimates sent before it.
    limit integer integer Estimates per page.
    cursor string string Next page cursor from the previous call.

    Example response

    {
      "estimates": [
        {
          "estimate_id": "est_4821",
          "customer": "Dana Ruiz",
          "customer_id": "cus_1093",
          "vehicle": "2019 Honda CR-V",
          "total": 1240,
          "sent_on": "2026-10-24",
          "status": "awaiting"
        },
        {
          "estimate_id": "est_4817",
          "customer": "Tom Becker",
          "customer_id": "cus_0877",
          "vehicle": "2016 Ford F-150",
          "total": 842,
          "sent_on": "2026-10-23",
          "status": "approved"
        }
      ],
      "next_cursor": null
    }
  • get_estimate Reads one estimate with its services, parts and approval record. read

    Returns the line items (services and parts with prices), the total, who approved or declined and when. AutoLeap stores the approval with the estimate, so the record is read from there. Returns an error if the ID does not exist in this shop.

    MCP callautoleap_read → get_estimate

    REST endpointGET https://cotlet.dev/api/v1/autoleap/estimates/{estimate_id}

    Parameters

    Parameters: get_estimate
    NameTypeDescription
    estimate_id string required string Estimate ID from list_estimates.

    Example input

    {
      "estimate_id": "estimate_8c41d2"
    }

    Example response

    {
      "estimate_id": "est_4821",
      "customer": "Dana Ruiz",
      "vehicle": "2019 Honda CR-V",
      "lines": [
        {
          "type": "service",
          "name": "Front brake pads and rotors",
          "price": 1090
        },
        {
          "type": "service",
          "name": "Brake fluid flush",
          "price": 150
        }
      ],
      "total": 1240,
      "status": "awaiting",
      "approval": null
    }
  • send_estimate Sends an existing estimate to the customer by text or email for approval. writeasks first

    Sends the estimate to the phone number or email saved on the customer. AutoLeap then records the approve, decline or defer answer on the estimate. It does not create or edit estimates. By default you confirm each call; you can switch that off for this tool.

    MCP callautoleap_write → send_estimate

    REST endpointPOST https://cotlet.dev/api/v1/autoleap/estimates/{estimate_id}

    Parameters

    Parameters: send_estimate
    NameTypeDescription
    estimate_id string required string Estimate ID from list_estimates.
    channel string required string text or email.

    Example input

    {
      "estimate_id": "estimate_8c41d2",
      "channel": "channel"
    }

    Example response

    {
      "estimate_id": "est_4825",
      "channel": "text",
      "sent_to": "+1 555 0188",
      "status": "awaiting"
    }
  • convert_estimate_to_repair_order Turns an approved estimate into a repair order. write

    AutoLeap carries the services and parts over without re-entry and returns the new RO number. It reaches no customer and the repair order can be deleted in AutoLeap, so it does not wait for your OK. An estimate that is not approved returns an error and nothing is created.

    MCP callautoleap_write → convert_estimate_to_repair_order

    REST endpointPOST https://cotlet.dev/api/v1/autoleap/estimates/{estimate_id}/to-repair-order/convert

    Parameters

    Parameters: convert_estimate_to_repair_order
    NameTypeDescription
    estimate_id string required string Estimate ID from list_estimates.

    Example input

    {
      "estimate_id": "estimate_8c41d2"
    }

    Example response

    {
      "estimate_id": "est_4817",
      "ro_number": "10483",
      "status": "New",
      "total": 842
    }

Repair orders2

Read only. Status names are your own Work Board columns.

  • list_repair_orders Lists repair orders with customer, vehicle, technician and status. read

    Returns the most recently updated repair orders first, with the RO number, customer, vehicle, assigned technician and the status as the Work Board shows it. Status names are the shop's own. Use next_cursor to read further pages.

    MCP callautoleap_read → list_repair_orders

    REST endpointGET https://cotlet.dev/api/v1/autoleap/repair-orders

    Parameters

    Parameters: list_repair_orders
    NameTypeDescription
    open_only boolean boolean When true, leaves out repair orders that are invoiced.
    updated_since string string ISO date. Keeps repair orders changed on or after it.
    limit integer integer Repair orders per page.
    cursor string string Next page cursor from the previous call.

    Example response

    {
      "repair_orders": [
        {
          "ro_number": "10482",
          "customer": "Tom Becker",
          "vehicle": "2016 Ford F-150",
          "technician": "Luis",
          "status": "In progress",
          "updated": "2026-10-28"
        },
        {
          "ro_number": "10479",
          "customer": "Priya Nair",
          "vehicle": "2021 Toyota Camry",
          "technician": "Sam",
          "status": "Waiting for parts",
          "updated": "2026-10-27"
        }
      ],
      "next_cursor": null
    }
  • get_repair_order Reads one repair order with services, parts, notes and totals. read

    Returns the services and parts, the technician, the notes and the totals. Use it before texting a customer so the message matches the job.

    MCP callautoleap_read → get_repair_order

    REST endpointGET https://cotlet.dev/api/v1/autoleap/ros/{ro_number}/repair-order

    Parameters

    Parameters: get_repair_order
    NameTypeDescription
    ro_number string required string Repair order number from list_repair_orders.

    Example input

    {
      "ro_number": "ro number"
    }

    Example response

    {
      "ro_number": "10482",
      "customer": "Tom Becker",
      "vehicle": "2016 Ford F-150",
      "technician": "Luis",
      "status": "In progress",
      "lines": [
        {
          "type": "service",
          "name": "Front brake pads and rotors",
          "price": 842
        }
      ],
      "total": 842
    }

Customers and vehicles3

Declined and deferred services come from the customer's own history in AutoLeap.

  • list_customers Searches the customer list by name, phone or email. read

    Returns the customer ID, name, phone, email, number of vehicles and the date of the last visit. The declined-services filter uses the declined services AutoLeap keeps per customer. Use next_cursor to read further pages.

    MCP callautoleap_read → list_customers

    REST endpointGET https://cotlet.dev/api/v1/autoleap/customers

    Parameters

    Parameters: list_customers
    NameTypeDescription
    query string string Name, phone number or email.
    has_declined_services boolean boolean When true, keeps customers with services they declined on a past visit.
    limit integer integer Customers per page.
    cursor string string Next page cursor from the previous call.

    Example response

    {
      "customers": [
        {
          "customer_id": "cus_1093",
          "name": "Dana Ruiz",
          "phone": "+1 555 0142",
          "email": "dana@example.com",
          "vehicles": 1,
          "last_visit": "2026-09-12"
        }
      ],
      "next_cursor": null
    }
  • get_customer Reads one customer with vehicles, service history and declined services. read

    Returns contact details, each vehicle, the service history by visit and the services the customer declined or deferred. Phone and email are the ones saved on the customer; nothing is guessed.

    MCP callautoleap_read → get_customer

    REST endpointGET https://cotlet.dev/api/v1/autoleap/customers/{customer_id}

    Parameters

    Parameters: get_customer
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.

    Example input

    {
      "customer_id": "customer_8c41d2"
    }

    Example response

    {
      "customer_id": "cus_1093",
      "name": "Dana Ruiz",
      "phone": "+1 555 0142",
      "vehicles": [
        {
          "vehicle_id": "veh_2210",
          "description": "2019 Honda CR-V"
        }
      ],
      "history": [
        {
          "date": "2026-09-12",
          "ro_number": "10311",
          "summary": "Oil change and tire rotation"
        }
      ],
      "declined_services": [
        {
          "date": "2026-09-12",
          "name": "Front brake pads and rotors",
          "price": 1090
        }
      ]
    }
  • create_customer Adds a customer, with a vehicle if you give one. write

    Creates the customer in your shop and returns the new ID. It reaches no one and you can archive the customer in AutoLeap, so it does not wait for your OK.

    MCP callautoleap_write → create_customer

    REST endpointPOST https://cotlet.dev/api/v1/autoleap/customers

    Parameters

    Parameters: create_customer
    NameTypeDescription
    name string required string Full name.
    phone string string Mobile number, used for texts.
    email string string Email address.
    vehicle string string Year, make and model, for example 2018 Subaru Outback.

    Example input

    {
      "name": "Jane Doe"
    }

    Example response

    {
      "customer_id": "cus_1120",
      "name": "Marcus Lee",
      "phone": "+1 555 0188",
      "vehicles": [
        {
          "vehicle_id": "veh_2251",
          "description": "2018 Subaru Outback"
        }
      ]
    }

Calendar and texts3

Texts go to the mobile number saved on the customer. AutoLeap lists Two-Way Texting from the Pro plan; Essentials texts one way.

  • list_appointments Lists appointments on the shop calendar between two dates. read

    Returns appointments in time order with customer, vehicle, the requested service and the assigned technician when one is set. Online bookings and appointments made by staff appear in the same list.

    MCP callautoleap_read → list_appointments

    REST endpointGET https://cotlet.dev/api/v1/autoleap/appointments

    Parameters

    Parameters: list_appointments
    NameTypeDescription
    from string required string ISO date, start of the range.
    to string required string ISO date, end of the range.
    cursor string string Next page cursor from the previous call.

    Example input

    {
      "from": "from",
      "to": "to"
    }

    Example response

    {
      "appointments": [
        {
          "appointment_id": "apt_7731",
          "start": "2026-10-29T08:30:00",
          "customer": "Priya Nair",
          "customer_id": "cus_0951",
          "vehicle": "2021 Toyota Camry",
          "service": "Check engine light",
          "technician": "Sam"
        }
      ],
      "next_cursor": null
    }
  • create_appointment Books an appointment on the shop calendar for a customer and vehicle. writeasks first

    The appointment appears on the live calendar. The shop's reminder settings in AutoLeap may then text or email the customer, so it counts as reaching a person. A slot that clashes with another booking returns an error. By default you confirm each call; you can switch that off for this tool.

    MCP callautoleap_write → create_appointment

    REST endpointPOST https://cotlet.dev/api/v1/autoleap/customers/{customer_id}/appointments

    Parameters

    Parameters: create_appointment
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.
    vehicle_id string required string Vehicle ID from get_customer.
    start string required string ISO date and time.
    service string required string What the customer comes for.
    technician string string Technician name from the calendar.

    Example input

    {
      "customer_id": "customer_8c41d2",
      "vehicle_id": "vehicle_8c41d2",
      "start": "start",
      "service": "service"
    }

    Example response

    {
      "appointment_id": "apt_7740",
      "start": "2026-11-03T09:00:00",
      "customer": "Dana Ruiz",
      "vehicle": "2019 Honda CR-V",
      "service": "Front brake pads and rotors",
      "technician": null
    }
  • send_text_message Sends a text message to a customer from your shop. writeasks first

    Sends the text to the mobile number saved on the customer. A customer with no mobile number returns an error and nothing is sent. A sent text cannot be recalled. By default you confirm each call; you can switch that off for this tool.

    MCP callautoleap_write → send_text_message

    REST endpointPOST https://cotlet.dev/api/v1/autoleap/customers/{customer_id}/text-messages

    Parameters

    Parameters: send_text_message
    NameTypeDescription
    customer_id string required string Customer ID from list_customers.
    body string required string Message text.

    Example input

    {
      "customer_id": "cus_1093",
      "body": "Hi Dana, your CR-V brake estimate of $1,240 is still open. Reply here if you have questions."
    }

    Example response

    {
      "customer_id": "cus_1093",
      "sent_to": "+1 555 0142",
      "body": "Hi Dana, your CR-V brake estimate of $1,240 is still open. Reply here if you have questions.",
      "status": "sent"
    }
Encrypted, revocable

Who can see my AutoLeap session, and how do I revoke it?

  • What we store

    Your signed-in AutoLeap profile, AES-256-GCM, in Finland. Not the password.

  • What your agent gets

    The 12 AutoLeap tools. No cookie, no Partner ID or Auth Key.

  • What the session sees

    What the login's role sees: estimates, ROs, customers, the calendar.

  • What no tool touches

    Invoices, parts orders, inventory, shop settings, users and deletes.

  • One device per login

    AutoLeap signs a user out of the last device. The Cloud Browser counts as one.

  • How to cut access

    Disable for agents, reset the browser, or change the login's password.

Because AutoLeap allows one device per user, signing in to the Cloud Browser with the login at your front counter logs the counter out. Use a login nobody works in all day, for example the owner's office login. AutoLeap includes 5 users and sells more, but its terms count a user as an employee or contractor, so ask your account manager before you add one for the agent. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.

Account risk

Is it against AutoLeap's terms? Account safety No bot clause, but a strict rule on passwords.

"Client shall keep Authorized User passwords confidential and cause Authorized Users not to share their respective passwords with any other individual."
AutoLeap Standard SaaS Agreement, section 1.5(b), effective 5 Jun 2026

The agreement names no robots, scrapers or AI agents. Section 1.6(a) bars letting "any person" use the Services outside the agreement, and 1.9 lets AutoLeap suspend an account it suspects of breaking 1.5 or 1.6, with notice before or after. You type the password into the Cloud Browser yourself and Cotlet never sees it, but AutoLeap could still read an agent in your login as access by someone else. We found no public case of a shop suspended for a script or an agent (checked 28 Oct 2026).

How we keep your account looking like you

  • Your own AutoLeap login, signed in by you
  • One Cloud Browser with its own IP and cookies, so one steady device
  • Estimates, bookings and texts wait for your OK
  • No tool deletes a customer, estimate or repair order
  • If AutoLeap objects, we pause the AutoLeap tools for everyone within 24 h

AutoLeap's SMS terms let a customer text STOP to end messages from your shop, and marketing texts need the customer's opt-in. Keep agent texts to the car in your bays and its estimate.

Tested every 12 h

What happens when AutoLeap changes? We fix the tool; your prompts do not change.

between tests of the AutoLeap reads and conversions
12 h
between tests of estimates, bookings and texts a customer would get
24 h
for a call to an AutoLeap tool paused for repair
$0

AutoLeap ships updates to its web app without a public changelog, and the Work Board columns are yours to rename. When a screen moves, we repair the tool, and a daily follow-up keeps its prompt. status.cotlet.dev checks the site, console and API every 3 minutes.

3 tools ask first

Approvals, undo and mistakes Customers hear from your shop only after you say yes.

  1. 01 Finds open estimates Sent over 2 days ago, still awaiting an answer.
  2. 02 Reads each customer Mobile number, vehicle and the estimate total.
  3. 03 Waits for your OK Each reminder text shows up in your Cotlet console.
  4. 04 Reports back Who got a text, who has no mobile number saved.
Which AutoLeap actions can be undone
ActionUndo
Create a customerArchive the customer in AutoLeap
Convert an estimate to a repair orderDelete the repair order in AutoLeap
Book an appointmentCancel it on the calendar; a reminder may be out already
Send an estimateNo, the customer has it; send a revised one
Text a customerNo, a sent text cannot be recalled

3 of 12 tools ask first: send_estimate, create_appointment and send_text_message, the three a customer sees. A new customer or a converted estimate reaches nobody and can be removed, so those run at once. Switch the wait off per tool for a scheduled run.

Your shop's reminder settings may text the customer about a new booking on their own. Check them before the agent books a batch.

MCP call
{
  "name": "send_text_message",
  "arguments": {
    "customer_id": "cus_1093",
    "body": "Hi Dana, your CR-V brake estimate of $1,240 is still open. Reply here if you have questions."
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/autoleap/customers/cus_1093/text-messages \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Dana, your CR-V brake estimate of $1,240 is still open. Reply here if you have questions."}'
Response
{
  "customer_id": "cus_1093",
  "sent_to": "+1 555 0142",
  "body": "Hi Dana, your CR-V brake estimate of $1,240 is still open. Reply here if you have questions.",
  "status": "sent"
}

Scripts reach the same tools over REST at /api/v1/autoleap, with the same key and price, so a cron job can list approved estimates each morning before the first car. A customer with no mobile number returns an error, and a failed call costs nothing. The tools table lists the REST path of each tool.

Pay per call

How much does the AutoLeap MCP server cost?

About $44 a monthfor one shop closing about 140 repair orders a month, 7,500 credits. Your AutoLeap plan stays billed by AutoLeap.

A month of AutoLeap jobs for one shop, in credits
JobCallsCredits
Remind 3 customers about open estimates, daily7 × 221,540
Turn about 4 approved estimates into ROs, daily5 × 221,100
Brief on about 6 of tomorrow's cars7 × 221,540
Status texts on 3 open ROs, daily7 × 221,540
Book 2 customers with declined work, weekly7 × 4280
Cloud Browser, 30 days1,500
Total7,500
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works on Essentials, Pro and Elite

The month is our example: AutoLeap's own blog uses a shop with 140 closed repair orders a month at a $600 average ticket. AutoLeap itself runs $179 to $409 a month billed yearly. Dollars at the $29 pack rate.

Cotlet credit packs: price, credits and calls at 10 credits each
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.

Other options

AutoLeap MCP server on GitHub, Zapier or hosted: which to use There is no other AutoLeap MCP server yet.

Other ways to reach AutoLeap data, checked 28 Oct 2026
OptionWhat it doesWhere it stops
UncleStalin728/kims-production-board-shareOne shop's production board. A script, run by Claude in Chrome on an open AutoLeap tab, reads approved and in-progress orders from AutoLeap's internal API.Reads one list, on an undocumented endpoint, while your Chrome tab stays open. 0 stars, last push 26 Apr 2026.
api-evangelist/autoleapA third-party profile of the Partner API: repair orders, customers, vehicles, appointments, inventory.Docs only. The keys still go to approved partners.
AutoLeap Partner APIVersioned REST with a Partner ID and Auth Key.For vendors AutoLeap approves; no estimate or text endpoint listed.
AutoLeap AIRAutoLeap's AI receptionist: answers calls, puts appointment requests on the calendar.Phone calls only, $99 a month, not callable from your agent.
SteerIntegration partner for booking, phones, reminders and text campaigns.Another subscription with its own automations, not your own agent.

Zapier and n8n have no AutoLeap app. A script on the internal API can be written in an afternoon and breaks with the next app update. AIR and Steer cover the phone and the marketing. Cotlet is for an agent you pick that chases estimates and texts customers from your shop login, on a schedule.

EU company, since 2019

Who runs Cotlet A company you can look up.

Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the AutoLeap tools to contact@cotlet.dev.

AutoLeap API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open AutoLeap under Integrations in the console and sign in to AutoLeap in its Cloud Browser. The trial starts with your first app, with no card.

How do I connect AutoLeap to ChatGPT or Claude?

Sign up at cotlet.dev, log in to AutoLeap once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your AutoLeap account through Cotlet, in their phone apps too.

What can ChatGPT do in AutoLeap?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in AutoLeap: follow up on unapproved estimates; convert approved estimates into repair orders; brief for tomorrow\. You ask in plain words, and anything that reaches other people waits for your OK first.

Does Cotlet need AutoLeap Partner API credentials?

No. Cotlet works in the AutoLeap web app with your own login, so it needs no Partner ID or Auth Key. AutoLeap issues those to approved integration partners, and its developer portal is behind a sign-in.

Will my customers see a different sender when my agent texts them?

The text goes out through AutoLeap's customer communication from your shop, the same way a text sent by hand does. Cotlet does not use a separate number.

Will the agent log me out of AutoLeap?

It can. AutoLeap lets each user be signed in on one device at a time, and the Cloud Browser is a device. Sign it in with a login nobody uses at the counter, and the shop keeps working while the agent does.

Does AutoLeap have webhooks?

None a shop can set up: the Partner API and its docs are for approved partners. Run your agent on a schedule instead, for example a list_estimates pass every morning.

Can the agent write or price an estimate?

No. send_estimate sends an estimate your advisor already built, and convert_estimate_to_repair_order works only once the customer approved it. Labor times and parts stay with your team.

Is the MCP server different from the REST API?

Only the door differs. Both carry the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and cron jobs use REST.

Is Cotlet affiliated with AutoLeap?

No. Cotlet is independent and not affiliated with AutoLeap Inc.

Can I use the AutoLeap API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

Give your agent access to AutoLeap.

Free 7-day trial with 2,000 credits, no card needed.