Skip to main content
Give your agent a documentation URL and ask it to fetch the page. You do not need to copy the page into the chat. Reading public documentation requires no API key. Calling the ESA API still requires your provider key.

​
Discover pages

Start at llms.txt. It links to every supported API endpoint and guide. Use https://esa.acreblitz.com/api/v2 for API requests. Documentation pages live under /v2/.

​
Read a page directly

Append .md to a page URL to fetch its Markdown, including parameters and examples:
The hosted site also supports requesting Markdown with an Accept header:
For full context, follow the All API documentation link in llms.txt. That link includes a version parameter for llms-full.txt so you receive the current release even when a CDN retains an older copy of the unversioned URL. It covers the supported V2 API and expands shared input documentation so agents can read required fields without following source-code imports. Prefer individual pages when the agent has a limited context window.

​
Example agent task

Fetch https://docs.acreblitz.com/llms.txt and use only the V2 documentation. Read the bulk submission, job status, results, and error pages directly. Build a request with shared products and crops, then override products and crops for one field. Explain the effective values for each field and handle both HTTP errors and failed items. Read the URLs yourself; do not ask me to paste their contents.
An agent needs a web-fetch or browsing tool to use these links. If its tool cannot fetch a page, it should report that limitation and try the Markdown URL or complete-content file. It should not guess endpoint behavior from an unread page.