2 APIs across 1 product group.
| I want to... | Use | Why |
|---|---|---|
| Chat, text completions, embeddings, image generation, or audio transcription and speech | AI/ML API | The aiml-api spec exposes the OpenAI-style chat, completions, embeddings, images, and audio endpoints plus model listing. |
| Text extraction from document images or vision-feature analysis of images | AIMLAPI | The aimlapi spec exposes the focused /ocr and /vision endpoints for document and image understanding. |
| Turning an image into a text description | AIMLAPI | Use /vision on the aimlapi spec for image analysis; the aiml-api spec generates images from text rather than describing them. |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AI/ML API APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Faimlapi.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faimlapi.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Once connected, ask your agent something like: “run inference and document analysis with AI/ML API”.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AI/ML API by hand means handling its account credential, matching each request to the right chat, embedding, image, audio, OCR, or vision endpoint across two specs, and writing your own retry logic. With Jentic you install Jentic One once, add AI/ML API from the Jentic directory, store the credential once, and your agent calls any endpoint.
Permission scoping
AI/ML API carries its model and inputs in the request body rather than in separate scopes, so you scope the agent by operation in your own self-hosted Jentic One instance. Your rules decide which endpoints and credentials it may use, for example allowing only /v1/chat/completions and /ocr while leaving out image, audio, and vision endpoints it does not need.
Credential isolation
Specific to using AI/ML API APIs through Jentic.
What can I build across AI/ML API's specs?
The broader spec runs chat and text completions, embeddings, image generation, audio transcription, and text-to-speech, and lists supported models. The focused spec adds document OCR and vision-feature image analysis. Together they cover text, image, and audio inference plus document and image understanding under one account.
Do the two specs share one account and credential?
Yes. Both call the same api.aimlapi.com base URL and use one AI/ML API account credential. The broader spec documents it as an HTTP Bearer token and the OCR and vision spec as an apiKey scheme, but both resolve to the same account.
Which spec should I use for a given task?
Use the aiml-api spec for chat, completions, embeddings, image generation, and audio. Use the aimlapi spec for extracting text from document images with OCR and for analysing images with vision features. Many workflows chain both, such as running OCR then answering questions with a chat completion.
Can I switch models without changing my integration?
Yes on the broader spec. Call GET /v1/models to discover which model identifiers are currently supported, then pass the chosen model id to the chat, completions, or embeddings endpoints. Switching backends is a config change rather than a code rewrite.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can generate chat and text completions, create embeddings, produce images, transcribe audio, synthesize speech, and list available models, plus run OCR on documents and analyse images with vision features, all through one AI/ML API account.
AI/ML API puts multi-model inference and focused document and vision endpoints behind a single OpenAI-style REST surface, so an agent can chat, embed, generate images, handle audio, run OCR, and analyse images without adopting separate providers. Switching between supported models is a config change rather than a rewrite.
Use for: Running inference against AI/ML API: chat, text completions, embeddings, image generation, audio transcription and speech, model listing, plus document OCR and vision-feature image analysis.
Not supported: model fine-tuning, model training, hosted vector storage, real-time audio streaming, custom model hosting
Credentials: Both specs call the same api.aimlapi.com base URL with a single account credential, though the broader spec documents it as an HTTP Bearer token and the OCR and vision spec as an apiKey scheme.
All 2 AI/ML API OpenAPI specs are Jentic-generated and indexed by Jentic, kept validated and agent-ready.
AI/ML API (aimlapi.com) is a unified inference platform reached through one Bearer-authenticated REST surface modelled on OpenAI conventions. Its broader spec runs chat completions, text completions, embeddings, image generation, audio transcription, and text-to-speech, and lists supported models so a client can switch backends without changing integration code. A companion spec adds two focused endpoints for document OCR and vision-feature image analysis. Jentic publishes and validates the only available OpenAPI specifications for both, keeping them agent-ready.
Each workflow spans multiple AI/ML API APIs. Jentic routes each operation to the right API automatically.
Scanned document to summarised answer
Extract text from an uploaded document with the OCR endpoint, embed the result for retrieval, then generate a chat answer grounded in the extracted content. One account covers OCR, embeddings, and chat.
POST the document image to /ocr on the aimlapi spec, POST the returned text to /v1/embeddings, then POST /v1/chat/completions with the retrieved context to answer the user's question
AIMLAPI + AI/ML API
Image triage with captioning and speech reply
Analyse an uploaded image for vision features, generate a natural-language caption from those features with a chat completion, then synthesize a spoken version of the caption. The image, text, and audio steps run against the same vendor.
POST the image to /vision on the aimlapi spec, send the returned features to /v1/chat/completions to write a caption, then POST that caption to /v1/audio/speech
AIMLAPI + AI/ML API
Mixed-input intake router
An agent receives a mix of scanned documents and everyday photos, routes documents to OCR and photos to vision, then normalises both into structured records using a chat completion. Routing and normalisation share one credential.
Classify each upload, POST documents to /ocr and photos to /vision on the aimlapi spec, then POST the combined output to /v1/chat/completions to produce a normalised record
AIMLAPI + AI/ML API
Your AI/ML API credential is stored once, encrypted, by your own Jentic One instance and injected at execution time for the operations you permit. It never enters the agent's prompt, logs, or context, even though both specs share the same account.
Intent-based discovery
Agents search the Jentic directory by intent such as 'generate a chat completion' or 'extract text from a document image', and Jentic returns the matching AI/ML API operation with its input schema so the agent calls the right endpoint across either spec without browsing the reference docs.
Are these official specs?
AI/ML API does not publish its own OpenAPI specifications. Jentic generates and maintains both specs so agents and developers can call the endpoints through structured tooling. Each is validated against the live API and kept up to date.
Are there published rate limits?
Neither spec declares explicit rate limits. Treat HTTP 429 responses as a signal to back off, and expect the practical limit to be the provider's per-key quota across both the inference and the OCR and vision endpoints.
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.