API
Common Sense Systems API
A machine-readable interface for the business. Human-friendly, under development, and documented at the service edge.
What this page is for
This is the human entry point for the Common Sense Systems API. The service is still in development, but the shape is already useful: a business-facing API for services, insights, availability, and company facts.
If you are evaluating the API, start with the OpenAPI spec. If you are just trying to understand what is there, use the endpoint browser below.
Quick start
The health endpoint is the fastest way to confirm the API is reachable.
curl https://api.common-sense.com/v1/health
{
"status": "healthy",
"timestamp": "2026-06-03T15:00:00Z",
"version": "1.0.0"
} Browse the surface
Grouped by the kinds of questions the API answers.
Discovery
Start here if you want to know whether the service is alive and what it can do.
- GET
/healthService status and timestamp.
- GET
/capabilitiesCategories, counts, and supported operations.
- GET
/businessCompany profile and public facts.
Services
Structured service catalog data for the consulting offer.
- GET
/servicesList the current services.
- GET
/services/{serviceId}Fetch one service and its details.
- GET
/services/{serviceId}/testimonialsClient quotes tied to a service.
- GET
/services/{serviceId}/faqCommon questions and answers for a service.
Insights
Content discovery and search for the public knowledge base.
- GET
/insightsBrowse recent insight entries.
- GET
/insights/{insightId}Fetch one insight in detail.
- GET
/insights/searchSearch insight content by topic or keyword.
- GET
/knowledge/toc-principlesTOC principle reference for integrations and tools.
Operations
Inquiry capture and scheduling helpers for real conversations.
- GET
/availabilityCurrent availability and response time.
- POST
/availability/bookSchedule a consultation request.
- POST
/inquiriesSubmit an inquiry and track it.
For humans
Use the spec first, then inspect the response shape.
The page is deliberately plain: it should help a person orient quickly, and it should not pretend the API is more finished than it is. If you need to integrate it, the OpenAPI document is the source of truth.
Need help integrating the API?
Start with the OpenAPI spec. If you need a conversation about fit, integration scope, or the data model, use the contact page.