NestBuddy Developer Portal & Agentic API
Connect your AI agents, moving concierge assistants, and custom software directly to NestBuddy’s vetted trade network across Brisbane Bayside. Built with zero-friction public access, live diagnostic sandbox modes, and full Model Context Protocol (MCP) support.
Zero-Key Access
Integrate instantly without waiting for API keys or filling sales forms.
Model Context Protocol
Native Streamable HTTP server for ChatGPT, Claude Desktop, and Cursor.
1-Tap Verification
Passwordless magic email link verifies leads with a single customer tap.
Diagnostic Sandbox
Test partial payloads safely with ?dry_run=true.
1. Platform Architecture & Protocol Standard
NestBuddy provides a headless, self-describing intake infrastructure tailored for modern autonomous agents, LLM tool callers, and web applications. All endpoints are hosted under https://nestbuddy.com.au and return standard application/json payloads.
REST Base URL (Production)
https://nestbuddy.com.au/api/v1/quotesMCP Server Endpoint (Streamable HTTP)
https://nestbuddy.com.au/api/mcp2. Core REST API Endpoints
Integrate quote discovery and lead submission directly into your application.
/api/v1/quotesReturns the active registry of supported trade categories (removalist, bond_clean, storage, gardener, conveyancer), location routing rules, and brand trust context.
curl -s https://nestbuddy.com.au/api/v1/quotes
/api/v1/quotesValidates the moving quote payload, registers the lead in pending verification status, and immediately dispatches a 1-tap confirmation magic link to the customer’s email.
curl -X POST https://nestbuddy.com.au/api/v1/quotes \
-H "Content-Type: application/json" \
-d '{
"services": ["removalist", "bond_clean"],
"locations": {
"from": "Wynnum QLD 4178",
"to": "Manly QLD 4179"
},
"timing": {
"date": "2026-11-19",
"date_mode": "on"
},
"home": {
"bedrooms": "3",
"bathrooms": "2",
"property_type": "house"
},
"contact": {
"name": "Jane Doe",
"email": "jane@example.com",
"phone": "0400123456",
"preference": "email"
}
}'3. Rate Limiting & HTTP Headers
NestBuddy uses token-bucket IP rate limiting to prevent spam and DoS attacks while remaining open for authentic AI agents and customer requests. Every API response includes standard IETF RFC RateLimit headers so agents can self-throttle in real time.
| Header | Description | Default Value |
|---|---|---|
| RateLimit-Limit | Maximum requests allowed per window | 20 |
| RateLimit-Remaining | Remaining requests in current window | 0–20 |
| RateLimit-Reset | Seconds until rate limit bucket refills | Seconds |
| Retry-After | Returned on HTTP 429 (Too Many Requests) | Seconds |
4. Machine-Readable Specifications & Manifests
NestBuddy publishes machine-readable contracts and discovery files at predictable canonical endpoints: