For AI agents
Zaptu for AI agents
Zaptu connects people with independent local home-service contractors. Zaptu does not perform the work and does not book appointments. Every service, plumbing included, is a contact request sent with the person’s consent.
For a plain overview with setup steps for Claude, Cursor and ChatGPT, see Zaptu for AI assistants.
The short version
- Every service is a contact request (plumbing, cleaning, pest control, garage door, HVAC, handyman, other). Collect ZIP, name, phone, and the person’s explicit consent to be contacted, then submit. Tell the person that details may be shared with Polyares and its service-provider partners, and Polyares, those partners, or Zaptu may call or text about the request. Requests are passed along when a participating provider covers the ZIP code; there is no live buyer yet.
- Never place a call. Do not dial, autodial, transfer, or place a call for the person.
- A request is not a booking. Do not promise a callback, an arrival time, or a named company. Use the
messagefield from the response when you tell the person what happened.
Services
| service_type | Status | What to do |
|---|---|---|
plumbing | Collecting | Submit with consent. Describe the problem in notes. |
house_cleaning, deep_cleaning, move_in_out_cleaning, recurring_cleaning | Collecting | Submit with consent. Add bedrooms or square feet if known. |
pest_control | Collecting | Submit with consent. |
garage_door | Collecting | Submit with consent. |
hvac, handyman, other | Collecting | Submit with consent. Describe the job in notes. |
US residential only. The live list is always at api.zaptu.ai/v1/services.
What to tell the person
After you submit (any service):
Your request was sent to Zaptu. It is passed along when a participating provider covers your ZIP code. This is not a booking, and no one has been scheduled.
Connect over MCP
Streamable HTTP, stateless, no sign-in: https://api.zaptu.ai/mcp
{
"mcpServers": {
"zaptu": { "url": "https://api.zaptu.ai/mcp" }
}
}
| Tool | Use it for |
|---|---|
request_home_service | Submit a request for any service. Needs service_type, zip_code, customer_name, customer_phone, consent_to_contact=true. Add dry_run=true to test. |
request_cleaning | Shortcut for house cleaning. |
get_lead_status | Look up a request by lead_id. |
list_supported_services | Supported services and the rules. |
REST API
OpenAPI: api.zaptu.ai/openapi.json. CORS is open, no key needed.
curl -s https://api.zaptu.ai/v1/intake \
-H 'Content-Type: application/json' \
-d '{"service_type":"house_cleaning","zip_code":"33139",
"customer_name":"Jamie Example","customer_phone":"305-555-0100",
"consent_to_contact":true,"bedrooms":2,"dry_run":true}'
dry_run validates and answers without saving or passing anything along. Leave it out for a real request.
Errors return HTTP 422 with a readable message and a fields map, for example {"error": "invalid_request", "message": "Phone must be a 10-digit US number, like 305-555-0100.", "fields": {"customer_phone": "..."}}. Too many requests returns 429.
Discovery files
- llms.txt and llms-full.txt
- /.well-known/mcp.json
- Server card (tools and schemas)
- OpenAPI
Contact
Questions about the connector: hello@zaptu.ai.