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

# Usestencil Stencil API

API for generating images, PDFs, and managing templates with Stencil. The API exposes 18 endpoints secured with bearer authentication.

## For AI agents

Programmatically get account information, list available projects. Covers 18 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Get account information
- List available projects
- Copy template
- Create image synchronously
- Monitor Stencil API operational status and events

## Use cases

### Media and Content Operations

Use the Stencil API to perform media operations programmatically. The API provides 18 endpoints covering core functionality including get account information, list available projects, get specific project.

Example prompt: Call GET /account to get account information

### Automated Account Management

Automate account operations by combining multiple Stencil API endpoints. Agents can list available projects and then get specific project in a single workflow.

Example prompt: Call GET /projects to list available projects, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stencil API 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 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/account` | Get account information |
| GET | `/projects` | List available projects |
| GET | `/projects/{id}` | Get specific project |
| GET | `/projects/{project_id}/templates` | List templates |
| GET | `/templates/{id}` | Get specific template |
| POST | `/templates/{id}/copy` | Copy template |
| POST | `/images/sync` | Create image synchronously |
| POST | `/images` | Create image asynchronously |

## Key resources

- **Account** — Operations for account
- **Airtables** — Operations for airtables
- **Collections** — Operations for collections
- **Editor** — Operations for editor
- **Images** — Operations for images

## 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:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 79 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/usestencil.com/usestencil/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 Stencil by hand means learning its bearer token auth against api.usestencil.com and hand-coding calls for every project, template, and image operation. Through Jentic you install once, import Stencil from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Stencil puts the project and template ids in the URL path (`/projects/{id}`, `/templates/{id}`), so a rule can pin your agent to one project or template. You choose the operations it may call, so writes like copying a template or syncing images are not included unless you add them.
- **Credential handling:** Your Stencil bearer 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 'list image templates' or 'generate an image from a template', and Jentic returns the matching Stencil operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Stencil API use?

The Stencil API uses a Bearer token in the Authorization header. 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 get account information with the Stencil API?

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

### What are the rate limits for the Stencil API?

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 get account information through Jentic?

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

### How many endpoints does the Stencil API have?

The Stencil API exposes 18 endpoints covering account, airtables, collections operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Stencil operations and credentials the agent may use. Stencil puts project and template ids in the URL path, such as `/projects/{id}` and `/templates/{id}`, so you can pin the agent to a single project or template and hand it read-only calls like GET /account or GET /projects. Write operations such as POST `/templates/{id}/copy` or POST `/images/sync` stay out of reach until you explicitly add them.