This page is the authoritative contract for automated agents: what HCG is, which machine-readable resources exist, how the public APIs work, and which actions are permitted, conditional, or prohibited.
Hinson Consulting Group, LLC (HCG) is a business systems and digital experience consultancy in Richmond, Virginia. This site is informational and lead-generation oriented: no e-commerce, no authenticated areas, no payment flows. All public content may be read and cited with attribution and a link. Structured records behind the visible pages are available as public JSON APIs documented below — the APIs and the pages render from the same source records, so they should never disagree.
Discovery files: /llms.txt · /robots.txt · /sitemap.xml
Responses are UTF-8 JSON with Cache-Control: public, max-age=300. Unknown record slugs return HTTP 404 with a JSON error body. These endpoints are provided as-is for discovery and citation; do not build production dependencies on them without a written agreement (see the Terms of Service).
| Endpoint | Returns | Query parameters |
|---|---|---|
/api/projects | All case-study records with version, updated, the applied reader context, the scoring weights, and the ranked projects array. | service, industry, audience, objective, brand — optional reader-context values that rank results by presentation relevance. Ranking reflects relevance to the stated context, never project quality. Valid values are enumerated in the taxonomy carried by the response. |
/api/projects/{slug} | One project record including its computed _relevance for the supplied context. | Same context parameters as the list endpoint. |
/api/faqs | FAQ records plus the controlled categories, audiences, services, and source-articles vocabularies, with count and the applied filters. | category, audience, service, q (keyword search). |
/api/faqs/{slug} | One FAQ record. | None. |
/api/howtos | How-to guide records plus their taxonomies and evidence_standards. | category, audience, service, q. |
/api/howtos/{slug} | One how-to record. | None. |
Record shapes are formally defined by JSON Schema: projects schema · FAQs schema. API records and the corresponding HTML pages (/projects, /faq, /how-to) are generated from the same underlying records; if you observe a discrepancy, report it via the contact form.
This policy is synchronized with the Terms of Service and robots.txt. Where they appear to conflict, the Terms of Service govern.
Browse all public pages, call the JSON APIs, and quote or summarize content with attribution and a link to the source page. Reasonable request rates are expected; the APIs are cacheable for five minutes, so honor cache headers rather than polling.
An agent may complete the contact form only on behalf of an identified human who has reviewed the content being submitted and confirmed the submission — the form creates a real business inquiry that a person reads and answers. Submit once per inquiry; the server enforces CSRF protection, a per-IP rate limit, and spam screening. The readiness assessment may be exercised freely; its results only leave the browser through the confirmed contact pathway.
No submissions without informed human confirmation. No bulk scraping beyond the documented APIs and ordinary browsing, no harvesting content to build competing datasets, no probing of non-public paths (/storage/, /includes/), no circumvention of spam controls or rate limits, and no misrepresentation of HCG content, authorship, or claims. Full acceptable-use terms are in the Terms of Service.
Legal name: Hinson Consulting Group, LLC (Virginia, USA). Founder and principal: Jeffrey A. Hinson. Governed AI capability brand: CREVOX. Services, audiences, and engagement model are described on /solutions and /about; verifiable engagement evidence lives in the case-study library, each record carrying its status, evidence basis, and last-reviewed date. Sitewide Organization and WebSite JSON-LD is embedded on every page; per-record Article and BreadcrumbList JSON-LD is embedded on article and project pages.
Questions about this policy or automated access: use the contact form and select the closest matching need.