Install Jentic One Beta

Connect the Festival API to your agent

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

List and filter film festivals via GET /festivals/

Read a single festival's full detail, including fees, deadlines, and platforms, via GET /festivals/{id}/

Read a festival's programming roster and programming profile via GET /festivals/{id}/roster/ and GET /festivals/{id}/programming-profile/

Rank the top composite-scored festivals via GET /festivals/scored/

GET STARTED

Start building with Festival API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Festival API for, with concrete tasks.

★ AI agent festival recommender

An AI assistant helps a filmmaker decide where to submit by pulling live festival data on demand. Through Jentic it filters festivals, reads their deadlines and fees, and ranks the top-scored options, then returns a shortlist with the next deadlines. Jentic injects the Festival API key at call time, so the agent never holds the credential.

Search Jentic for 'find film festivals to submit to', call GET /festivals/ with filters, read GET /festivals/scored/ for ranking, and summarise the shortlist with each festival's next deadline

Submission deadline tracking

Filmmakers miss festivals because deadlines creep up across dozens of events. The Festival API surfaces the deadlines closing soon and the fee tiers behind each one, so a tracker can remind a user before a window closes. Reading one festival's detail returns its full deadline and platform information.

Call GET /deadlines/closing-soon/ to find imminent deadlines, then read GET /festivals/{id}/ for each to confirm its fee tiers and submission platforms

Festival discovery and filtering

A discovery experience lets users browse festivals by category, country, and state and drill into any one. The Festival API exposes the category, country, and state reference lists alongside a filterable festival list, so a frontend can build facet filters that map to real data. Each festival detail includes the roster and programming profile for deeper context.

Call GET /categories/, GET /countries/, and GET /states/ to build filters, then call GET /festivals/ with the chosen facets to list matching festivals

Score-based festival shortlist

When there are too many festivals to weigh by hand, a composite score helps rank them. The Festival API returns the top-scored festivals directly, so an agent can build a shortlist ordered by that score and then pull each festival's roster and programming profile to judge fit. This turns a sprawling list into a ranked, explainable set.

Call GET /festivals/scored/ for the ranked list, then read GET /festivals/{id}/programming-profile/ for the top entries to judge programming fit

Key Endpoints

11 endpoints — the festival api aggregates film-festival data into a single json surface: submission deadlines, categories and genres, standard submission fees, submission platforms, past winners, programming rosters, and a composite score.

METHOD

PATH

DESCRIPTION

GET

/festivals/

List festivals

GET

/festivals/{id}/

Get festival detail

GET

/festivals/{id}/roster/

Get festival roster

GET

/festivals/scored/

Get top-scored festivals

GET

/deadlines/closing-soon/

Get deadlines closing soon

GET

/festivals/{id}/programming-profile/

Get a festival's programming profile

GET

/calendar/

Get the festival calendar feed

GET

/categories/

List categories

GET

/festivals/

List festivals

GET

/festivals/{id}/

Get festival detail

GET

/festivals/{id}/roster/

Get festival roster

GET

/festivals/scored/

Get top-scored festivals

GET

/deadlines/closing-soon/

Get deadlines closing soon

GET

/festivals/{id}/programming-profile/

Get a festival's programming profile

GET

/calendar/

Get the festival calendar feed

GET

/categories/

List categories

Why Jentic?

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

Setup

Wiring the Festival API by hand means managing its bearer key, remembering the trailing-slash paths, and stitching the reference lists into festival filters yourself. Through Jentic you install once, import the Festival API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Festival API is read-only, so a rule can allow your agent just the lookups it needs: the festival list, a festival read by the id in its path, or the scored and deadline feeds. You choose the operations it may call, and because nothing writes, the agent can only read festival data.

Credential isolation

Your Festival 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 'find film festivals to submit to' or 'festival deadlines closing soon', and Jentic returns the matching Festival API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Festival API through Jentic.

What authentication does the Festival API use?

The Festival API authenticates with a bearer API key issued from your Festival API dashboard, sent as a Bearer token, per its OpenAPI spec. When you call it through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt, logs, or context.

Can I filter festivals by category or country with the Festival API?

Yes. Build your facets from GET /categories/, GET /countries/, and GET /states/, then call GET /festivals/ with the chosen filters to list matching festivals. Each festival's full detail, including fees and deadlines, comes back from GET /festivals/{id}/.

Can the Festival API tell me which deadlines are closing soon?

Yes. Call GET /deadlines/closing-soon/ for the festivals whose submission windows are near, and read GET /festivals/{id}/ for each one to see its full deadline and fee information. A calendar feed is also available from GET /calendar/.

What are the rate limits for the Festival API?

The OpenAPI spec does not specify rate limits for the Festival API. Check the Festival API documentation for current limits, cache reference lists like categories and countries, and have your agent back off when the API signals that it is being throttled.

How do I find festivals to submit to through Jentic?

Search Jentic for 'find film festivals to submit to' to load the Festival API operations with their input schemas, call GET /festivals/ with your filters, and rank results with GET /festivals/scored/. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. The Festival API is read-only, so a rule can allow your agent just the lookups it needs, such as listing festivals, reading one by the id in its path, or the scored and deadline feeds. Because nothing writes, the agent can only read festival data, and every call it makes is logged.

Festival API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer11 EndpointsREST

For Agents

Search and discover film festivals through the Festival API: list and filter festivals, read a festival's detail, roster, and programming profile, rank the top-scored festivals, and check deadlines closing soon.

Use for: Find film festivals accepting documentary submissions, Get the submission deadline and fee for a festival, List the top-scored film festivals, Check which festival deadlines are closing soon

Not supported: Does not handle submitting films, processing submission payments, or managing a festival's back office. Use for reading and discovering film-festival data such as deadlines, fees, rosters, and scores only.

The Festival API aggregates film-festival data into a single JSON surface: submission deadlines, categories and genres, standard submission fees, submission platforms, past winners, programming rosters, and a composite score. It lists and filters festivals, returns the full detail for one festival including its roster and programming profile, and ranks the top-scored festivals. Supporting endpoints expose categories, countries, states, a calendar feed, and the deadlines closing soon. Authentication uses a bearer API key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

86%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

75%

Example Validity

Percentage of examples that conform to their schemas.

48%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

29%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Festival API to your agent

Capabilities

Start building with Festival API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Festival API

Jentic AI Readiness Score

Festival API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness