Arlite Energy developer resources: API and MCP server

Arlite Energy publishes its public website content as a read-only JSON API and a Model Context Protocol (MCP) server, so assistants and developers can read our services, support answers and business details without scraping pages. Everything returned is the same copy that is on this website. There is no account, API key or sign-up.

MCP server

The Arlite Energy MCP server speaks JSON-RPC 2.0 over Streamable HTTP and is stateless: there are no sessions and no server-sent event stream.

• Endpoint: https://arlite.co/wp-json/arlite/v1/mcp (POST). A GET request returns a short JSON description of the server.
• Server card: https://arlite.co/wp-json/arlite/v1/mcp/server-card (discovery metadata).
• Protocol versions: 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26.
• Authentication: none.

Tools, all read-only:

• get_business_info: legal name, ABN, address, phone, email, licences and service area. Start here.
• list_services and get_service: the services Arlite offers, and one service in full with its FAQs.
• search_site: search services, pages and support articles.
• list_support_articles and get_support_article: the Support Centre, with plain-text answers.
• get_faq: every frequently asked question on the site, optionally filtered by topic.

Resources: arlite://business, arlite://services, arlite://support, arlite://faq, and the templates arlite://services/{path} and arlite://support/{slug}.

Connect from Claude Code with claude mcp add --transport http arlite-website https://arlite.co/wp-json/arlite/v1/mcp. In claude.ai, add a custom connector with that URL and no authentication. To check the server without a client, POST a tools/list JSON-RPC request to the endpoint.

JSON API

The base URL is https://arlite.co/wp-json/arlite/v1/. Every endpoint is a GET that returns JSON, and the index at the base URL lists them all.

• /business: business facts.
• /services and /services/{slug-path}: all services, and one service with its full text and FAQs, for example /services/solar-power/solar-batteries.
• /pages and /pages/{slug}: information pages such as For Home, For Work, Finance Options and Contact.
• /support, /support/categories, /support/{category} and /support/{category}/{slug}: the Support Centre. /support/search?q= searches articles only.
• /search?q=&type=: search services, pages and support articles (type is all, service, page or support).
• /faq?topic=: every FAQ question and answer.

For example, curl -s https://arlite.co/wp-json/arlite/v1/business returns the business facts.

Limits and good manners

• Responses carry an ETag and are cacheable for a few minutes; please cache and send If-None-Match.
• Each IP address can make 120 requests a minute. Beyond that the API answers 429 with a Retry-After header.
• The MCP endpoint only accepts browser requests from arlite.co. Clients that are not browsers are not affected.
• Please attribute Arlite Energy when you use the content.

What it does not do

The API and MCP server cannot book work, quote prices or give timeframes. Arlite quotes after an in-home, no cost consult. To arrange one, use the contact page, call (07) 3062 9299, or email info@arlite.co.

Other machine-readable files

• openapi.json: OpenAPI 3.1 description of the JSON API.
• /.well-known/api-catalog (RFC 9727), MCP server card, ard.json and the agent skills index.
• llms.txt: an index of the site for language models, including when to use Arlite Energy and how to engage. Section indexes: services, support, contact.
• llms-full.txt: the index followed by the full text of services and support articles.
• XML sitemap.
• Any page on this site returns Markdown when requested with the header Accept: text/markdown, or by adding .md to its address (for example https://arlite.co/about.md).
• Add ?mode=agent to the home page address for a compact JSON summary of the business and these endpoints.

Browser agents that support WebMCP can also use read-only tools registered on every page of this site.