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

# BeYourCover Partner API

The BeYourCover Partner API generates AI book covers for a book and refines them through variations, prompt-based edits, upscaling, and text removal. It builds print-ready KDP wraps with calculated spine and bleed dimensions, produces square audiobook versions, and accepts reference-image uploads to steer the look. Long-running generation returns a job to poll, and finished assets download on demand once credits are available.

## For AI agents

Generate, edit, and upscale AI book covers and full print wraps: create covers from a book's genre, produce variations, remove text, build KDP-ready wraps, and poll async jobs for finished assets across 24 endpoints.

## Scope

Does not print or ship physical books, sell them, or manage distribution to retailers. Use for generating and preparing book cover artwork only.

## Capabilities

- Generate AI book covers for a book from its genre and metadata
- Create variations of an existing cover and edit it with a text prompt
- Upscale a cover to print resolution and remove rendered text
- Build a full KDP print wrap and calculate its spine and bleed dimensions
- Generate a square audiobook version of a cover
- Generate a cover from uploaded reference images
- Poll long-running jobs and download finished cover assets

## Use cases

### Generate book covers through Jentic

Produce finished book covers from a book's genre and metadata without hand-wiring the async API. The agent creates a book record, submits a generation request, and polls the returned job until the cover assets are ready. Through Jentic the generation operation is discovered by intent and called with its input schema, so the whole flow runs in one place.

Example prompt: Create a book with POST `/api/v1/books`, generate its covers with POST `/api/v1/covers/generate`, then poll the result with GET `/api/v1/jobs/{jobId}`

### Cover variations and edits

Iterate on a chosen cover without regenerating from scratch. The agent requests variations of an existing cover, edits the image with a text prompt, or strips rendered text, so an author can refine the design across a few passes.

Example prompt: Request variations with POST `/api/v1/covers/{coverId}/variations`, then refine one with POST `/api/v1/covers/{coverId}/edit-image`

### Print-ready wrap production

Turn a chosen front cover into a print-ready paperback wrap. The agent calculates the KDP wrap dimensions for the trim size and page count, builds the full wrap, and re-typesets it as needed, so the file is ready for upload to a print-on-demand service.

Example prompt: Calculate dimensions with GET `/api/v1/wraps/calculate`, then create the wrap with POST `/api/v1/wraps`

### Audiobook cover variant

Produce a square audiobook cover from an existing book cover so the same artwork works across formats. The agent generates the square version from a chosen cover and downloads it once the job finishes.

Example prompt: Generate a square audiobook cover with POST `/api/v1/covers/{coverId}/audiobook-cover` and download it when the job completes

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/books` | Create a book record |
| POST | `/api/v1/covers/generate` | Generate covers for a book |
| POST | `/api/v1/covers/{coverId}/variations` | Generate variations of a cover |
| POST | `/api/v1/covers/{coverId}/upscale` | Upscale a cover to print resolution |
| POST | `/api/v1/wraps` | Create a full print wrap for a cover |
| GET | `/api/v1/wraps/calculate` | Calculate KDP wrap dimensions |
| GET | `/api/v1/jobs/{jobId}` | Poll a job's status and result |
| GET | `/api/v1/credits` | Get credit balance and plan |

## Key resources

- **Books** — Create and list book records that covers are generated for
- **Covers** — Generate, vary, edit, upscale, remove text from, and download cover assets
- **Wraps** — Calculate dimensions for, build, and re-render full print wraps for a cover
- **Jobs** — Poll long-running generation jobs for their status and result

## 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:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 88 / 100
- **View full report:** https://jentic.com/apis/beyourcover.com/beyourcover/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 BeYourCover by hand means learning its bearer auth, its asynchronous job-and-poll pattern, and presigned reference-image uploads. Through Jentic you install once, import BeYourCover from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** BeYourCover puts the cover id in the URL path (`/api/v1/covers/{coverId}/...`), so a rule can pin your agent to one cover: it can generate variations and upscales for that cover and nothing else. You choose which operations it may call, so credit-spending ones like generating new covers are not included unless you add them.
- **Credential handling:** Your BeYourCover token 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 'generate a book cover' or 'build a print wrap', and Jentic returns the matching BeYourCover operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **PhotoRoom API** — PhotoRoom generates and edits product and marketing images; BeYourCover is purpose-built for book covers and print wraps.
- **DynaPictures API** — DynaPictures renders images from templates and data; BeYourCover generates original AI cover artwork and sizes it for print.
- **Canva Connect API** — Canva assembles and exports designs; BeYourCover supplies the generated cover artwork you can bring into a layout.

## FAQ

### What authentication does the BeYourCover Partner API use?

The BeYourCover Partner API authenticates with a bearer token per its OpenAPI spec: send your partner key as `Authorization: Bearer byc_sk_...`. The liveness health check is public, while the cover, wrap, and job operations require the token. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

### Can I generate print-ready wraps with the BeYourCover Partner API?

Yes. Calculate the KDP wrap dimensions for your trim size and page count, create a full wrap for a chosen cover, and re-typeset or re-extend the front panel as needed. Finished wrap assets are available to download once the job completes.

### Can I limit what my agent is allowed to do with the BeYourCover Partner API?

Yes. BeYourCover puts the cover id in the URL path, so a rule can allow your agent to generate variations and upscales for one cover while blocking new book creation or wrap production unless you add those operations. Each run draws on the credit balance you can read separately.

### What are the rate limits for the BeYourCover Partner API?

The OpenAPI spec does not specify rate limits, though generation operations are asynchronous and metered by credits. Check the BeYourCover documentation at https://beyourcover.com for current limits.

### Is there a BeYourCover MCP server?

You don't need an MCP server to give your agent BeYourCover. Jentic connects it directly from the API Directory: import it, store your token once, and your agent runs the cover and wrap operations on demand. That also keeps extra tool definitions out of the agent's context.

### How do I generate a book cover with the BeYourCover Partner API through Jentic?

Search Jentic for 'generate a book cover' and it returns the cover-generation operation with its input schema. Your agent creates a book, submits the generation request, and polls the job until the cover assets are ready. To run it on your own infrastructure, install Jentic One from its GitHub repo.