The developer API for real local service data
One MCP endpoint returns real businesses on Lokuli with their actual services, prices and durations, open times from each shop's live calendar, and local price ranges built from Lokuli's own call-arounds. It can hold a real slot, confirmed by text. About 900 service types. Prices from local pros anywhere in the US; businesses you can book on Lokuli are mostly in California. The data is real and live. No API key. No cost.
Point any MCP client that supports remote servers to the endpoint below. Your client discovers every tool and its input schema. No registration. No API key. Claude, ChatGPT, Gemini and Grok users can add it as a custom connector: setup steps.
MCP access is open. Connect and start querying immediately. No sign-in, no OAuth, no registration.
Requests are JSON-RPC 2.0 messages. Every tool returns a text summary and structured JSON with typed fields.
book_appointment and request_quotes only text the person a link. Nothing is booked, and no business is called, until they tap it.
The Local Service API exposes these six tools through MCP. Agents discover them automatically on connection.
The same read-only call in four formats. Each one asks for house cleaning in San Diego. The data shown under each example is real: it is what the live server returned on Oct 31, 2026. Run these from a server or script: browser calls are limited to allowed origins.
Businesses you can book on Lokuli are mostly in California, with a few in other states; what you get is real and live. A search can return businesses you can book, public-record businesses (marked not bookable) with local price ranges, or nothing yet. When nothing is bookable, request_quotes works anywhere in the US: Lokuli phones pros near any US ZIP code and texts the person their prices.
Local price ranges are built from quotes Lokuli collected in its own call-arounds. They appear only when there are 3 or more quotes for the same job in the same city, and they are what local shops quoted, not any one business's own price.
These are ideas, not shipped products. Each follows the same pattern: your app reads real data and holds a time or asks for prices, and the person confirms by text. Businesses you can book on Lokuli are mostly in California, so plan for searches that return no bookable business; request_quotes works anywhere in the US.
Build an assistant that finds a business, reads its prices and open times, and holds a time. The person confirms by text. Works with any MCP-compatible model; the agent discovers the tools automatically.
Use the same flow behind a voice or chat interface. It collects the person's name and US mobile number, holds a time with book_appointment, and tells them a text is coming.
A tenant or fleet app can look up a business and its open times, then hold a time for the person to confirm, or ask Lokuli for prices with request_quotes. The person always confirms; quotes work for any US ZIP code, and businesses you can book are mostly in California.
Combine find_businesses (prices set by businesses on Lokuli, and local price ranges for public-record businesses) with request_quotes for exact prices at the person's day and time.
Every tool returns a text summary in result.content and structured JSON in result.structuredContent. The fields below come from real responses (and, for holds, from the server's documented behavior). Optional fields appear only when there is data.
Businesses on Lokuli that can be booked. Returned by find_businesses.
| Field | Type | Description |
|---|---|---|
| name | string | Business name as set on its Lokuli page. |
| slug | string | Pass as business to the other tools. |
| url | string | The business's lokuli.com/shop/... page. |
| trade, city, zip | string | Kind of business and location. |
| bookable | boolean | true for businesses on Lokuli. |
| matched | string | How it matched the search: name, service, synonym or trade. |
| matchedServiceIds | string[] | Ids of the services that matched. |
| address | string | Street address. |
| services | array | Each service: id, name, price (USD) and durationMinutes. |
| rating | object | average, count and source, only when the business has Lokuli reviews. |
Businesses built from public records. They are not on Lokuli and cannot be booked here.
| Field | Type | Description |
|---|---|---|
| name, slug, url | string | As for shops. |
| trade, city, zip | string | Kind of business and location. |
| address | string | Street address, when known. |
| matched | string | How it matched the search, for example name. |
| bookable | boolean | Always false. |
| priceRange | object | low, high, quotes, month, note. Present only when Lokuli has 3 or more quotes for the same job in the same city. |
| note | string | Says it is not on Lokuli yet and points to request_quotes. |
For a business on Lokuli (kind: "shop"). For a public-record business, kind is "listing" and the result has its category, location, status and priceRange instead.
| Field | Type | Description |
|---|---|---|
| kind, name, slug, url | string | Identity of the business. urlEs is its Spanish page. |
| bookable | boolean | Whether it can be booked through book_appointment. |
| booking | object | via, instantBook, payment and confirmation: how booking works there. |
| address, phone, city | string | Included when the business has them. |
| timezone | string | IANA time zone of the business. |
| hours | object | Hours by day, for example "monday": "8:00 AM–6:00 PM" or "Closed". |
| services | array | id, name, price, durationMinutes, and a short description when the business wrote one. |
| team | array | Bookable team members (id, name), when there are any. Pass an id as staff_id. |
| rating | object | Lokuli reviews summary, when there are reviews. |
Open slots from the business's live Lokuli calendar.
| Field | Type | Description |
|---|---|---|
| business | string | The business slug. |
| service | object | id, name, price, durationMinutes. |
| timezone | string | IANA time zone of the business. |
| days | array | For each date: date (YYYY-MM-DD) and slots. Days with no openings say why. |
| days[].slots[].start | string | ISO time. Pass it unchanged to book_appointment. |
| days[].slots[].label | string | The time as shown in the business's time zone, for example "8:00 AM". |
| booking | object | How booking works at this business. |
Returned when a time is held. Not run in the examples on this page, because it texts a real person.
| Field | Type | Description |
|---|---|---|
| ok, status | boolean, string | true and "held". |
| holdExpiresAt | string | ISO time when the hold is released if the person has not tapped Confirm (15 minutes). |
| business, url, service | string, object | Which business and service. |
| start, when, timezone | string | The held time. |
| instantBook | boolean | Whether the business confirms at once after the person taps Confirm. |
| staff | string | Name of the team member, when one was picked. |
| no hold: ok false, url | boolean, string | A business that takes a card when booking cannot be held. The result has ok: false, an error message and that business's booking page as url; isError is not set. |
Real results, fetched Oct 31, 2026: ZIP 75024 returned {"ok": true, "zip": "75024", "city": "Plano", "state": "TX", "tz": "America/Chicago"} and the text “Yes, Lokuli covers 75024 (Plano, TX). Calls to pros go out Monday–Saturday, 11am–6pm local time.”; ZIP 00000 returned {"ok": false, "zip": "00000", "reason": ...} with the reason “00000 isn't a US zip code Lokuli can find. Check the 5 digits.”
| Field | Type | Description |
|---|---|---|
| ok | boolean | Whether Lokuli can call pros near the ZIP code (any US ZIP code). |
| zip, city, state | string | The ZIP code, and the city and state it is in. |
| tz | string | IANA time zone of the ZIP code, for example America/Chicago. Calls go out in this time zone. |
| reason | string | Why not, when ok is false. |
Using the API costs nothing and needs no key. MCP calls have no per-IP limit. What is limited is what Lokuli texts and who may call from a browser. The full list is in auth.md.
| Limit | Value |
|---|---|
| Confirmation texts | 3 per phone number per day for price requests, and 3 for bookings |
| Bookings waiting for confirmation | One per phone number, and at most 3 per business |
| Lokuli's texts overall | A daily cap |
| Phone numbers | A 10-digit US mobile number that can receive texts; toll-free numbers are refused |
| Area | Quotes: any US ZIP code (the 50 states and DC). Booking: businesses on Lokuli, most of them in California |
| Calls to businesses | Monday to Saturday, 11am to 6pm in the ZIP code's local time; a request made outside those hours waits for the next opening |
| Browser (CORS) calls | claude.ai, claude.com, anthropic.com, chatgpt.com, openai.com, gemini.google.com, grok.com, x.ai and lokuli.com. Server-to-server calls without an Origin header are accepted. |
| Plain HTTP API and /ask chat | 10 requests per day per IP address (MCP calls have no per-IP limit) |
There are no webhooks. A hold moves forward by text to the person, not by callback to your app.
| Step | What happens | Who is told |
|---|---|---|
| book_appointment | The time is held for 15 minutes and Lokuli texts the person a link. | The person. The business is not told. |
| Person taps Confirm | The hold becomes a request, or is confirmed at once at instant-book businesses. | The business |
| Business accepts or declines | The same link shows the answer. | The person |
| 15 minutes pass without a tap | The hold is released and the business never hears about it. | No one |
Lokuli has no SDK of its own. Use any MCP client library, or send JSON-RPC 2.0 messages with any HTTP client.
Connect any MCP client that supports remote servers. It discovers the tools and their input schemas. Claude, ChatGPT, Gemini and Grok can add the URL as a custom connector.
POST JSON-RPC 2.0 messages to the same endpoint from any language. Responses are plain JSON (not streamed). The endpoint is for POST requests.
A small HTTP API covers price requests and ZIP coverage. It is described by an OpenAPI file. Booking is on the MCP server only.
There is no npm or Python SDK and there are no webhooks today. Poll the read-only tools when you need fresh data.
Two kinds of problem. A problem with a tool's arguments comes back as a normal JSON-RPC result with isError: true and a message you can read. A protocol problem comes back as an HTTP error or a JSON-RPC error. The examples below are real responses from the live server, fetched Oct 31, 2026.
| Where | Code | When It Happens |
|---|---|---|
| Tool result | isError: true | An argument is missing or wrong (for example an unknown business slug or service id, or a time that is no longer open), or a limit was reached. Read the message and fix the call. The HTTP status is 200. |
| HTTP 400 | -32700 | The body is not a JSON-RPC 2.0 message. |
| HTTP 403 | -32600 | A browser request came from an origin that is not allowed. Server-to-server calls are not affected. |
| JSON-RPC | -32601 | An unknown method, or an unknown tool name (-32602). |
| HTTP 500 | -32603 | Internal error. Retry the request. |
The tools are strict about a few formats. They are the same in every tool.
zipString of 5 digits, for example "90640". Any US ZIP code works for check_coverage and request_quotes; find_businesses also takes a city.
dateYYYY-MM-DD. For get_available_times, today up to 90 days ahead. For request_quotes, today through 60 days ahead.
time (request_quotes)"10:00 AM" or "14:30", in the person's local time.
phoneA 10-digit US mobile number that can receive texts. Toll-free numbers are refused.
start (book_appointment)The slot's start exactly as get_available_times returned it, for example "2026-11-02T16:00:00.000Z" (real value, fetched Oct 31, 2026).
business, service_idbusiness is a slug from find_businesses or a lokuli.com/shop/... link. service_id comes from get_business.
From emergency plumbing to wedding photography. find_businesses searches the businesses on Lokuli for any of them, and request_quotes has Lokuli phone local pros for the rest. Browse every service type at lokuli.com/services.
The Local Service API is the developer-facing interface to Lokuli: an MCP server at lokuli.com/mcp with six tools, plus a small HTTP API for price requests and ZIP coverage. It returns real businesses on Lokuli with their actual services, prices and durations, open times from each shop's live calendar, and local price ranges built from Lokuli's own call-arounds. It can hold a slot that the person confirms by text. It works for any US ZIP code for price requests; businesses you can book on Lokuli are mostly in California.
Businesses you can book on Lokuli are mostly in California, with a few in other states, and the list changes. The data is real and live. For example, on Oct 31, 2026 a search for house cleaning near San Diego returned one bookable business with its actual services, prices and open times. A search for barbers near Montebello (90640) returned public-record barbershops, not bookable, with a local price range of $20–$40 built from 3 quotes. A search for a plumber near San Jose (95112) returned no business on Lokuli yet. Where nothing is bookable, request_quotes works anywhere in the US: Lokuli phones pros near any US ZIP code and texts the person their prices.
No. MCP access is open: no API key, no registration, no OAuth. Connect an MCP client to https://lokuli.com/mcp, or POST JSON-RPC 2.0 messages to it. Don't send passwords, tokens or other secrets to the endpoint.
Any. MCP is protocol-level, so any MCP client library works, and any HTTP client can POST JSON-RPC 2.0 messages. The code examples below use Python, JavaScript (Node.js), cURL and raw MCP JSON. Responses are JSON.
From Lokuli's own call-arounds. Local price ranges are built from quotes Lokuli collected in its own call-arounds. They appear only when there are 3 or more quotes for the same job in the same city, and they are what local shops quoted, not any one business's own price. They appear as a priceRange on the public-record businesses that find_businesses and get_business return, marked not bookable.
Every tool returns a text summary and structured JSON (structuredContent). find_businesses returns shops (businesses on Lokuli, with services that carry an id, price and durationMinutes) and listings (public-record businesses, with a priceRange when there are enough quotes). See the result reference and the real example on this page.
Problems with a tool's arguments come back as a normal result with isError set to true and an error message (for example, an unknown business or service id). Protocol problems come back as JSON-RPC errors: 400 for a message that is not JSON-RPC 2.0, 403 for a browser origin that is not allowed, -32601 for an unknown method and -32602 for an unknown tool name. The endpoint is for POST requests; opening the address in a browser shows a short information page.
book_appointment holds a time for 15 minutes and texts the person a link. It is booked only when they tap Confirm; then the business accepts or declines the request (instant-book businesses confirm at once). Payment is at the business. A business that takes a card when booking returns a link to its own booking page instead of a hold. The API does not process payments.
No. Lokuli has no webhooks and no SDK today. Use any MCP client library, or plain HTTP, and read the tools again when you need fresh data. The hold and confirmation steps happen by text to the person, not by callback.
There is no API fee and no key. Read Lokuli's terms (lokuli.com/terms) and the limits in auth.md first: the tools that text a person are limited per phone number, and browser-based calls are limited to a list of allowed origins.
Quotes: any US ZIP code (the 50 states and DC), with calls Monday to Saturday, 11am to 6pm in the ZIP code's local time. Booking: businesses on Lokuli, most of them in California and a few in other states. Check a ZIP code with check_coverage (or GET https://lokuli.com/ask/coverage?zip=90640), which returns the place, state and time zone. On Oct 31, 2026, check_coverage for 75024 returned: “Yes, Lokuli covers 75024 (Plano, TX). Calls to pros go out Monday–Saturday, 11am–6pm local time.” For 00000 it returned: “00000 isn't a US zip code Lokuli can find. Check the 5 digits.”
For price requests, start the service name with the word "test" (for example "test house cleaning"). The text and link still go to the number given, but no business is called. Use only your own number. The search and availability tools read live data.
Lokuli is the platform where businesses keep their services, prices and calendars. LocalServiceAPI.com is developer documentation for the endpoints that read them: the MCP server at lokuli.com/mcp and the small HTTP API. BookingClaw is Lokuli's AI-native directory of local services.
Agents can do the reading and the holding on their own, but not the deciding. book_appointment and request_quotes only text the person a link. Nothing is booked, and no business is called, until the person taps it.
The Local Service API is one part of the Lokuli ecosystem for local services. Explore the other platforms and entry points.
Real businesses, prices and open times. About 900 service types. MCP over Streamable HTTP. $0 cost. No API key. The person confirms by text. Businesses you can book on Lokuli are mostly in California, and the data is real.