Understand the operating layer.
In plain wordsYou send us messy signals. We turn them into tidy records your team can act on. This page explains the parts and the words we use.
Croutons structures AI activity, visibility signals, workflows, claims, sources and evidence into reusable records your team can route, govern, measure and trust.
The primitives behind Croutons.
Crouton Unit
A structured record created from one messy AI, business or website signal. It carries claim, source, confidence, route, policy, action and impact.
AI Layer Diagnosis
A first-pass map of inference load, routing waste, governance gaps and operational risk, built from sample data.
AI Visibility Layer
A machine-readable map of crawl paths, schema, feeds, evidence and answer-ready data that helps search engines and AI assistants interpret a business.
Evidence Brief
A reusable proof object that connects a claim to source-backed evidence.
Anatomy of a Crouton Unit
| Field | Answers |
|---|---|
| Claim | What the AI said |
| Source | Where it came from |
| Confidence | How certain it is |
| Route | Where it should go |
| Policy | What rules apply |
| Action | What can be approved |
| Impact | Cost, risk and value |
Send messy signals.
- URLs and sitemaps
- Schema
- Logs and traces
- AI outputs
- Workflows and policies
- Claims and screenshots
- Exports, feeds and documents
Get usable records.
- AI visibility score and crawl readiness
- Schema graph
- Evidence Briefs
- Risk map and workflow gaps
- Citation gaps
- Implementation tickets
- Machine-readable files and structured records
How the first pass works.
- Send signalssamples only
- We structureCrouton Units
- Breaks mappedwaste, risk, gaps
- You get actionsscores & tickets
After the first pass, teams choose one of three paths: diagnosis only, a managed layer or integrated infrastructure.
Files this site publishes for machines.
These are the same kinds of files Croutons helps clients structure, validate or generate from verified business data.
/llms.txt
Plain-text guide to this site for language models
/llms-full.txt
Full page-by-page context for language models
/sitemap.xml
Every public URL with last-modified dates
/robots.txt
Crawl rules, open to search and AI crawlers
/api/sessions
Live sessions, prices and booking rules (JSON)
/openapi.json
OpenAPI 3.1 description of the booking API
/.well-known/api-catalog
RFC 9727 API catalog (linkset)
/.well-known/mcp.json
MCP server descriptor
/context-map.json
Page types, entities and topics per URL
/semantic-index.json
Entities, terms and their relationships
The words we use, defined once.
- AI inference management
- AI inference management is the process of measuring, routing, governing, and optimizing the model calls used by AI applications, agents, and automated workflows.
- Inference
- One run of an AI model: the model reads an input and produces an output. Each run uses compute and usually costs money per token.
- Crouton Unit
- A structured record created from one messy AI, business or website signal. It carries claim, source, confidence, route, policy, action and impact.
- AI Layer Diagnosis
- A first-pass map of inference load, routing waste, governance gaps and operational risk, built from sample data.
- AI Visibility Layer
- A machine-readable map of crawl paths, schema, feeds, evidence and answer-ready data that helps search engines and AI assistants interpret a business.
- Evidence Brief
- A reusable proof object that connects a claim to source-backed evidence.
- Model routing
- Rules that decide which AI model handles each request based on task class, risk, quality, latency and cost.
- Agent fan-out
- The spread of one user task into many model calls, tool calls, retrievals and retries inside an AI agent system.
- Generative engine optimization (GEO)
- The practice of making content visible and usable to generative AI engines through retrieval, interpretation and citation, not only traditional search rankings.
- WebMCP
- A browser proposal that lets a web page register tools an AI agent can call directly, such as checking availability or booking, instead of scraping the page.
Common implementation questions
Do we need production integration first?
No. The first diagnosis can run from sample URLs, logs, schema, workflows, docs or exports.
Is Croutons an SEO tool?
Not only. It supports AI visibility, evidence, AI operations, workflow risk and machine-readable business structure.
Does this replace our schema?
No. It helps design, audit, connect and operationalize schema as part of a larger machine-readable layer.
Start with a free 30-minute call.
Bring one question. Leave with the top three things to fix and a written follow-up within two business days.