SCALOGY PUBLIC API
Three endpoints, no API key. Everything is served from https://scalogy.com as JSON. The machine-readable description is an OpenAPI 3.1 document at /openapi.json, and the catalog for automated discovery (RFC 9727) is at /.well-known/api-catalog.
POST /api/contact
Submit a contact request. It becomes a lead and the Scalogy team replies by email, usually within one business day. Only name and email are required. Optional fields: businessName, industry,timeWaster (the problem to automate, in your words), source, and utm_source,utm_medium, utm_campaign.
curl -X POST https://scalogy.com/api/contact \
-H "Content-Type: application/json" \
-d '{"name":"Jordan Rivera","email":"[email protected]","businessName":"Rivera Plumbing","industry":"Plumbing","timeWaster":"Missed calls after hours","source":"api"}'
200 {"ok":true,"id":"3f1c8e6a-2b7d-4c1e-9d3f-5a6b7c8d9e0f"}
400 {"error":"Name and email are required"}POST /api/chat
Ask the site assistant about Scalogy's AI agents, pricing or process. Send the conversation so far as messages(roles user and assistant, oldest first) and receive the next reply. An empty array returns the greeting.
curl -X POST https://scalogy.com/api/chat \
-H "Content-Type: application/json" \
-d '{"messages":[{"role":"user","content":"What does the lead response agent do?"}]}'
200 {"reply":"It answers every new inquiry within a minute, by text or email, and books the call."}
502 {"error":"AI service error"}GET /api/health
Returns 200 when the site and its API are serving requests. Use it as the status link for monitoring.
curl https://scalogy.com/api/health
200 {"status":"ok","service":"scalogy.com","time":"2026-09-22T17:00:00.000Z"}DISCOVERY
Every HTML page carries a Link header with rel="api-catalog", and the catalog links to the spec (service-desc), this page (service-doc) and the health endpoint (status). The site also publishes /llms.txt and returns Markdown for any page requested with Accept: text/markdown.
Questions or a use case that needs more than this? Get in touch.