What output formats does the HTML renderer support?

POST /html-renderer accepts HTML and returns a rendered image or PDF depending on the output parameter you set in the request body. It is stateless - each call renders from the supplied HTML rather than persisting a document.

Can I generate any barcode format with ExoAPI?

POST /barcode-generator generates barcodes from a value and format pair. The supported formats are listed in the operation's request schema; common ones such as code128 and qr are supported. The endpoint returns the generated image directly.

How accurate is the reverse-geocoding endpoint?

GET /reverse-geocoding returns the address corresponding to a latitude and longitude pair. Accuracy depends on the underlying geocoding source ExoAPI uses; for high-precision use cases compare against a dedicated geocoder such as Google Maps or HERE.

How do I render an HTML invoice to PDF through Jentic?

Run pip install jentic, then search 'render html to pdf', load the POST /html-renderer operation, and execute it with html=<your template> and output=pdf. Jentic injects the bearer token at execution time and returns the rendered PDF bytes.

What are the rate limits for ExoAPI?

The OpenAPI spec does not declare numeric rate limits. ExoAPI applies plan-based limits on its dashboard; check 429 responses for Retry-After and consult your account tier for current quotas.

Can I limit what my agent is allowed to do with the ExoAPI?

Yes. Because Jentic One is self-hosted, your own rules decide which ExoAPI operations and credentials the agent can use, so you can scope it to just the utilities it needs, such as GET /reverse-geocoding or GET /unit-converter. Since every ExoAPI call is stateless and takes its input in the request body or query, the operations you leave out, like POST /barcode-generator or POST /html-renderer, stay unavailable to the agent unless you add them. Your bearer token is held by your own instance and injected only for the operations you permit.