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
Jentic publishes the only available OpenAPI specification for Academic Torrents API, keeping it validated and agent-ready. Academic Torrents is a community-maintained distributed repository for sharing large research datasets over BitTorrent, and its v2 API exposes operations for creating, retrieving, and modifying torrent entries and managing named collections of torrents. Authentication uses session-style credentials passed as cookies (uid, pass) or query parameters, and the API is hosted at academictorrents.com/apiv2. It is intended for researchers, archive maintainers, and dataset publishers who want to programmatically register, group, and manage torrents.
Jentic publishes the only available OpenAPI specification for Airtable Web API, keeping it validated and agent-ready. Airtable is a cloud database that combines spreadsheet familiarity with relational features such as linked records, formulas, and views. The 21 documented endpoints expose record-level CRUD inside a base/table, metadata for bases, tables, and fields, and webhook subscriptions for change notifications. Authentication uses bearer personal access tokens or OAuth 2.0 tokens with scoped permissions per base.
The AlloyDB API is the control plane for AlloyDB for PostgreSQL on Google Cloud — Google's PostgreSQL-compatible managed database service tuned for transactional and analytical workloads. It provisions and manages clusters and primary or read-pool instances, runs failover and switchover, drives backups and exports, and supports cluster restore. Application data access still goes through the standard PostgreSQL wire protocol; this API is for lifecycle and operations.
Jentic publishes the only available OpenAPI specification for Amazon Cognito Sync, keeping it validated and agent-ready. Amazon Cognito Sync stores and synchronizes user-scoped key-value data across a user's devices and the cloud. Each user has datasets containing string records that are merged on conflict and pushed to all signed-in devices via Amazon SNS push notifications. It is a legacy service - AWS now recommends AWS AppSync for new cross-device sync work - but it remains useful for apps already on Cognito Identity that need lightweight per-user state.
Jentic publishes the only available OpenAPI specification for Amazon Data Lifecycle Manager, keeping it validated and agent-ready. Amazon Data Lifecycle Manager (DLM) automates the creation, retention, and deletion of Amazon EBS snapshots and AMI backups through declarative lifecycle policies. The API exposes a small surface — create, get, update, and delete policies, plus tag operations — that is purpose-built for treating backup schedules as code. Use it when an agent needs to enforce backup posture across many accounts or to programmatically rotate retention windows as compliance requirements change.
Jentic publishes the only available OpenAPI specification for Amazon DocumentDB, keeping it validated and agent-ready. Amazon DocumentDB is a managed document database with MongoDB compatibility, designed to run document workloads at scale on AWS. The API covers the full control plane: clusters, instances, parameter groups, snapshots, subnet groups, global clusters, event subscriptions, and pending-maintenance actions. Use it when an agent needs to provision DocumentDB clusters, restore from a snapshot, scale instances, or manage cross-region global clusters without going through the AWS console.
Jentic publishes the only available OpenAPI specification for Amazon DynamoDB Accelerator (DAX), keeping it validated and agent-ready. Amazon DynamoDB Accelerator (DAX) is a managed in-memory caching service that sits in front of Amazon DynamoDB to deliver sub-millisecond read latency for cached items. The DAX control plane API lets you provision and operate clusters, manage parameter groups and subnet groups, scale replication factor, describe events, and tag resources. It is intended for read-heavy workloads where DynamoDB latency or cost-per-read becomes a bottleneck and a write-through cache makes economic sense.
Jentic publishes the only available OpenAPI specification for the Amazon EBS direct APIs, keeping them validated and agent-ready. The EBS direct APIs let backup vendors and applications create EBS snapshots, write data blocks directly into a snapshot, read snapshot blocks, and compute the differences between two snapshots. They are designed for incremental backup and disaster recovery flows that need block-level access without spinning up an EC2 instance to mount a volume. Use them when an agent needs to ingest snapshot data, restore from on-premises backups into the cloud, or efficiently track changed blocks between snapshots.
Jentic publishes the only available OpenAPI specification for Amazon Import/Export Snowball, keeping it validated and agent-ready. The Snow Family management API lets organisations create and track jobs that move large volumes of data between on-premises sites and Amazon S3 using physical Snowball, Snowball Edge, and Snowcone devices. Agents can create addresses, request jobs and clusters, fetch job manifests and unlock codes, generate return shipping labels, and manage long-term pricing arrangements. The 26 operations cover addresses, jobs, clusters, manifests, return shipping, and Snow device pricing.
Jentic publishes the only available OpenAPI specification for Amazon QLDB Session, keeping it validated and agent-ready. QLDB Session is the low-level transactional protocol behind Amazon Quantum Ledger Database. It exposes a single SendCommand operation that multiplexes session start, transaction begin, PartiQL statement execution, fetch-page, commit, and end-session commands over one signed request channel. Most applications use the QLDB driver or shell on top of this API; direct use is appropriate when building a custom QLDB client, language binding, or agent transport layer.
Jentic publishes the only available OpenAPI specification for Amazon SimpleDB, keeping it validated and agent-ready. Amazon SimpleDB is a schemaless, automatically indexed key-value data store that exposes domain, item, and attribute primitives over a query API. Agents can create domains, put and get attributes on items, run select-style queries, and perform batched mutations without managing servers, indexes, or replication. SimpleDB targets small-to-medium structured datasets where simplicity and elasticity matter more than transactional joins.
Upload a BidPrice record. The API exposes 1 endpoints secured with apiKey authentication.
Si prefiere usar Postman -> [Click aquí](https://drive.google.com/file/d/122dFgnGraTBVTtx3AMHzdApc9YJ42mVA/view?usp=sharing). The API exposes 2 endpoints secured with bearer authentication.
AWS Backup is a unified, policy-based backup service for AWS resources, including EBS volumes, EC2 instances, RDS and Aurora databases, DynamoDB tables, EFS, FSx, S3, and Storage Gateway. The API lets you define backup plans with schedules and retention rules, group resources via selections and tags, store recovery points in encrypted backup vaults with vault locks for immutability, restore on demand, and run audit frameworks with reports for compliance evidence. It also supports legal holds that block deletion of designated recovery points.
Jentic publishes the only available OpenAPI specification for AWS Database Migration Service, keeping it validated and agent-ready. AWS Database Migration Service (DMS) moves data between databases — homogeneous (Oracle to Oracle) or heterogeneous (Oracle to PostgreSQL) — with optional ongoing change-data-capture replication. The API covers the full migration lifecycle: replication instances, source and target endpoints, replication tasks, table mappings, premigration assessments, and Fleet Advisor inventory. Use it when an agent needs to orchestrate a migration plan, kick off a replication task, or pull assessment results back into a runbook.
Jentic publishes the only available OpenAPI specification for AWS Elemental MediaStore, keeping it validated and agent-ready. MediaStore is a low-latency object store optimized for media workflows — live origin storage, ingest from encoders, and delivery to packagers. Containers are the top-level namespace; each container has a unique data endpoint and supports container policies, CORS policies, lifecycle policies, and metric policies. The service is designed for high-throughput sequential reads and writes typical of streaming workloads rather than archival use cases.
Jentic publishes the only available OpenAPI specification for the AWS RDS Data API, keeping it validated and agent-ready. The RDS Data API runs SQL against Aurora Serverless and Aurora DSQL clusters over HTTPS without persistent database connections or VPC connectivity, using IAM and Secrets Manager for authentication. Six operations cover single-statement execution, batch parameterized execution, transaction begin and commit and rollback, and a legacy ExecuteSql endpoint. It is the right fit for serverless functions, mobile clients, and AI agents that need ad-hoc SQL access without managing a connection pool.
The Azure Data Catalog Resource Provider API manages Azure Data Catalog services as ARM resources. It exposes operations to list, create, update, and delete catalogs scoped to a resource group, plus a discovery endpoint that returns supported Microsoft.DataCatalog actions. This is the control plane for provisioning the catalog itself; the catalog's data-plane content (assets, sources, terms) is registered through a separate Data Catalog REST API.
The Azure Data Migration Service (DMS) Resource Provider API manages DMS service instances and the projects and tasks they execute to move databases into Azure. It exposes 26 endpoints covering service CRUD, project lifecycle, generic migration tasks with typed inputs and outputs, SKU listings, name availability checks, and quota usage. Tasks are deliberately generic so new migration scenarios can be added without provider updates.
Jentic publishes the only available OpenAPI specification for Azure SQL Database, keeping it validated and agent-ready. This 2014-04-01 surface scopes down to the checkNameAvailability operation under Microsoft.Sql, which validates whether a candidate Azure SQL server name is available within a subscription before provisioning. It is a focused control plane utility used as a precondition step in any Azure SQL server creation workflow.
The Azure SQL Database Backup API provides read access to recoverable databases and restorable dropped databases under Azure SQL Server resources. Agents can list geo-redundant backups available for recovery, retrieve backup metadata for specific databases, and inspect dropped databases that remain restorable within their retention window. The API exposes 4 GET operations under the Microsoft.Sql resource provider and is intended for disaster-recovery discovery and audit workflows on Azure SQL Server.
Jentic publishes the only available OpenAPI specification for Azure SQL Database Backup Long Term Retention Policy, keeping it validated and agent-ready. The API reads and updates the long-term retention policy applied to a single Azure SQL database, the policy that pins backups beyond the default short-term retention window. It exposes 3 endpoints under Microsoft.Sql for listing the policy on a database, getting a named policy, and creating or updating one.
Jentic publishes the only available OpenAPI specification for Azure SQL Database disaster recovery configurations, keeping it validated and agent-ready. The API provisions and manages disaster recovery configurations on Azure SQL Database servers, allowing agents to inspect a server's DR configuration, create or remove a recovery pairing, and trigger failover or forced failover that allows data loss. It targets the Microsoft.Sql resource provider on the Azure Resource Manager control plane and is intended for high-availability automation across regions, not for routine database query or schema work.
Jentic publishes the only available OpenAPI specification for Azure SQL Database Import/Export spec, keeping it validated and agent-ready. The API drives BACPAC-based import and export operations on Azure SQL Database, letting agents export a database to Azure Blob Storage, import a BACPAC into a new database, or register an extension that tracks the operation. It targets the Microsoft.Sql resource provider on Azure Resource Manager and is intended for migration, archival, and environment-cloning workflows rather than live data access.
Jentic publishes the only available OpenAPI specification for Azure SQL Database replication links, keeping it validated and agent-ready. The API inspects and controls geo-replication links between a primary Azure SQL database and one or more secondary copies, letting agents list links, retrieve a specific link, delete it, or trigger a planned or forced failover at the database level. It targets the Microsoft.Sql resource provider on Azure Resource Manager and complements the server-level disaster recovery configuration API for finer-grained, per-database failover control.
Jentic publishes the only available OpenAPI specification for Azure SQL Server Backup Long Term Retention Vault, keeping it validated and agent-ready. The API associates an Azure SQL logical server with a Recovery Services vault that holds long-term retention backups, letting agents list current vault associations, retrieve a specific vault registration, or attach a new vault to a server. It targets the Microsoft.Sql resource provider on Azure Resource Manager and is intended for compliance and retention workflows that exceed the default backup window.
Jentic publishes the only available OpenAPI specification for AzureDataManagementClient, keeping it validated and agent-ready. The API registers and manages on-premises SQL Server instances as Azure Data resources, letting agents create SQL Server registrations, list registered SQL Servers under a registration, and manage individual SQL Server entries. It targets the Microsoft.AzureData resource provider on Azure Resource Manager and is intended for hybrid scenarios where on-prem SQL Server inventory needs to surface inside the Azure portal and ARM tooling.
Jentic publishes the only available OpenAPI specification for Backblaze B2 Cloud Storage API, keeping it validated and agent-ready. Store and retrieve objects in B2 cloud storage with 24 endpoints covering bucket management, file upload and download, application key administration, and large file multipart operations. Pricing runs at one-quarter the cost of major cloud providers with no egress fees for partner integrations and S3-compatible access.
The Backup and DR Service API manages Google Cloud's enterprise backup product for Compute Engine, VMware, databases, and file storage. It exposes operations to provision management servers, control data sources, initiate and finalise backups, and manage the long-running operations associated with each step. The API is the integration surface for orchestrating backups from external schedulers, ticketing systems, or compliance workflows. It manages backup orchestration, not the actual virtual machines, databases, or file systems being protected.
Jentic publishes the only available OpenAPI specification for BackupManagementClient, keeping it validated and agent-ready. The Admin Backup Management Client exposes operations metadata for the Microsoft.Backup.Admin resource provider on Azure Stack Hub. It allows operators to enumerate the available admin-side backup operations against an Azure Stack stamp through its admin management endpoint.
Jentic publishes the only available OpenAPI specification for Basesnap API, keeping it validated and agent-ready. Basesnap is a database snapshot and backup service that lets teams capture point-in-time copies of their databases and roll back to any prior snapshot on demand. The API exposes three core operations covering snapshot listing, snapshot creation, and snapshot restoration, all secured by an API key passed in the Authorization header. It is suitable for ops teams that want programmatic disaster-recovery automation rather than relying on manual database tooling.
This is the section of the Bifrost API that provides all methods to incorporate fundus image upload and handling in custom apps. The API exposes 28 endpoints.
BOOK A DEMO
Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.