Install Jentic One Beta

Connect the Quay Frontend to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Quay Frontend, 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%2Fquayio%2Fquayio" | sh

Step 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%2Fquayio%2Fquayio" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Quay Frontend API.

listPlans

listOrgInvoices

bindSkuToOrg

listOrgSkus

batchRemoveSku

GET STARTED

Start building with Quay Frontend API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Quay Frontend API for, with concrete tasks.

★ Developer Tools Operations

Use the Quay Frontend to perform developer tools operations programmatically. The API provides 116 endpoints covering core functionality including listplans, listorginvoices, bindskutoorg.

Call GET /api/v1/plans/ to listplans

Automated billing Management

Automate billing operations by combining multiple Quay Frontend endpoints. Agents can listorginvoices and then bindskutoorg in a single workflow.

Call GET /api/v1/organization/{orgname}/invoices to listorginvoices, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Quay Frontend endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.

Search Jentic for 'listplans', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

116 endpoints — this api allows you to perform many of the operations required to work with quay repositories, users, and organizations.

METHOD

PATH

DESCRIPTION

GET

/api/v1/plans/

listPlans

GET

/api/v1/organization/{orgname}/invoices

listOrgInvoices

POST

/api/v1/organization/{orgname}/marketplace

bindSkuToOrg

GET

/api/v1/organization/{orgname}/marketplace

listOrgSkus

POST

/api/v1/organization/{orgname}/marketplace/batchremove

batchRemoveSku

DELETE

/api/v1/organization/{orgname}/marketplace/{subscription_id}

removeSkuFromOrg

GET

/api/v1/user/marketplace

getUserMarketplaceSubscriptions

POST

/api/v1/repository/{repository}/build/

requestRepoBuild

GET

/api/v1/plans/

listPlans

GET

/api/v1/organization/{orgname}/invoices

listOrgInvoices

POST

/api/v1/organization/{orgname}/marketplace

bindSkuToOrg

GET

/api/v1/organization/{orgname}/marketplace

listOrgSkus

POST

/api/v1/organization/{orgname}/marketplace/batchremove

batchRemoveSku

DELETE

/api/v1/organization/{orgname}/marketplace/{subscription_id}

removeSkuFromOrg

GET

/api/v1/user/marketplace

getUserMarketplaceSubscriptions

POST

/api/v1/repository/{repository}/build/

requestRepoBuild

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Quay by hand means running its OAuth2 or bearer flow against quay.io, tracking the repo and org scopes it grants, and shaping each request yourself. Through Jentic you install once, import Quay from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Quay puts the organization name in the URL path (/organization/{orgname}/marketplace), so a rule can pin your agent to one organization: it can read invoices and marketplace entries there and nothing else. You choose the operations it may call, so destructive ones like removing a subscription are not included unless you add them.

Credential isolation

Your Quay credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list pricing plans' or 'read an organization's invoices', and Jentic returns the matching Quay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Quay Frontend API through Jentic.

What authentication does the Quay Frontend use?

The Quay Frontend uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I listplans with the Quay Frontend?

Yes. Use the GET /api/v1/plans/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Quay Frontend?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I listplans through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'listplans'. Jentic returns the matching Quay Frontend operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Quay Frontend have?

The Quay Frontend exposes 116 endpoints covering billing, build, capabilities operations.

Can I limit what my agent is allowed to do with the Quay Frontend API?

Yes. Because you run Jentic One yourself, your own rules decide which Quay operations and credentials the agent may use. Since Quay carries the organization name in the URL path, such as /organization/{orgname}/marketplace, you can pin the agent to a single organization and let it only read that organization's invoices and marketplace entries. You choose the exact operations it can call, so destructive ones like removing a subscription stay off limits unless you explicitly add them.

Quayio Quay Frontend

Name: Quay Frontend API
Brand: Quay Frontend
Availability: InStock

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer, oauth2116 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically listplans, listorginvoices. Covers 116 operations with bearer, oauth2 authentication.

Use for: I need to listplans, I want to listorginvoices, Search for bindskutoorg, Find all listorgskus

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

This API allows you to perform many of the operations required to work with Quay repositories, users, and organizations. The API exposes 116 endpoints secured with bearer, oauth2 authentication.

Jentic One on Github View OpenAPI Document