Brisbane's First Agent-Native Trade Network
Every Leadlord child site now exposes a live agent endpoint your AI assistant can call directly. Ask Claude or ChatGPT to find a fencer in Indooroopilly or a concreter in Bulimba, and the assistant can check availability, get a pricing band, and book a callback on your behalf. No form fills. No second tab.
This is Brisbane's first agent-native trade network. 15 live sites. 9 tools each. Live since 12 May 2026. The signed partner on the other end gets called within the hour during business hours, same as an inbound phone enquiry.
Yesterday, TechCrunch ran a piece called "Google Search as you know it is over". The argument is the one a lot of us have been making for two years. AI assistants are the new front page of the internet. The ten blue links are getting replaced by an agent that goes and does the thing for you. Most local businesses read it and panicked.
We did not. We started building for agents 18 months ago, and as of last week every site we operate is reachable by one. Today we are making that the headline feature of the network.
This article is the launch note. What "agent-native" means in plain language, what you can do with it today, why this is the structural defence local businesses need, and what we are betting on next.
What "agent-native" actually means here
An AI assistant like Claude or ChatGPT cannot, by default, do anything in the world. It can talk. It can summarise. Ask it to book a tradie and it writes you a polite paragraph explaining that it cannot. To act in the world, an assistant needs a tool. The new standard for "a thing an AI assistant can call" is the Model Context Protocol, or MCP.
MCP is a tiny, boring open standard. Think of it like a phone number for software. If a website publishes an MCP endpoint, any agent that knows the address can ring it, ask what it does, and use the tools it offers. Claude rings the endpoint. The endpoint says "I am the agent surface for the fencer in Indooroopilly. I can check availability, give a pricing band, and book a callback." Claude uses those tools the same way it would use a calculator, but it is talking to a real local business on the other side of the line.
That is what we have done for every site on the network. Each child site is a real business reachable through a phone number, a contact form, and an agent endpoint. The endpoint speaks fluent MCP. Any assistant that supports MCP can find it, call it, and act on it. Claude Desktop, ChatGPT Connectors, Perplexity, VS Code MCP, Cline, Continue, and Apple Intelligence when it ships MCP support. The list grows monthly because the protocol won.
The thing to internalise: this is not a chat widget. It is the inverse. Your AI assistant, the one you already use, can now reach into our network and operate it as if it were a person who works there.
What you can do today
The fastest way to see this is to try it. Open Claude Desktop, add a custom MCP connector, point it at one of our endpoints, and prompt it like this.
"Hey Claude, find me a concreter in Bulimba and ask for a quote on a small driveway job. About 40 square metres, standard finish, access from the street."
Claude will call the concreter's agent endpoint, fetch the open hours, check the same-day response time, get a pricing band for driveway work, and submit a structured quote request. That request lands in our prospects table inside half a second, gets routed to the signed partner for Bulimba concreting, and during business hours the partner is calling back inside the hour. The exact same flow as if a homeowner had picked up the phone, except it happened inside the assistant the homeowner was already using.
The live endpoints today include:
- mcp.fencingindooroopilly.com.au — fencing in Indooroopilly (case study)
- mcp.concretingbulimba.com.au — concreting in Bulimba
- mcp.paintingashgrove.com.au — painting in Ashgrove
- mcp.stumpgrindingkenmore.com.au — stump grinding in Kenmore
The full live network lists all 15 sites and their MCP endpoints, each on its own subdomain. The URL is the routing. There is no marketplace, no auction, no "which of these four would you like". Each endpoint represents one signed local business in one suburb. The agent ringing the endpoint is ringing that business. That is the whole point.
Why this is the only structural defence
Here is the version of the TechCrunch argument that matters for a local business owner.
For 20 years, the front page of the internet for "I need a fencer in Indooroopilly" was a list of ten blue links. You ranked, you got the click, you got the call. That model is being replaced by an assistant that reads ten pages on your behalf, picks one, and ideally acts on it. If you are not findable by the assistant, you do not exist for that searcher.
Call-driven local businesses are partly insulated. People still pick up the phone. AI Overviews citing your business still drives a call. Reviews still matter. The collapse will not happen overnight. But the direction is settled and the speed has surprised everyone who tried to predict it. The smart move is to be ready early.
Being agent-native is the version of "being on Google" for the next decade. Same fundamental work, finding you when someone needs your service, except the someone is now an assistant doing the work on behalf of the person. If your competitor is reachable by Claude and you are not, the assistant picks the competitor and never mentions you. There is no second page of results in an agent conversation. There is one answer.
The defensible version of this is not a chat widget on your homepage. It is a real agent surface with real capability. Tools that do things. A live integration to a real booking flow. A human or AI receptionist on the other end who answers within minutes. That is what the network does today and what almost nobody else in local services has built.
What's inside an MCP call
Every site on the network exposes the same nine tools. They are deliberately scoped to "the things an agent needs to operate on behalf of a homeowner", not "the entire CMS". Here is the surface in plain terms.
Returns the business operating in this suburb. Trading name, suburb served, trade category, ABN, public contact details, plus a short description of the kind of work they do. This is the first tool any agent calls, so it knows who it is talking to.
Returns the specific services the provider offers. For a fencer that might be timber fencing, Colorbond fencing, gates, pool fencing, and repairs. For a concreter it might be driveways, paths, slabs, exposed aggregate, and resurfacing. Each item is structured so the agent can match a user's request to a real service.
Returns the trading hours for the week, including any one-off closures. Lets the agent answer "are they open right now" without guessing, and lets it schedule a callback inside business hours.
Returns the live expected response time for a callback right now, in minutes. Inside business hours, this is usually under 60. Out of hours, the agent gets a clear answer that the callback lands the next morning. This is the kind of thing an assistant cannot fake.
Returns an honest indicative range for a given service. Not a quote, a band. A concreter's driveway band, a painter's per-room band, a stump grinder's per-stump band. Calibrated so the homeowner can self-screen before booking a callback, and the partner is not wasting time on jobs that are out of scope.
Given a preferred window (this week, next week, a specific day) returns whether the partner can take a new job in that window. Lets the agent qualify timing before it bothers writing up a request.
Returns the partner's licences, insurances, registrations, and accreditation. ABN, contractor licence number, public liability cover, any trade-specific tickets. This is the tool an assistant will call if the homeowner asks "are they licensed".
The active one. Takes a structured payload (service, scope, suburb, contact details, preferred window) and writes it directly to our prospects table, the same table that inbound phone calls land in. The signed partner gets called within the hour during business hours, with the full structured context from the agent conversation.
The lighter version. The homeowner does not want a quote yet, they just want the partner to call them back at a specific time. Books the slot, confirms the channel, and queues the callback in the same operational system that drives the rest of the partner's day.
Under the hood it is the standard MCP protocol, JSON-RPC over streamable HTTP, anonymous on v1. Nothing exotic. Any agent client that ships MCP support can connect without an API key, list the tools, and call them. We are deliberately conservative on what we expose, because an agent surface for a real business is not a playground. Each tool maps to something a partner has signed up to deliver.
What we're betting on
The bet is the same one we have been making since we started the network.
Inside 18 months, a meaningful share of "find me a tradie" intent will run through an AI assistant rather than a search results page. Not all of it. A lot of it. The assistant will not show ten blue links and let the user pick. It will pick one, on the user's behalf, based on signals it can read. Reviews, schema, AI Overview citations, response time, and increasingly, whether the business has an agent endpoint the assistant can actually use.
The moat is network breadth (do you have a site for the trade and suburb the user is searching), tool depth (can the assistant do useful things on your endpoint), and the quality of the person or system on the other end (does the request turn into a callback inside an hour or a voicemail at 5pm). We are building all three deliberately, and we are well ahead on the third because the network has run on AI phone answering since day one.
The fourth piece coming is signed partner status with the assistant vendors themselves. Anthropic, OpenAI, Perplexity, Apple. None of those exist yet for local trades in Australia, and we are not claiming any today. We are claiming that when they ship, the networks with a working agent surface across dozens of suburbs and trades are the ones the vendors partner with first.
Want one of these sites for your trade?
If you operate a trade business in Brisbane and your suburb is not on the network yet, three options.
- Call us. 0480 846 576. Honest conversation, no contract, no pressure. We will tell you whether your trade and suburb is open and what the first 60 days would look like.
- Browse the live network. The network page shows every site that is already live, the trade and suburb it serves, and which ones are still looking for a signed partner.
- Talk to your AI. If you already use Claude or ChatGPT, point it at one of the live endpoints (say, mcp.fencingindooroopilly.com.au) and ask it what it can do. That is the experience your customers will have in 12 months. The earlier you build for it, the more obvious the lead.
One site, one signed partner, one suburb. Reachable by phone, by web form, and by an AI assistant on the user's behalf. That is the network. We are signing partners now.
Quick answers
Want to be the signed partner for your trade and suburb?
One site. One agent endpoint. One signed partner per area. We are signing now across Brisbane.
Call 0480 846 576