ExoAPI

Name: ExoAPI API
Brand: ExoAPI
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage Registrybearer5 EndpointsREST

For Agents

Call a small toolbox of developer utilities — generate barcodes, render HTML, reverse-geocode coordinates, run content moderation, and convert units — through a single bearer-authenticated API.

Install Jentic One Beta

Connect the ExoAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ExoAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ExoAPI API.

Generate barcode images for product codes, URLs, or arbitrary strings

Render HTML to a screenshot or PDF using a headless browser

Reverse-geocode latitude and longitude pairs to a postal address

Run text content moderation checks against user-submitted strings

GET STARTED

Start building with ExoAPI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ExoAPI API for, with concrete tasks.

★ On-Demand Barcode and Label Generation

Use POST /barcode-generator to produce barcode images for shipping labels, product tags, or ticketing flows. The endpoint returns a barcode for the supplied value and format without requiring a separate barcode service. Useful for one-off generation inside a workflow that already uses other ExoAPI utilities.

Call POST /barcode-generator with value=ABC12345 and format=code128 and store the returned image.

HTML-to-Image and HTML-to-PDF Rendering

Send HTML to POST /html-renderer and receive back a rendered image or PDF, useful for invoice generation, social-preview cards, or report exports. This avoids running a headless browser inside the agent's environment and keeps the rendering layer behind a single API call.

Call POST /html-renderer with html=<invoice template> and output=pdf, then attach the result to an outbound email.

Lightweight Geocoding and Unit Conversion

Combine GET /reverse-geocoding and GET /unit-converter to enrich data inside agent workflows — for example, turning device GPS coordinates into a city name and converting reported distances into the user's preferred unit before display. Both endpoints are stateless and bearer-authenticated.

Call GET /reverse-geocoding with lat=51.5074&lng=-0.1278 to resolve the address, then GET /unit-converter with value=10&from=km&to=mi to localise distance.

AI Utility Toolkit via Jentic

An AI assistant loads ExoAPI's small operation set through Jentic so it can pick the right utility on demand — barcode, HTML render, geocode, moderate, or convert — without each utility requiring its own integration. The bearer token sits in the Jentic vault and is injected per request.

Through Jentic, search 'render html to pdf', load the POST /html-renderer operation, and execute it with the agent's invoice HTML.

Key Endpoints

5 endpoints — exoapi is a universal utility api that bundles common developer building blocks behind a single bearer-authenticated endpoint surface.

METHOD

PATH

DESCRIPTION

POST

/barcode-generator

Generate a barcode

GET

/content-moderation

Run content moderation on text

POST

/html-renderer

Render HTML to image or PDF

GET

/reverse-geocoding

Reverse-geocode coordinates

GET

/unit-converter

Convert values between units

POST

/barcode-generator

Generate a barcode

GET

/content-moderation

Run content moderation on text

POST

/html-renderer

Render HTML to image or PDF

GET

/reverse-geocoding

Reverse-geocode coordinates

GET

/unit-converter

Convert values between units

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ExoAPI bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped, short-lived credential at execution time and the raw token never enters the agent's prompt, memory, or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'render html to pdf' or 'reverse geocode coordinates') and receive the matching ExoAPI operation with its input schema, so the agent picks the right utility without browsing exoapi.dev docs.

Time to first call

Direct ExoAPI integration: half a day to wire bearer auth and per-utility request shapes. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Positionstack API

Positionstack offers dedicated forward and reverse geocoding beyond ExoAPI's utility endpoint

Pick Positionstack for high-volume geocoding; pick ExoAPI when reverse geocoding is one of several utilities the agent needs.

Alternative

MapQuest API

MapQuest provides full mapping, routing, and geocoding services

Choose MapQuest for routing and mapping in addition to geocoding; choose ExoAPI for ad-hoc reverse-geocode lookups inside a multi-utility workflow.

Complementary

Cloudinary Upload API

Cloudinary handles image and PDF storage and transformation alongside ExoAPI's HTML renderer

Use Cloudinary to store and transform the rendered output from ExoAPI's HTML renderer.

FAQs

Specific to using ExoAPI API through Jentic.

What authentication does the ExoAPI use?

ExoAPI uses HTTP bearer authentication. Pass an Authorization: Bearer <token> header where the token is issued from your ExoAPI dashboard. Through Jentic the token is held in the vault and injected per call so it does not appear in agent prompts or logs.

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.