Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Anvil API, 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%2Fuseanvil.com%2Fuseanvil" | shStep 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%2Fuseanvil.com%2Fuseanvil" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Anvil API.
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
GET STARTED
Patterns agents use Anvil API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'fill pdf template', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — anvil provides apis for pdf generation, pdf filling, and e-signature collection.
METHOD
PATH
DESCRIPTION
/fill/{pdfTemplateID}.pdf
Fill PDF Template
/generate-pdf
Generate PDF
/fill/{pdfTemplateID}.pdf
Fill PDF Template
/generate-pdf
Generate PDF
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Anvil API through Jentic.
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.
For Agents
Programmatically fill pdf template, generate pdf. Covers 2 operations with basic authentication.
Use for: I need to fill pdf template, I want to generate pdf, Get the current status of Anvil API resources, List all records from Anvil API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
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.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>