Install Jentic One Beta

Connect the PassEntry API to your agent

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

Design pass templates with custom fields and visual layouts

Issue individual passes or batch-create thousands simultaneously

Send push notifications directly to passes in user wallets

Configure NFC readers for contactless pass scanning and validation

Track scan events with timestamps and reader location data

GET STARTED

Start building with PassEntry API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PassEntry API for, with concrete tasks.

★ Event Ticketing with Digital Passes

Create and distribute digital event tickets directly to attendees' Apple Wallet or Google Wallet through the PassEntry API. Design a pass template with event branding, issue individual passes with unique barcodes or QR codes, and validate entry using NFC readers or scan endpoints. Each pass supports real-time updates for gate changes, time modifications, or cancellation notices pushed directly to the wallet.

Create a pass template for 'Summer Concert 2026' via POST /api/v1/pass-templates, then issue a pass for attendee email user@example.com via POST /api/v1/passes with the template ID

Loyalty Card Program Management

Issue digital loyalty cards that live in customers' mobile wallets and update in real time as points accumulate or tier status changes. The PassEntry API provides dedicated loyalty endpoints for reading and updating point balances, plus push notifications to alert cardholders of rewards milestones. Eliminates physical card production and enables instant program enrollment at point of sale.

Retrieve loyalty pass details via GET /api/v1/loyalty/{id}, update the points balance via PATCH /api/v1/loyalty/{id}, then send a notification via POST /api/v1/passes/{id}/notification

Batch Pass Issuance for Large Events

Generate hundreds or thousands of unique digital passes in a single batch operation using the PassEntry API. Upload attendee data, specify the template, and monitor batch job progress through status endpoints. Each pass receives a unique identifier and barcode, and the batch can be cancelled mid-processing if needed. Suitable for conference registration, stadium events, or membership renewals.

Submit a batch pass creation job for 200 attendees via POST /api/v1/passes/batch with the template ID and attendee data, then check status via GET /api/v1/batches/{id}

AI Agent Pass Management via Jentic

AI agents issue and manage digital wallet passes through Jentic without handling Bearer token authentication directly. Jentic stores the API key securely and provides operation discovery by intent, letting agents create passes, send notifications, or check scan status by describing what they need. This eliminates the need to read PassEntry documentation or manage token headers manually.

Search Jentic for 'create a digital wallet pass', load the PassEntry pass creation schema, and execute with template ID and recipient details

Key Endpoints

38 endpoints — jentic publishes the only available openapi specification for passentry api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/passes

Create a new digital pass

POST

/api/v1/pass-templates

Create a pass template

POST

/api/v1/passes/batch

Batch create multiple passes

POST

/api/v1/passes/{id}/notification

Send push notification to a pass

POST

/api/v1/scans

Record a pass scan event

PATCH

/api/v1/loyalty/{id}

Update loyalty card points

GET

/api/v1/batches/{id}

Check batch job status

POST

/api/v1/webhook-subscriptions

Subscribe to pass lifecycle events

POST

/api/v1/passes

Create a new digital pass

POST

/api/v1/pass-templates

Create a pass template

POST

/api/v1/passes/batch

Batch create multiple passes

POST

/api/v1/passes/{id}/notification

Send push notification to a pass

POST

/api/v1/scans

Record a pass scan event

PATCH

/api/v1/loyalty/{id}

Update loyalty card points

GET

/api/v1/batches/{id}

Check batch job status

POST

/api/v1/webhook-subscriptions

Subscribe to pass lifecycle events

Why Jentic?

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

Setup

Wiring the PassEntry API by hand means learning its bearer token auth and webhook signature header, setting the api.passentry.com host, and building batch and notification handling yourself. Through Jentic you install once, import PassEntry from the API Directory, store the token once, and your agent calls it.

Permission scoping

PassEntry puts the pass id in the URL path (/api/v1/passes/{id}/...), so a rule can pin your agent to a named pass for actions like sending its notification. You choose the operations it may call, so creating passes, batch creation, or webhook subscriptions are not included unless you add them.

Credential isolation

Your PassEntry 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a digital event pass' or 'send a pass notification', and Jentic returns the matching PassEntry operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PassEntry API through Jentic.

Why is there no official OpenAPI spec for PassEntry API?

PassEntry does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PassEntry API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the PassEntry API use?

The API uses Bearer token authentication for standard operations (passed in the Authorization header) and a separate X-Webhook-Signature header for verifying incoming webhook payloads. Through Jentic, Bearer tokens are stored encrypted and agents authenticate without exposing tokens in their context.

Can I create passes for both Apple Wallet and Google Wallet?

Yes. The PassEntry API generates passes compatible with both Apple Wallet and Google Wallet from a single pass template. You design the template once and the platform handles format conversion for each wallet type.

How do I send a push notification to a pass holder?

Call POST /api/v1/passes/{id}/notification with the notification content in the request body. The message is delivered directly to the pass in the user's wallet app. You can also send wallet-level messages via POST /api/v1/entities/{entity_id}/messaging/wallet.

What is the batch pass creation limit?

The API supports batch creation via POST /api/v1/passes/batch and batch updates via POST /api/v1/passes/batch/update. Monitor job progress with GET /api/v1/batches/{id}. Specific batch size limits depend on your PassEntry plan tier.

How do I validate a pass scan through Jentic?

Search Jentic for 'record pass scan event' to find the POST /api/v1/scans operation. Load the schema to see required fields (pass ID, reader ID, timestamp), then execute. You can also retrieve scan history via GET /api/v1/scans. Install with pip install jentic.

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

Yes. Because you run Jentic One yourself, your own rules decide which PassEntry operations and credentials the agent may use, so it can only call the endpoints you explicitly grant. You choose the operations it may run, meaning creating passes via POST /api/v1/passes, batch creation via POST /api/v1/passes/batch, or webhook subscriptions are excluded unless you add them. Since PassEntry puts the pass id in the URL path, such as /api/v1/passes/{id}/notification, a rule can also pin the agent to a single named pass for actions like sending its push notification.

PassEntry API

Name: PassEntry API
Brand: PassEntry API
Availability: InStock

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticE CommerceOrder Managementbearer, apiKey38 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create and manage digital wallet passes for Apple Wallet and Google Wallet. Issue event tickets, loyalty cards, and membership passes individually or in batches, with NFC scanning and push notification support.

Use for: I need to create a digital event ticket for Apple Wallet, I want to send a push notification to all loyalty cardholders, Issue a batch of 500 membership passes, Check whether a pass has been scanned at the venue

Not supported: Does not handle payment processing, event scheduling, or venue management - use for digital pass creation, distribution, and validation only.

Jentic publishes the only available OpenAPI specification for PassEntry API, keeping it validated and agent-ready. The PassEntry API enables creation and management of digital passes for Apple Wallet and Google Wallet, covering event tickets, loyalty cards, boarding passes, and membership credentials. It provides 38 endpoints for pass template design, individual and batch pass issuance, NFC reader configuration, scan validation, wallet push notifications, and webhook-based lifecycle events.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D-Signals: 4

64%

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

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: BSignals: 4

27%

Example Density

How richly the API is illustrated with examples.

93%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

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

93%

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: CSignals: 4

59%

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.

57%

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: CSignals: 1

55%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PassEntry API to your agent

Capabilities

Start building with PassEntry API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PassEntry API

Jentic AI Readiness Score

PassEntry 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