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

# Useanvil Anvil API

Anvil provides APIs for PDF generation, PDF filling, and e-signature collection. Build document workflows with features like fillable PDFs, dynamic generation, and embedded signing experiences. The API exposes 2 endpoints secured with basic authentication.

## For AI agents

Programmatically fill pdf template, generate pdf. Covers 2 operations with basic authentication.

## Scope

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

## Capabilities

- Fill PDF Template
- Generate PDF
- Integrate Anvil API into automated workflows
- Query and filter Anvil API records by parameters
- Monitor Anvil API operational status and events

## Use cases

### Developer Tools Operations

Use the Anvil API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including fill pdf template, generate pdf.

Example prompt: Call POST `/fill/{pdfTemplateID}.pdf` to fill pdf template

### Data Retrieval and Monitoring

Query Anvil API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Anvil API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/fill/{pdfTemplateID}.pdf` | Fill PDF Template |
| POST | `/generate-pdf` | Generate PDF |

## Key resources

- **Fill** — Operations for fill
- **Generate Pdf** — Operations for generate pdf

## 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:** 41 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/useanvil.com/useanvil/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 the Anvil API by hand means setting up its basic auth, base64-encoding the credential on every request, and posting fill and generate-PDF payloads yourself. Through Jentic you install once, import Anvil from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Anvil puts the PDF template id in the URL path (`/fill/{pdfTemplateID}.pdf`), so a rule can pin your agent to one template: it can fill that template and nothing else. You choose the operations it may call, so ad-hoc PDF generation is not included unless you add it.
- **Credential handling:** Your Anvil 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 'fill a PDF template' or 'generate a PDF', and Jentic returns the matching Anvil 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 Anvil API use?

The Anvil API uses HTTP Basic authentication with username and password. 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 fill pdf template with the Anvil API?

Yes. Use the POST `/fill/{pdfTemplateID}.pdf` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Anvil 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 fill pdf template through Jentic?

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

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

The Anvil API exposes 2 endpoints covering fill, generate pdf operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Anvil operations the agent may call and which credential it uses, so you can allow POST `/fill/{pdfTemplateID}.pdf` while withholding POST /generate-pdf. Since Anvil carries the template id in the path (`/fill/{pdfTemplateID}.pdf`), a rule can pin the agent to a single template, letting it fill that one document and nothing else. The stored Anvil credential is injected only for the operations you have approved, so any call outside that scope simply is not available to the agent.