ChatHome · Authentication Profile

ChatHome Authentication

Authentication

ChatHome secures its APIs with none, apiKey, http, and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyReal EstateProperty SearchLuxembourgHousingProperty ValuationAI AgentsMCPA2A
Methods: none, apiKey, http, oauth2 Schemes: 3 OAuth flows: API key in: header

Security Schemes

apiKey apiKey
· in: header (X-API-Key)
bearer http
scheme: bearer
oauth2-pkce oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-03'
method: searched
source: https://chathome.lu/llms.txt
docs: https://chathome.lu/en/developers
summary:
  types:
  - none
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  anonymous_surface: The public read API (openapi/chathome-lu-openapi.yml) declares no security; its description states "Every endpoint in this document answers WITHOUT an account, an API key, or an OAuth
    token." Anonymous MCP discovery and public discovery tools are also callable without credentials.
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter: X-API-Key
  description: 'llms.txt: "Generate a key at: https://chathome.lu/dashboard/agent-access / Pass as header: X-API-Key: cht_<key>". The developer portal shows a key format beginning ch_ ("ch_a1b2c3d4...")
    and states "Keys are shown once at creation".'
  key_prefixes_documented:
  - cht_ (llms.txt)
  - ch_ (developer portal example)
  sources:
  - openapi/chathome-lu-agent-api-openapi.yml
  - https://chathome.lu/llms.txt
  - https://chathome.lu/en/developers
- name: bearer
  type: http
  scheme: bearer
  description: Use the ChatHome MCP OAuth token, bound to /api/mcp, with market:read scope.
  sources:
  - openapi/chathome-lu-agent-api-openapi.yml
- name: oauth2-pkce
  type: oauth2
  flow: authorization_code
  pkce: S256
  public_clients: true
  description: 'llms.txt: "OAuth 2.1 with PKCE (recommended). This server uses PUBLIC OAuth clients — no client secret is required." Documented client IDs: claude-desktop, cursor, chatgpt. "OAuth tokens
    expire after 1 hour (clients auto-refresh)".'
  metadata_url: https://chathome.lu/.well-known/oauth-authorization-server
  scopes:
  - listings:read
  - market:read
  - inquiries:write
  - inquiries:read
  - documents:write
  token_lifetime: 1 hour
  sources:
  - https://chathome.lu/llms.txt
  - https://chathome.lu/.well-known/oauth-authorization-server (GET 200, grant_types_supported [authorization_code], code_challenge_methods_supported [S256])
unauthenticated_response: Protected MCP tool calls "answer 401 with a WWW-Authenticate header pointing at the OAuth metadata" (llms.txt).
related_docs:
- https://chathome.lu/llms.txt
- https://chathome.lu/.well-known/oauth-authorization-server

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/chathome-lu-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.