AXO / AEO Machine Web Glossary
π A complete reference of standardized web, API, and agent-related terms —with plain-English explanations, context, and relevance to Agent Experience Optimization (AXO) and Answer Engine Optimization (AEO).
πΉ A
AEO (Answer Engine Optimization)
Optimization practice so that AI answer engines (like Google AI Overviews, ChatGPT, Perplexity, or Bing Copilot) can understand and use your data directly.
API (Application Programming Interface)
A structured way for systems to communicate using HTTP and JSON. Core to web automation and agent interaction.
API Semantics
Defines meaning, safety, and structure of API endpoints. Ensures agents can interpret APIs correctly.
AXO (Agent Experience Optimization)
Optimization for AI agents and autonomous systems to discover, interpret, and act on your site and APIs.
πΉ B
Base URL
The main domain or root of a website or API, e.g.,
https://faunapc.com.
πΉ C
Caching
Temporary storage of resources for speed and efficiency. Helps performance and AXO scoring.
Content-Language
HTTP header declaring the main language of content.
Crawl Accessibility
How easily crawlers and AI agents can access and index site data.
πΉ D
Discovery
Mechanisms allowing agents to find structured data, APIs, and policies (e.g.,
robots.txt,.well-known/agent.json).
πΉ E
Error Schema
Standard JSON format for API error responses, usually containing
code,message, andremediation.
ETag
HTTP header identifying a version of a resource to optimize caching and change detection.
πΉ F
FAQPage / HowTo
JSON-LD schema types enabling AI to extract direct answers from content.
πΉ H
hreflang
HTML tag specifying alternate language versions of a page.
HTTP Methods
Web request verbs defining API behavior: GET, POST, PUT, DELETE, PATCH.
πΉ I
Idempotent
Operation that produces the same result even when repeated multiple times (e.g.,
DELETE /user/123).
i18n (Internationalization)
Preparing systems to support multiple languages and regions.
πΉ J
JSON (JavaScript Object Notation)
Lightweight, structured data format used for APIs.
JSON-LD (JSON for Linked Data)
W3C standard embedding semantic data into web pages for AI understanding.
πΉ K
KB (Knowledge Base)
Machine-readable repository (e.g.,
/api/kb.json) of facts, FAQs, and policies.
πΉ L
Link Header
HTTP relation headers (e.g.,
rel="openapi") that point agents to structured resources.
πΉ M
Machine Knowledge
Structured data consumable directly by AI agents or LLMs.
πΉ O
OpenAPI Specification (OAS)
Standard for describing REST APIs in JSON or YAML format; previously known as Swagger Specification.
πΉ P
Performance & Caching
Category measuring API speed, latency, and cache efficiency.
Policies
Structured documents (e.g.,
/api/refunds.json) exposing legal and business rules.
πΉ R
robots.txt
File defining which site areas are accessible to crawlers (RFC 9309).
Retry Safety
Ensures repeated API calls do not cause duplicate actions.
πΉ S
Schema.org
Vocabulary for structured data markup used by search and answer engines.
security.txt
File in
/.well-known/listing security contact information (RFC 9116).
Swagger
Toolset for creating and visualizing OpenAPI specifications.
πΉ T
TTI (Time to Initial Results)
Metric for how quickly a system returns first usable output.
πΉ U
User-Agent
HTTP header identifying the requesting client (browser, bot, or agent).
πΉ V
Verbose
Means "detailed" or "wordy." In computing, verbose mode shows extended logs.
πΉ W
Well-Known Directory (/.well-known/)
Standardized folder for machine-readable metadata like
security.txtandagent.json(RFC 8615).
YAML (YAML Ain't Markup Language)
Human-friendly data format for configuration and API specs (commonly used in OpenAPI files).
π‘ Summary Table — Machine Data Standards Overview
| Layer | Example File | Standard | Purpose |
|---|---|---|---|
| Discovery | robots.txt, sitemap.xml |
RFC 9309 | Bot & agent navigation |
| Machine Knowledge | /api/kb.json |
AXO Convention | Factual data for AI |
| Policies | /api/refunds.json |
AXO Convention | Legal and operational context |
| Structured Data | JSON-LD | W3C / Schema.org | Answer engine visibility |
| APIs | /api/openapi.yaml |
OpenAPI 3.1 | Machine-readable API docs |
| Metadata | /.well-known/agent.json |
RFC 8615 (pattern) | Agent discovery |
| Error Schema | JSON with code, message, remediation |
AXO Convention | Predictable error handling |
| i18n | Content-Language, hreflang |
W3C | Multilingual support |
Comments