JFrog
JFrog provides universal DevOps solutions for software supply chain automation and security, offering a unified platform for managing binaries, securing the software supply chain, and automating DevOps workflows.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles JFrog the way a machine reads it — 230 machine-readable artifacts across 53 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — JFrog scores 77.6/100 (exemplar), with a separate agent-readiness read of 70/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile JFrog
Each block below is one kind of artifact we hold for JFrog. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 53
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
JFrog Access Tokens API
Token creation and management
JFrog Artifacts & Storage API
Deploy, retrieve, copy, move, and delete artifacts
JFrog Audit API
Curation audit and activity logs
JFrog Builds API
Build information and promotion
JFrog Commands API
Remote command execution on devices
JFrog Components API
Component details and vulnerability information
JFrog Deployments API
Model deployment and serving
JFrog Device Groups API
Logical grouping of devices
JFrog Devices API
Device management and monitoring
JFrog Distribution API
Distribute release bundles to edge nodes
JFrog Evidence API
Create and manage evidence attestations
JFrog Execution API
Worker testing and execution
JFrog Experiments API
ML experiment tracking
JFrog GraphQL API
GraphQL query interface for package and CVE data
JFrog Groups API
User group management
JFrog Ignore Rules API
Rules for ignoring specific vulnerabilities
JFrog Integrations API
External service integrations
JFrog JPDs API
JFrog Platform Deployment management
JFrog Labels API
Custom label management for packages
JFrog Licenses API
License management across instances
JFrog Model Versions API
Model version management
JFrog Models API
ML model registry and management
JFrog Node Pools API
Build node pool management
JFrog Packages API
Package metadata search and retrieval
JFrog Permissions API
Permission target management
JFrog Pipeline Sources API
Manage pipeline source configurations
JFrog Pipelines API
Pipeline definitions and management
JFrog Policies API
Curation policy management
JFrog Projects API
Project administration
JFrog Promotion API
Promote release bundles through environments
JFrog Properties API
Set, update, and delete artifact properties
JFrog Release Bundles V1 API
Create and manage release bundles (v1)
JFrog Release Bundles V2 API
Create and manage release bundles v2
JFrog Replication API
Push and pull replication configuration
JFrog Reports API
Vulnerability and compliance reports
JFrog Repositories API
Create, read, update, and delete repositories
JFrog Runs API
Pipeline run execution and monitoring
JFrog Scanning API
On-demand scanning operations
JFrog Scripts API
Remote execution scripts
JFrog Searches API
Search for artifacts using various criteria
JFrog Security API
Users, groups, permissions, and access tokens
JFrog Steps API
Pipeline step execution details
JFrog Summary API
Artifact and build vulnerability summaries
JFrog System API
Access service system information
JFrog System & Configuration API
System health, configuration, and version information
JFrog Tokens API
Access token creation, management, and revocation
JFrog Updates API
OTA software update deployments
JFrog Users API
Platform user management
JFrog Verification API
Verify evidence and retrieve verification status
JFrog Violations API
Policy violations management
JFrog Watches API
Watch policies for monitoring artifacts
JFrog Webhooks API
Webhook configuration
JFrog Workers API
Worker lifecycle management
Scroll within the panel for all 53 ·
Postman Collections 14
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
JFrog Access REST API
POSTMANJFrog Artifactory REST API
POSTMANJFrog Catalog REST API
POSTMANJFrog Connect REST API
POSTMANJFrog Curation REST API
POSTMANJFrog Distribution REST API
POSTMANJFrog Evidence REST API
POSTMANJFrog ML REST API
POSTMANJFrog Pipelines REST API
POSTMANJFrog Platform REST API
POSTMANJFrog Workers REST API
POSTMANJFrog Xray REST API
POSTMANScroll within the panel for all 14 ·
Open Collections 14
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
JFrog Access REST API
OPEN COLLECTIONJFrog Artifactory REST API
OPEN COLLECTIONJFrog Catalog REST API
OPEN COLLECTIONJFrog Connect REST API
OPEN COLLECTIONJFrog Curation REST API
OPEN COLLECTIONJFrog Distribution REST API
OPEN COLLECTIONJFrog Evidence REST API
OPEN COLLECTIONJFrog Mission Control REST API
OPEN COLLECTIONJFrog ML REST API
OPEN COLLECTIONJFrog Pipelines REST API
OPEN COLLECTIONJFrog Platform REST API
OPEN COLLECTIONJFrog Release Lifecycle Management REST API
OPEN COLLECTIONJFrog Workers REST API
OPEN COLLECTIONJFrog Xray REST API
OPEN COLLECTIONScroll within the panel for all 14 ·
Arazzo Workflows 25
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
JFrog Access Create User With Group
Create a group then a user in that group via the Access service.
ARAZZOJFrog Cleanup Stale Artifacts
Run an AQL search for stale artifacts and delete the first match.
ARAZZOJFrog Configure Repository Replication
Confirm a repository exists then configure push replication for it.
ARAZZOJFrog Deploy and Verify Artifact
Deploy an artifact to a repository and confirm its storage metadata.
ARAZZOJFrog Distribution Release Bundle
Create a release bundle, sign it, distribute it, and poll for status.
ARAZZOJFrog Grant Repository Permission
Create a permission target granting a group access to a repository.
ARAZZOJFrog Pipelines Trigger and Monitor
Trigger a pipeline run, find the new run, and poll until it finishes.
ARAZZOJFrog Promote Artifact by Checksum
Find an artifact by its checksum and copy it to a release repository.
ARAZZOJFrog Provision Local Repository
Create a local Artifactory repository and confirm its configuration.
ARAZZOJFrog Release Bundle v2 Promote
Create a v2 release bundle from a build and promote it to an environment.
ARAZZOJFrog Secure Publish Artifact
Deploy an artifact then immediately scan it with Xray for issues.
ARAZZOJFrog Xray Component License Check
Look up component details then confirm via the catalog version data.
ARAZZOJFrog Xray Policy and Watch
Create a security policy then a watch that assigns it to a repository.
ARAZZOJFrog Xray Triage Violation
Query Xray violations and create an ignore rule when any are found.
ARAZZOScroll within the panel for all 25 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERAgent Skills 2
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
jfrog-package-safety-and-download
AGENT SKILLjfrog
AGENT SKILLGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
JFrog GraphQL API
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Jfrog Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Jfrog Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Jfrog Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Jfrog Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JFrog API Rules
SPECTRALJSON Schema 110
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessToken
JSON SCHEMAAqlSearchResult
JSON SCHEMAJFrog Artifact
JSON SCHEMAArtifactSummary
JSON SCHEMAAuditEntry
JSON SCHEMAJFrog Build Info
JSON SCHEMABuildInfo
JSON SCHEMABuildPromotion
JSON SCHEMABuildRuns
JSON SCHEMABuildsList
JSON SCHEMABuildSummary
JSON SCHEMACatalogVulnerability
JSON SCHEMAChecksums
JSON SCHEMACommandRequest
JSON SCHEMAComponentDetail
JSON SCHEMACreateEvidenceRequest
JSON SCHEMACreateTokenRequest
JSON SCHEMACreateUserRequest
JSON SCHEMAJFrog Curation Policy
JSON SCHEMACurationPolicy
JSON SCHEMACurationPolicyRequest
JSON SCHEMADeployment
JSON SCHEMADeploymentRequest
JSON SCHEMADeployResponse
JSON SCHEMADevice
JSON SCHEMADeviceGroup
JSON SCHEMADeviceGroupRequest
JSON SCHEMADistributeRequest
JSON SCHEMADistributionRequest
JSON SCHEMAJFrog Evidence
JSON SCHEMAEvidenceRequest
JSON SCHEMAEvidenceSearchRequest
JSON SCHEMAExperiment
JSON SCHEMAExperimentRequest
JSON SCHEMAFileInfo
JSON SCHEMAFolderInfo
JSON SCHEMAGraphQLRequest
JSON SCHEMAGraphQLResponse
JSON SCHEMAGroup
JSON SCHEMAGroupSummary
JSON SCHEMAIgnoreRule
JSON SCHEMAIntegration
JSON SCHEMAIntegrationRequest
JSON SCHEMAIssue
JSON SCHEMAItemProperties
JSON SCHEMAJPD
JSON SCHEMAJPDRequest
JSON SCHEMALabel
JSON SCHEMALabelRequest
JSON SCHEMALicenseBucket
JSON SCHEMALicenseInfo
JSON SCHEMAModel
JSON SCHEMAModelRequest
JSON SCHEMAModelVersion
JSON SCHEMAModelVersionRequest
JSON SCHEMAMoveOrCopyResponse
JSON SCHEMANodePool
JSON SCHEMANodePoolRequest
JSON SCHEMAPackageDetail
JSON SCHEMAPackageSearchRequest
JSON SCHEMAPackageSearchResponse
JSON SCHEMAPackageSummary
JSON SCHEMAPackageVersion
JSON SCHEMAJFrog Permission Target
JSON SCHEMAPermissionTarget
JSON SCHEMAPermissionTargetSummary
JSON SCHEMAJFrog Pipeline
JSON SCHEMAPipelineSource
JSON SCHEMAPipelineSourceRequest
JSON SCHEMAPlatformGroup
JSON SCHEMAPlatformUser
JSON SCHEMAPolicy
JSON SCHEMAProject
JSON SCHEMAProjectRequest
JSON SCHEMAPromotionRequest
JSON SCHEMAPromotionStatus
JSON SCHEMAJFrog Release Bundle
JSON SCHEMAReleaseBundle
JSON SCHEMAReleaseBundleRequest
JSON SCHEMAReleaseBundleV2
JSON SCHEMAReleaseBundleV2Request
JSON SCHEMAReleaseBundleV2Summary
JSON SCHEMAReplicationConfig
JSON SCHEMAJFrog Repository
JSON SCHEMARepositoryConfiguration
JSON SCHEMARepositoryListItem
JSON SCHEMARun
JSON SCHEMAScript
JSON SCHEMAScriptRequest
JSON SCHEMASearchResult
JSON SCHEMAJFrog Security Vulnerability
JSON SCHEMAStep
JSON SCHEMAStorageSummary
JSON SCHEMASystemHealth
JSON SCHEMASystemVersion
JSON SCHEMATokenInfo
JSON SCHEMATokenResponse
JSON SCHEMAUpdate
JSON SCHEMAUpdateRequest
JSON SCHEMAUpdateUserRequest
JSON SCHEMAJFrog Platform User
JSON SCHEMAUserSummary
JSON SCHEMAVerificationResult
JSON SCHEMAViolationsResponse
JSON SCHEMAVulnerability
JSON SCHEMAWatch
JSON SCHEMAWebhook
JSON SCHEMAWebhookRequest
JSON SCHEMAJFrog Worker
JSON SCHEMAWorkerRequest
JSON SCHEMAScroll within the panel for all 110 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Jfrog Structure
JSON STRUCTURESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for JFrog — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 12
Reference material describing how the API behaves
Scroll within the panel for all 12 ·
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 27
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 27 ·
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
Access & Security 4
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 6
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/jfrog · machine-readable index on apis.io