Developers & API

The Care to Change API is free to use and there is nothing to sign up for. There are no API keys, no accounts and no sandbox, because there is nothing private to protect: every endpoint below serves information that is already public on this website. Requests are anonymous and read-only.

Machine-readable files

• OpenAPI specification — /openapi.json
• MCP server manifest — /.well-known/mcp
• Site index for language models — /llms.txt, and the same content as Markdown at /llms.md
• Sitemap — /sitemap_index.xml

Every page URL on this site also answers to Accept: text/markdown, returning the page as Markdown instead of HTML.

The REST API

The Care to Change API root is https://www.caretochange.com.au/wp-json. It is the standard WordPress REST API, so any existing client library works. Responses are JSON, and so are errors.

• GET /wp/v2/pages — published pages, including every service page
• GET /wp/v2/posts — articles and updates
• GET /wp/v2/accommodation — Supported Independent Living homes and vacancies
• GET /wp/v2/job-listing — open roles
• GET /wp/v2/search?search=term — search across published content

Only GET is public. Writing requires authentication and returns 401.

Errors

Every Care to Change API error is JSON with a stable machine-readable code, a human-readable message and an HTTP status:

{"code":"rest_no_route","message":"No route was found matching the URL and request method.","data":{"status":404}}

Rate limits

Anonymous requests are limited to 240 requests per 60 seconds per IP address. Every response carries the standard headers, so a client can pace itself without guessing:

• RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset
• RateLimit-Policy — for example 240;w=60
• Retry-After on a 429

Please honour these. If you need a higher allowance, email info@caretochange.com.au and tell us what you are building.

Versioning and deprecation

The API is versioned in the URL path (wp/v2), and every response carries an API-Version header. Nothing is currently deprecated, which the Deprecation: false header states explicitly.

If an endpoint is ever retired we will signal it in advance with the standard Deprecation and Sunset headers, note it on this page, and allow at least 90 days before removal.

MCP server

An MCP (Model Context Protocol) server lets an AI assistant query us directly rather than scraping pages. Point a client at https://www.caretochange.com.au/wp-json/caretochange/v1/mcp using Streamable HTTP transport; the manifest is at /.well-known/mcp.

Five read-only tools are available: search_content, list_services, list_sil_vacancies, get_faqs and get_organisation.

The endpoint speaks JSON-RPC 2.0 over POST. Opening it in a browser sends a GET, which returns a short pointer describing the transport, the manifest and the tool list — so you can confirm it is alive without wiring up a client first.

WordPress Abilities

The same five tools are also registered with the WordPress Abilities API, so you can call them through core’s own endpoints instead of our MCP server if that suits your stack better. They are read-only, so core serves them over GET:

GET /wp-json/wp-abilities/v1/abilities/caretochange/list-services/run
GET /wp-json/wp-abilities/v1/abilities/caretochange/search-content/run?input[query]=support%20coordination

Ability names use dashes where the MCP tool names use underscores, so search_content is caretochange/search-content. Note that listing abilities requires a logged-in user — that is a WordPress core restriction, not ours — so the MCP server above remains the anonymous route to the same data.