Install Jentic One Beta

Connect the WaiverFile API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WaiverFile 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%2Fwaiverfile.com%2Fwaiverfile" | sh

Step 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%2Fwaiverfile.com%2Fwaiverfile" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with WaiverFile API.

Check that the service is live

Get your WaiverSite details

Search waivers

Query and filter WaiverFile API records by parameters

Monitor WaiverFile API operational status and events

GET STARTED

Start building with WaiverFile API

Explore with Jentic One

View OpenAPI Document

Automated SMS Management

Automate sms operations by combining multiple WaiverFile API endpoints. Agents can get your waiversite details and then get an individual waiver in a single workflow.

Call GET /api/v1/GetSiteDetails to get your waiversite details, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'check that the service is live', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

17 endpoints — waiverfile is a digital waiver solution.

METHOD

PATH

DESCRIPTION

GET

/api/v1/Ping

Check that the service is live

GET

/api/v1/GetSiteDetails

Get your WaiverSite details

GET

/api/v1/GetWaiver

Get an individual waiver

GET

/api/v1/GetWaiverPDF

Get an individual waiver as PDF

GET

/api/v1/SearchWaivers

Search waivers

GET

/api/v1/GetWaiversByReferenceID

Get waivers by reference ID

GET

/api/v1/GetEventsByDateRange

Get events by date range

GET

/api/v1/GetUpcomingEvents

Get a list of upcoming events

GET

/api/v1/Ping

Check that the service is live

GET

/api/v1/GetSiteDetails

Get your WaiverSite details

GET

/api/v1/GetWaiver

Get an individual waiver

GET

/api/v1/GetWaiverPDF

Get an individual waiver as PDF

GET

/api/v1/SearchWaivers

Search waivers

GET

/api/v1/GetWaiversByReferenceID

Get waivers by reference ID

GET

/api/v1/GetEventsByDateRange

Get events by date range

GET

/api/v1/GetUpcomingEvents

Get a list of upcoming events

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the WaiverFile API by hand means passing your key as the apiKey query parameter on api.waiverfile.com and attaching it to every request yourself. Through Jentic you install once, import the WaiverFile API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The WaiverFile API exposes read operations that take identifiers as query parameters rather than fixed resource URL paths, so limit the agent to the operations it needs, such as searching waivers and fetching site details, and leave others out of the allowed set unless you add them.

Credential isolation

Your WaiverFile API key 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 'check that the service is live' or 'search signed waivers', and Jentic returns the matching WaiverFile API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using WaiverFile API through Jentic.

What authentication does the WaiverFile API use?

The WaiverFile API uses an API key passed in the `apiKey` query. 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 check that the service is live with the WaiverFile API?

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

What are the rate limits for the WaiverFile 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 check that the service is live through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check that the service is live'. Jentic returns the matching WaiverFile API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the WaiverFile API have?

The WaiverFile API exposes 17 endpoints covering sms, subscription, waiverevent operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which WaiverFile API operations and credentials your agent may use. Since these are read operations that take identifiers as query parameters, you can allow only the ones the agent needs, such as searching waivers or fetching your WaiverSite details, and leave others like retrieving waiver PDFs or events by date range out of the allowed set. Your API key is injected at execution time under those limits, so the agent can only call the operations you have permitted.

WaiverFile API

Name: WaiverFile API
Brand: WaiverFile API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsBilling SubscriptionsapiKey17 EndpointsREST

For Agents

Programmatically check that the service is live, get your waiversite details. Covers 17 operations with apiKey authentication.

Use for: I need to check that the service is live, I want to your waiversite details, Search for an individual waiver, Find all an individual waiver as pdf

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

WaiverFile is a digital waiver solution. This API allows management of waivers, events, subscriptions, and SMS subscribers. The API exposes 17 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the WaiverFile API to your agent

Capabilities

Start building with WaiverFile API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

WaiverFile API