Why not start improving Business Central APIs definitions for supporting AI?
Business Central APIs lack AI-ready metadata that LLMs need to reliably call functions. The post explains how exposing API descriptions, field types, and OpenAPI specifications would help AI agents automatically discover and use the right endpoints without explicit function calling.
post Stefano Demiliani
"An LLM-ready API is an interface designed for intelligent agents to use reliably and programmatically without the need for human translation."
Key points
- Current Business Central APIs were not designed for AI and lack descriptions that LLMs need to understand field meanings and relationships
- API page Description properties should be exposed in Page Metadata table to pass dynamic API context to language models
- OpenAPI specification support should be offered out of the box for all APIs (standard, custom, third-party) to enable automatic schema discovery
- AI agents require structured metadata including endpoints, parameters, request/response formats, and field explanations to function effectively without hallucinating
Quotes
- “An LLM-ready API is an interface designed for intelligent agents to use reliably and programmatically without the need for human translation.” (Defines the goal: APIs must be naturally understandable to language models without requiring human explanation or workarounds)
- “AI agents require access to comprehensive API schema definitions, including endpoints, parameters, and capabilities, to function effectively.” (Core requirement for AI solutions in Business Central that prevents hallucinated behaviors and incorrect API calls)
- “It’s time to make APIs the cornerstone of your AI strategy also in Business Central.” (Captures the central thesis that API design should prioritize AI consumption as a fundamental business strategy)
AL objects mentioned
As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.
- page “SD Sales Invoice API”
- table “Page Metadata”
- table “Page Table Field”
- table “Page Info and Fields”
Not found in BC28-30: page “SD Sales Invoice API”, table “Page Metadata”, table “Page Table Field”, table “Page Info and Fields”.
Context
- Features: API metadata exposure, OpenAPI specification support, Description property for AI, Dynamic API discovery, Schema validation, Field type documentation
Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.