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.
1Password Connect is a self-hosted REST API that lets applications and infrastructure read and write items stored in 1Password vaults without exposing master credentials. The server runs alongside your workloads, exchanges a Connect bearer token (JWT) for scoped vault access, and exposes endpoints for vaults, items, files, activity logs, and health probes. It is the deployment path teams use to inject secrets into CI/CD pipelines, Kubernetes clusters, and homelab services without reaching out to the public 1Password.com API. The catalogued spec covers 15 endpoints across Items, Vaults, and Activity, plus heartbeat, health, and Prometheus metrics endpoints for operational monitoring.
Retrieve audit events, item usage logs, and sign-in attempt records from 1Password Business accounts through 5 focused endpoints. The Events API surfaces security-relevant activity including vault item access patterns, failed authentication attempts, and administrative changes across the organization. Regional endpoint support (US, Canada, EU) ensures data residency compliance while bearer token authentication via service account JWTs provides secure programmatic access for SIEM integrations and security monitoring workflows.
Jentic publishes the only available OpenAPI specification for abuse.ch URLhaus API, keeping it validated and agent-ready. URLhaus is abuse.ch's project for sharing malicious URLs used for malware distribution. The API exposes two operations: a POST endpoint for submitting newly observed malware URLs with tags and threat metadata, and a recent-CSV export endpoint for downloading the database. Authentication is via an Auth-Key tied to a free abuse.ch account, and the dataset is widely used as a threat-intel feed by SOCs, mail filters, and DNS sinkholing services.
Jentic publishes the only available OpenAPI specification for AbuseIPDB API, keeping it validated and agent-ready. AbuseIPDB is a community-driven database of IP addresses reported for malicious activity such as brute-force attacks, scanners, and spam. The v2 API exposes seven endpoints covering single-IP and CIDR-block lookups, full report histories, blacklist downloads, single and bulk abuse reports, and self-clearing of submitted reports. Authentication is a Key header tied to a free or paid AbuseIPDB account, and responses include a 0-100 abuse confidence score that fits naturally into firewall, SIEM, and triage workflows.
Jentic publishes the only available OpenAPI specification for AbuseIPDB API, keeping it validated and agent-ready. AbuseIPDB is a community-driven database of IP addresses reported for malicious behaviour including brute-force attacks, scanners, and spam. The v2 API exposes seven endpoints for scoring single IPs, querying CIDR blocks, downloading blacklists, submitting individual or bulk abuse reports, and clearing your own reports. Authentication is a Key header on every call, and responses include a 0-100 abuse confidence score that is widely used as input to firewall, SIEM, and authentication-risk pipelines.
The Abusive Experience Report API exposes Google's findings on sites that show abusive experiences such as fake messages, deceptive ads, and unexpected redirects. It returns the abusive status (Failing, Passing, or Not Reviewed) for a single site and a list of all sites currently failing the report. Publishers and ad-quality teams use it to monitor whether their domains are at risk of having Chrome filter abusive ads.
The Access Approval API gives Google Cloud customers explicit control over when Google personnel can access their data. It exposes operations to configure approval settings on a project, folder, or organisation, list pending approval requests, and approve, dismiss, or invalidate each request. Compliance and security teams use it to satisfy regulatory requirements that demand documented, customer-approved access by the cloud provider's support staff.
The Access Context Manager API lets Google Cloud organisations define attribute-based access controls on requests to Google Cloud services. It exposes operations to manage access policies, access levels (boolean expressions over device, IP, and identity attributes), and service perimeters that restrict data movement between projects. Security and platform teams use it to enforce zero-trust controls and to build VPC Service Controls perimeters around regulated workloads.
This is an example of using OAuth2 Password Flow in a specification to describe security to your API. The API exposes 2 endpoints secured with oauth2 authentication.
Jentic publishes the only available OpenAPI specification for Acronis Cyber Protect Cloud API, keeping it validated and agent-ready. The Cyber Protect Cloud API exposes platform management for managed service providers and enterprise tenants — tenant management, user management, alerts, and reporting — through 13 endpoints under cloud.acronis.com/api. Authentication is bearer token, obtained via POST /2/idp/token. The API is used by MSPs and security teams to provision client tenants, manage user access, and read protection alerts programmatically.
Jentic publishes the only available OpenAPI specification for Acronis Cyber Protect Cloud API, keeping it validated and agent-ready. The Acronis Cyber Protect Cloud API exposes platform management for managed service providers and IT teams running Acronis-backed cyber protection: tenant provisioning, user lifecycle, alert review, and reporting. It uses bearer token authentication issued through the /2/idp/token endpoint and operates on the cloud.acronis.com/api base. The endpoint surface is compact and tuned for partner-portal automation rather than backup-agent control.
Jentic publishes the only available OpenAPI specification for addy.io API Documentation, keeping it validated and agent-ready. addy.io is an anonymous email forwarding service that lets users create unlimited aliases backed by their real inbox, then activate, deactivate, pin, or delete those aliases as relationships with senders change. The API exposes account details, alias bulk actions, individual aliases, blocklists, recipients, custom domains, usernames, rules, failed deliveries, and more — covering every concept in the addy.io UI. Authentication is a personal access token passed as a bearer token in the Authorization header.
Submit GDPR Subject Erasure Requests against shopper data held by Adyen, including payment details, delivery addresses, and shopper email addresses tied to past transactions. The API exposes a single operation that records the erasure request and returns a unique request reference for audit and follow-up. Designed for merchants that need a programmatic way to satisfy Article 17 right-to-be-forgotten obligations.
Jentic publishes the only available OpenAPI specification for Akamai SIEM API, keeping it validated and agent-ready. The Akamai SIEM API exposes a security information and event management integration surface — three endpoints covering token-based authentication and resource listing and retrieval. It is intended for ingesting Akamai security events into an external SIEM, with API-key authentication on the X-API-Key header and a separate token endpoint for issuing access tokens.
Jentic publishes the only available OpenAPI specification for Akeyless API, keeping it validated and agent-ready. Akeyless is a vaultless secrets-management platform — the v2 API exposes 17 endpoints covering authentication, static and dynamic secrets, encryption and decryption, auth methods, roles and rules, and gateway access listing. Calls are POST-driven with bearer-token authentication after an initial /auth call returns a session token.
Jentic publishes the only available OpenAPI specification for Amazon Detective, keeping it validated and agent-ready. Amazon Detective uses machine learning and graph analytics to help security teams investigate potential security issues across AWS workloads. The API manages behavior graphs that aggregate CloudTrail, VPC flow logs, and GuardDuty findings from a set of member accounts, and lets the administrator account invite, accept, and remove members, configure organization-wide enrolment, and apply tags. Use it when an agent or workflow needs to programmatically administer Detective behavior graphs across many AWS accounts.
Jentic publishes the only available OpenAPI specification for Amazon GuardDuty, keeping it validated and agent-ready. Amazon GuardDuty is a continuous threat detection service that analyses VPC flow logs, CloudTrail events, DNS logs, EKS audit logs, and EBS volume data to surface suspicious activity in AWS accounts. The API covers full lifecycle management of detectors, findings, threat intelligence sets, IP allow lists, member accounts, malware protection plans, and publishing destinations across 67 operations.
The Anchore Engine API is the primary external surface for Anchore Engine, an open-source container image scanning and policy evaluation service. Across 112 endpoints it covers accounts and users, image and repository management, archives of historical analyses, archive rules, events, policies and policy evaluation, registries, repository credentials, subscriptions, summaries, system health and configuration, and import flows for SBOM and analysis data. The spec uses HTTP Basic authentication and is typically deployed inside a customer's environment, so the base URL is whatever host the operator binds the service to.
The Google Cloud API Keys API manages the API keys associated with developer projects. It exposes operations to create, retrieve, update, delete, and undelete keys, look up a key by string, and fetch the key string itself. API keys can be restricted by API target, IP address, HTTP referrer, or Android and iOS application identifiers, giving teams least-privilege credentials for unauthenticated services.
Api encargada de la administracion de la seguridad. The API exposes 1 endpoints secured with basic authentication.
HCL AppScan on Cloud is a security testing platform for static, dynamic, and software composition analysis. Its v4 REST API exposes the same operations as the AppScan UI plus additional automation hooks: managing application records, launching SAST and DAST scans, exporting issues, and integrating with asset groups and policies. Security teams use it to embed AppScan into CI/CD pipelines and pull issue data into ticketing systems for triage.
AppServiceCertificateOrders API Client is the Azure Resource Manager surface for managing App Service Certificates — the Azure-managed TLS certificate offering for App Service Web Apps. It covers the full certificate order lifecycle: placing orders, validating registration data, retrieving and reissuing certificates, renewing before expiry, and resending email or domain verification. Certificates issued through the API can be deployed directly to App Service apps and Key Vault.
Jentic publishes the only available OpenAPI specification for Arventa WHS Monitor API, keeping it validated and agent-ready. Arventa WHS Monitor is a cloud-based Work Health and Safety compliance platform used by Australian businesses to manage workers, sites, chemicals, incident reports, and risk assessments. The API exposes 58 endpoints across 15 resource areas including checklists, audit logs, departments, locations, and chemical storage tracking. Bearer token authentication protects all calls and the API supports paginated retrieval for high-volume operational data.
The Assured Workloads API programmatically manages Google Cloud's compliance-controlled folders that enforce regulatory regimes such as FedRAMP, IL4, CJIS, and EU Sovereign Controls on the resources created inside them. It exposes operations to create and update workloads, restrict allowed resource types and locations, mutate partner-controlled permissions, and acknowledge violations surfaced by the platform. Workload state changes are returned as long-running operations that callers must poll for completion. The API is the control-plane for compliance posture, not for building or running the underlying applications.
AttestationClient is the per-tenant Azure Attestation Service API used to verify the integrity of trusted execution environments such as Intel SGX enclaves and TPM-backed workloads. It exposes the OpenID Connect discovery document, the signing certificate set used to verify attestation tokens, and the policy management endpoints that govern how attestation requests are evaluated. Use this client to validate confidential compute workloads or to maintain attestation policy.
The Vonage Audit API (audit) exposes a read-only stream of changes made to a Vonage account. It records application configuration changes, user secret creations and deletions, and account-level setting updates with timestamps, actor identifiers, and before/after diffs. The 2 endpoints — paginated list and single-event retrieval — cover the surface needed to drive compliance dashboards, SIEM integration, and incident triage. Vonage flags this API as beta on the /beta/audit base path.
The Vonage Audit API (audit-api) exposes a read-only stream of changes made to a Vonage account. It records application configuration changes, user secret creations and deletions, and account-level setting updates with timestamps, actor identifiers, and before/after diffs. The 2 endpoints — paginated list and single-event retrieval — cover the surface needed to drive compliance dashboards, SIEM integration, and incident triage. Vonage flags this API as beta on the /beta/audit base path.
The HubSpot Audit Logs API returns user-activity records for a HubSpot portal — successful logins, audit events, and security-history entries such as password changes and two-factor updates. The three endpoints under /account-info/v3/activity each return paginated activity records that a SIEM or compliance dashboard can ingest. The data is read-only and is intended for security monitoring rather than user management. Authentication uses OAuth 2.0 or a private app token.
AWS Audit Manager automates the collection of evidence for compliance audits across AWS workloads. It uses prebuilt and custom frameworks — such as PCI DSS, HIPAA, and SOC 2 — to map controls to assessable AWS services and continuously gather evidence into structured assessments and reports.
Jentic publishes the only available OpenAPI specification for AWS Certificate Manager, keeping it validated and agent-ready. AWS Certificate Manager (ACM) provisions, manages, and deploys SSL/TLS certificates for AWS resources such as Elastic Load Balancers, CloudFront distributions, and API Gateway endpoints. The API exposes 15 operations covering certificate request, import, listing, deletion, tagging, and account-level configuration, so platform teams can automate certificate lifecycle and avoid expiry-related outages.
Jentic publishes the only available OpenAPI specification for AWS CloudHSM V2, keeping it validated and agent-ready. AWS CloudHSM V2 provides single-tenant, FIPS 140-2 Level 3 hardware security modules in your VPC for generating and using cryptographic keys. Agents can create and manage HSM clusters, provision individual HSMs, take and restore backups, and copy backups across regions. The service is intended for workloads with strict key custody, compliance, or BYOK requirements where AWS KMS multi-tenant HSMs are not sufficient.
Jentic publishes the only available OpenAPI specification for AWS CloudTrail, keeping it validated and agent-ready. AWS CloudTrail records management and data events across an AWS account, delivers them to S3 or an event data store, and lets you query the log with CloudTrail Lake. The API covers trails, channels, event data stores, query execution, and resource policies, so an agent can configure logging, run SQL-like queries, and pull recent events without touching the console.