Machine-readable

For agents and other programs

Our thesis holds that a website should describe what its organization offers in a form software can read: the outcomes it supports, the inputs it accepts, its constraints, and what authorizes a request. This site does that for itself.

The files

Four files, one description.

/.well-known/c2consultants.json: What we offer, what each offering needs to start, its constraints, its prices, and the exact fields a request takes.
/llms.txt: A short summary of the company, the products and the pages.
/llms-full.txt: The product facts, the pilot, our method, and the full text of every published paper.
/sitemap-index.xml: Every public page.

Use the API

Read what we offer. Send a request.

Reading is open. A request authorizes nothing. An order is an order request that a person confirms, invoices and starts; nothing is charged by the API. Every request and order is acknowledged by email with its id.

GET /api/v1/catalog: What we offer, with prices, constraints and which offerings take an order request.
POST /api/v1/requests: A question, follow-up, details, demo, pilot scoping or partnership request.
POST /api/v1/orders: An order request for a C2Empowered pilot or an IntentSharp licence.
GET /api/v1/openapi.json: The OpenAPI 3.1 description of every endpoint, with schemas and examples.

curl -X POST https://www.c2consultants.net/api/v1/requests \
  -H "Content-Type: application/json" \
  -d '{"kind":"demo","offeringId":"c2empowered-pilot",
       "contact":{"name":"Ada Example","email":"ada@example.com"},
       "message":"We would like to see a live build on one of our processes."}'

curl -X POST https://www.c2consultants.net/api/v1/orders \
  -H "Content-Type: application/json" \
  -d '{"offeringId":"c2empowered-pilot","acceptsTerms":true,
       "contact":{"name":"Ada Example","email":"ada@example.com"}}'

One limit: there is no database. The acknowledgment email is the record, so quote its id when you follow up. The full contract is in the OpenAPI document.

The limit

A person answers every request.

A program can send a request to the API above, or to POST /api/contact with the fields the manifest lists. Nothing is charged, booked or started by software: an order request is confirmed by a person. A person replies within one business day, and any work is agreed in writing.

Read the chapter: Websites other software can use Talk to us