canonical: https://jentic.com/apis/quayio/quayio

# Quayio Quay Frontend

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.

## For AI agents

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

## Scope

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

## Capabilities

- listPlans
- listOrgInvoices
- bindSkuToOrg
- listOrgSkus
- batchRemoveSku
- removeSkuFromOrg
- getUserMarketplaceSubscriptions

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **billing** — Operations related to billing
- **build** — Operations related to build
- **capabilities** — Operations related to capabilities
- **discovery** — Operations related to discovery
- **error** — Operations related to error

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 58 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 39 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 70 / 100
  - Agent Usability: 80 / 100
  - Security: 48 / 100
  - AI Discoverability: 57 / 100
- **View full report:** https://jentic.com/apis/quayio/quayio/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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