How Jentic Works
From API assessment to production deployment in four simple steps.
PLATFORM
CAPABILITIES
TOOLS
GET STARTED
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
BOOK A DEMO
Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.
Jentic publishes the only available OpenAPI specification for 3Scribe API, keeping it validated and agent-ready. The 3Scribe API submits audio for automated transcription and exposes the resulting job lifecycle. Authentication is via an APIKey header. The four endpoints let applications create a transcription job from an audio source, list jobs in the account, retrieve a specific job's status and transcript, and delete completed jobs.
Jentic publishes the only available OpenAPI specification for AccurAI API, keeping it validated and agent-ready. AccurAI is an AI-powered document processing service that extracts structured data from uploaded documents — invoices, receipts, forms — and exposes the result through a simple two-endpoint API. Documents are submitted to POST /documents and the structured extraction is retrieved by id from GET /documents/{id}. Authentication is via an Authorization header API key, and the base URL is api.accurai.com.
Jentic publishes the only available OpenAPI specification for Affinda API, keeping it validated and agent-ready. Affinda is a document-AI platform that extracts structured data from resumes, invoices, receipts, IDs, and other document types and supports recruiter-facing resume search, job-description search, and skill-and-occupation taxonomies. Version 3 of the API exposes 140 endpoints covering document upload and parsing, workspaces and document types, validation results, mapping data sources, tags and annotations, webhook subscriptions, and dedicated resume and job-description search engines. Authentication uses a bearer token issued from the Affinda dashboard.
Jentic publishes the only available OpenAPI specification for AgentQL API, keeping it validated and agent-ready. AgentQL extracts structured data from web pages and documents using AgentQL query syntax or natural language prompts. The 0.1.0 spec exposes both versioned (/v1) and unversioned routes for the query-data endpoint plus the Tetra remote Chrome browser session API. Each call returns parsed fields keyed by the names declared in the query, removing brittle CSS or XPath selectors from agent code.
Jentic publishes the only available OpenAPI specification for AgentQL API, keeping it validated and agent-ready. The main 1.0.0 surface combines AgentQL's web and document extraction with Tetra remote browser session creation behind a single base URL. Three endpoints handle the full flow: query a web page, query a document, or spin up a browser session for sites that need login. Each query call accepts AgentQL syntax or a natural-language prompt and returns parsed fields directly.
Jentic publishes the only available OpenAPI specification for AgentQL REST API, keeping it validated and agent-ready. The 1.0.0 surface is the slimmest production cut of AgentQL: three endpoints that cover web-page queries, document queries, and Tetra remote browser session creation. Each request takes a target (URL or document) plus an AgentQL query or natural-language prompt and returns parsed fields keyed by the query shape. Everything else — pagination, scheduling, dataset storage — is intentionally out of scope.
Jentic publishes the only available OpenAPI specification for Agentset API, keeping it validated and agent-ready. Agentset is an agentic RAG-as-a-service platform that exposes namespace, document, ingest job, and search endpoints behind 11 routes. Agents create a namespace, ingest source documents, then run semantic search with optional filtering and reranking. The API removes the need to operate a vector database, embeddings pipeline, or reranker on your own infrastructure.
Jentic publishes the only available OpenAPI specification for Agility Writer API, keeping it validated and agent-ready. Agility Writer is an AI long-form article generator that produces SEO-optimised content in a job-based flow — a single create call kicks off generation, and a status call returns the article body when ready. The API exposes two endpoints under /api/v1: one to start an article job with a topic and configuration, and one to retrieve the generated article by job ID. Authentication is a Bearer-style token sent in the Authorization header.
Jentic publishes the only available OpenAPI specification for AI For Thai API, keeping it validated and agent-ready. AI For Thai is a suite of Thai-language AI services developed by NECTEC, the National Electronics and Computer Technology Center of Thailand. The API covers text processing (summarisation, word tokenisation, part-of-speech tagging, named-entity recognition, sentiment), speech (Thai speech-to-text and text-to-speech), translation to and from Thai, and image processing (object detection and OCR for Thai script). Authentication uses an API key sent in the Apikey header.
AI Platform Training & Prediction is Google Cloud's earlier-generation managed service for training custom machine learning models and serving online and batch predictions. The API exposes models, model versions, jobs, online predict and explain calls, hyperparameter trial measurement, and study management. Most teams new to Google Cloud now use the Vertex AI API for the same workloads, but AI Platform remains supported for existing pipelines.
Jentic publishes the only available OpenAPI specification for AI/ML API, keeping it validated and agent-ready. AI/ML API is a unified inference platform that exposes chat completions, completions, embeddings, image generation, audio transcription, and text-to-speech behind a single Bearer-authenticated REST surface modelled on OpenAI conventions. The /v1/models endpoint lists supported models so a client can switch backends without changing integration code.
Jentic publishes the only available OpenAPI specification for AIception Interactive, keeping it validated and agent-ready. AIception is a computer vision API that accepts an image URL, runs an asynchronous task (adult content detection, artistic image creation, object detection, face detection, or face age estimation), and returns the result via a task ID lookup. Each capability is implemented as a POST to start the task and a GET by taskId to retrieve the outcome. Authentication uses HTTP Basic with a user account.
AIception Interactive is a computer vision and creative AI service that processes images for content moderation, object detection, face analysis, and artistic style transfer. The API uses an asynchronous task pattern: a POST request creates a task that returns an internal id, and a follow-up GET retrieves the result. It covers vision endpoints for adult content detection, object recognition, face detection, and face age estimation, plus a creative endpoint for stylising one image with another. Authentication is via a UserSecurity API key passed in the request header.
Jentic publishes the only available OpenAPI specification for AIception Interactive, keeping it validated and agent-ready. AIception provides image-analysis services covering content moderation, object detection, face detection, face age estimation, and artistic style transfer. Each endpoint follows an asynchronous task pattern: a POST creates a task that returns a task id, and a GET retrieves the answer once processing is complete. Authentication is via a UserSecurity API key sent as a header.
Jentic publishes the only available OpenAPI specification for AIMLAPI, keeping it validated and agent-ready. AIMLAPI exposes two purpose-built endpoints for document and image understanding: /ocr extracts text from a document image, and /vision analyses an image with vision features. Authentication uses an apiKey scheme (apiKeyAuth). The surface is intentionally narrow, suited to integrations that need OCR and vision analysis without adopting a full multi-modal LLM stack.
Jentic publishes the only available OpenAPI specification for AirOps API, keeping it validated and agent-ready. AirOps is a workflow and agent platform that lets teams build LLM-powered pipelines without writing infrastructure code. The API runs workflows, agents, and legacy apps with synchronous or streaming execution, polls execution status, and supports conversation-style chat with deployed agents. Each workflow or agent is identified by an opaque ID and accepts a JSON inputs payload.
Jentic publishes the only available OpenAPI specification for Airtop API, keeping it validated and agent-ready. Airtop provides cloud browser sessions purpose-built for AI agents, exposing primitives for creating sessions, opening windows, navigating pages, clicking, hovering, filling forms, and running scrape and monitor jobs. The 39-endpoint surface includes synchronous and asynchronous automation flows, a form-filler builder, page query and scrape operations, and profile persistence so a long-running agent can keep cookies and login state across runs. Authentication is bearer-token based, with operations grouped around sessions, windows, automations, and profiles.
Jentic publishes the only available OpenAPI specification for Airweave API, keeping it validated and agent-ready. Airweave is a search and data-management platform that lets developers build retrieval over heterogeneous SaaS sources (Notion, Slack, Google Drive, Stripe, and more). The 27-endpoint API exposes collections (search-ready indexes), source connections (sync configurations), webhook ingestion, and three search modes — instant keyword search, classic semantic search, and agentic search with optional streaming. Authentication uses an x-api-key header.
Jentic publishes the only available OpenAPI specification for AISTA API, keeping it validated and agent-ready. AISTA is a chatbot creation and management platform that lets developers spin up ChatGPT-style assistants trained on custom data. The 6-endpoint API covers chatbot listing, creation, retrieval, deletion, and two training paths — uploading training data directly or scraping a website to harvest source content. Authentication uses an X-API-Key header.
Jentic publishes the only available OpenAPI specification for Akkio API, keeping it validated and agent-ready. Akkio is a no-code predictive AI platform that lets teams upload tabular datasets, train classification and regression models, and run predictions through a REST API. The same API exposes a Chat Explore endpoint for asking natural-language questions about a dataset, plus project and dataset management for organising data across teams. Authentication uses an API key supplied either as an X-API-Key header or an api_key query parameter.
Jentic publishes the only available OpenAPI specification for Aleph Alpha PhariaAI API, keeping it validated and agent-ready. PhariaAI is the inference platform behind Aleph Alpha's Luminous family of large language models, exposing endpoints for text completion, chat, embeddings, semantic similarity, evaluation, question answering, summarisation, and tokenisation. The API is European-hosted and aimed at enterprise teams that need sovereign LLM infrastructure for retrieval, classification, and generation workloads. Authentication uses a bearer token issued from the Aleph Alpha account portal.
Jentic publishes the only available OpenAPI specification for All-Images.ai API, keeping it validated and agent-ready. All-Images.ai is an AI image generation platform that exposes a tight surface area: one endpoint to kick off a generation job and one endpoint to poll for the resulting image. Authentication is via an X-API-Key header, and jobs run asynchronously so callers submit a prompt and check back for the rendered output. The minimal endpoint count makes it well suited for embedding inside agent workflows where one specific image is needed.
Jentic publishes the only available OpenAPI specification for AltText.ai API, keeping it validated and agent-ready. AltText.ai is a vision-AI service that generates accessibility-grade alt text for images at scale, with support for over a hundred languages and an e-commerce-aware mode that incorporates product context. The API exposes 10 X-API-Key endpoints for creating images individually or in bulk, scraping pages for image discovery, and managing the resulting asset records. Teams use it to retrofit alt text on existing CMS libraries and to generate alt text on upload for new content.
Jentic publishes the only available OpenAPI specification for AltTextLab API, keeping it validated and agent-ready. AltTextLab is an AI alt-text generation service that exposes a single POST /alt-text/generate endpoint, supporting more than 130 languages and an e-commerce-aware mode for product imagery. Teams use it to add alt text to images at upload, retrofit existing libraries, and translate alt text into multiple locales. Authentication is a single x-api-key header issued from the AltTextLab dashboard.
Jentic publishes the only available OpenAPI specification for Amazon Augmented AI Runtime, keeping it validated and agent-ready. Amazon Augmented AI (A2I) is the human-in-the-loop layer for ML predictions — when a model's confidence falls below threshold, A2I routes the prediction to a configured workforce (private, vendor, or Amazon Mechanical Turk) for human review. The runtime API starts, monitors, stops, and deletes individual human review tasks (called HumanLoops) tied to a flow definition you create in the SageMaker console.
Jentic publishes the only available OpenAPI specification for Amazon Bedrock Runtime API, keeping it validated and agent-ready. Amazon Bedrock Runtime is the inference plane of Amazon Bedrock, AWS's managed service for foundation models from Anthropic, AI21, Cohere, Meta, Mistral, Stability, and Amazon's own Titan and Nova families. The runtime API lets you invoke a model with a request body in the model's native format, stream tokens as they are generated, run a unified Converse loop across providers, and apply Bedrock Guardrails to inputs and outputs for safety filtering.
Jentic publishes the only available OpenAPI specification for Amazon Comprehend, keeping it validated and agent-ready. Amazon Comprehend is a managed natural language processing service that extracts insights from unstructured text. It detects entities, key phrases, sentiment, targeted sentiment, dominant language, syntax, and personally identifiable information, and supports custom classification and entity recognition models trained on your data. Both real-time analysis and large-scale asynchronous batch jobs are supported, along with topic modeling, document classification, and PII redaction.
Jentic publishes the only available OpenAPI specification for Amazon Forecast Query Service, keeping it validated and agent-ready. The Forecast Query Service is the runtime side of Amazon Forecast and exposes only the operations needed to query trained predictors. The API returns point and quantile forecasts for a specific item, and serves what-if forecasts that compare baseline predictions against scenario adjustments. It is built for application teams that want to embed pre-computed Forecast predictions into customer-facing demand, capacity, or pricing flows.
Jentic publishes the only available OpenAPI specification for Amazon Kendra, keeping it validated and agent-ready. Amazon Kendra is a managed enterprise search service that ingests documents from S3, SharePoint, Confluence, Salesforce, ServiceNow, and many other sources, then answers natural-language queries with passage-level results. Its 65 endpoints cover index lifecycle, data source connectors, query and suggestion APIs, FAQ ingestion, access control mappings for tenant-aware results, query suggestions, and featured-results experiences. Kendra is a frequent retrieval layer for enterprise RAG pipelines that need permission-aware document search.
Jentic publishes the only available OpenAPI specification for Amazon Lex Model Building Service, keeping it validated and agent-ready. The Lex Model Building Service is the v1 control plane for designing conversational bots: defining intents, slot types, slots, and bot aliases that route conversation traffic to specific bot versions. Its 42 endpoints cover intent and slot type lifecycle, bot version management, channel associations for Facebook and Slack, import and export jobs, migration to Lex v2, and tagging. The runtime API for end-user conversations is separate.
Jentic publishes the only available OpenAPI specification for Amazon Lex Model Building V2, keeping it validated and agent-ready. Lex Model Building V2 is the authoring control plane for Amazon Lex conversational bots — it manages bots, bot versions, locales, intents, slot types, slots, custom vocabulary and aliases, and orchestrates the build, import, export and tagging of those resources. The 71 endpoints cover the full bot lifecycle from CreateBot through BuildBotLocale, intent and slot configuration, custom vocabulary upload, version pinning and alias-based deployment.
Jentic publishes the only available OpenAPI specification for Amazon Lex Runtime V2, keeping it validated and agent-ready. Lex Runtime V2 is the conversational dataplane for Amazon Lex V2 bots — it exchanges user text or audio with a deployed bot alias and returns recognised intents, slot values, and the bot's next response. The runtime carries session state across turns, supports both text and streaming utterance recognition, and is the integration point for chat widgets, IVR systems, and voice assistants built on Lex V2.