Install Jentic One Beta

Connect the LoyaltyDog to your agent

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

Enrol a customer in a loyalty program with firstName, lastName, email, phone, and starting points via POST /v2/loyalty/programs/{programId}/customers

Add reward points to a customer's account through POST /v2/loyalty/programs/{programId}/customers/{customerId}/points/add

Publish, cancel, or duplicate program offers and let a customer claim one through the offers/{offerId}/claim operation

Push a message to every consenting pass holder in a program via POST /v2/loyalty/programs/{programId}/customers/push

GET STARTED

Start building with LoyaltyDog API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LoyaltyDog API for, with concrete tasks.

★ Point-of-sale loyalty agent through Jentic

A store assistant agent awards points after each purchase. It searches Jentic for 'add loyalty points to a customer', receives the LoyaltyDog points operation with its input schema, finds the customer by email with the customers list operation, and posts the points to POST /v2/loyalty/programs/{programId}/customers/{customerId}/points/add. The updated points total comes back in the response, so the agent can tell the customer their new balance.

Call GET /v2/loyalty/programs/{programId}/customers with email 'ana@example.com', then POST /v2/loyalty/programs/{programId}/customers/{customerId}/points/add with points 50 and report the new total

Wallet pass promotions

Announce a weekend offer straight to customers' phones. The merchant publishes an offer with POST /v2/loyalty/programs/{programId}/offers/{offerId}/publish, then sends a message with the program-wide push operation. The response reports recipients and members, so the merchant sees how many pass holders granted marketing consent and actually receive the notification.

Publish the offer with POST /v2/loyalty/programs/{programId}/offers/{offerId}/publish, then call POST /v2/loyalty/programs/{programId}/customers/push with message 'Double points this weekend' and report recipients versus members

Gift card issuance and redemption

Run a gift card program next to the loyalty card. POST /v2/giftcards/programs/{programId}/cards/bulk issues multiple cards with an initialValue and returns a task to poll, while redeem, reload, and refund operations handle the card's lifecycle at the till with a posTransactionId and terminalId for reconciliation.

Call POST /v2/giftcards/programs/{programId}/cards/bulk with initialValue 25 and count 100, then poll GET /v2/giftcards/programs/{programId}/cards/bulk/{taskId} until the task completes

Consent and privacy requests

Keep marketing consent and data-subject requests in order. Consents are recorded per customer with a consentType such as marketing_email or marketing_sms, a method such as checkbox or pos_terminal, and a policyVersion, and a customer's data can be exported or a DSAR request created and tracked through its status.

Call POST /v2/loyalty/programs/{programId}/customers/{customerId}/consents with consentType marketing_sms, granted true, method checkbox, and the current policyVersion

Key Endpoints

257 endpoints — the loyaltydog api runs digital loyalty programs delivered as wallet passes, letting a merchant enrol customers, add reward points, publish offers and vouchers, and push messages to the passes on customers' phones.

METHOD

PATH

DESCRIPTION

POST

/v2/token

POST

/v2/loyalty/programs/{programId}/customers

Enrol a customer in a program

POST

/v2/loyalty/programs/{programId}/customers/{customerId}/points/add

Add reward points to a customer

POST

/v2/loyalty/programs/{programId}/customers/push

Push a message to all consenting pass holders

POST

/v2/loyalty/programs/{programId}/offers/{offerId}/publish

Publish an offer

POST

/v2/giftcards/programs/{programId}/cards/bulk

Issue multiple gift cards

GET

/v2/passes/{passTypeIdentifier}/{serialNumber}/savetowallet

Get the save-to-wallet URL for a pass

POST

/v2/webhooks

Create a webhook

POST

/v2/token

POST

/v2/loyalty/programs/{programId}/customers

Enrol a customer in a program

POST

/v2/loyalty/programs/{programId}/customers/{customerId}/points/add

Add reward points to a customer

POST

/v2/loyalty/programs/{programId}/customers/push

Push a message to all consenting pass holders

POST

/v2/loyalty/programs/{programId}/offers/{offerId}/publish

Publish an offer

POST

/v2/giftcards/programs/{programId}/cards/bulk

Issue multiple gift cards

GET

/v2/passes/{passTypeIdentifier}/{serialNumber}/savetowallet

Get the save-to-wallet URL for a pass

Why Jentic?

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

Setup

Wiring LoyaltyDog by hand means logging in through the OAuth2 password form at POST /v2/token, refreshing the JWT, handling MFA, and sending separate Eposn token headers on gift card routes. Through Jentic you install once, import LoyaltyDog from the API Directory, store your token once, and your agent calls it.

Permission scoping

LoyaltyDog puts the program id in the URL path (/v2/loyalty/programs/{programId}/...), so a rule can pin your agent to one loyalty program and the operations you pick. You choose the operations it may call, so destructive ones like customer purge or gift card void are not included unless you add them.

Credential isolation

Your LoyaltyDog 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 'add loyalty points to a customer' or 'issue gift cards', and Jentic returns the matching LoyaltyDog operation with its input schema, out of 257, so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using LoyaltyDog API through Jentic.

What authentication does the LoyaltyDog API use?

Per its OpenAPI spec, the LoyaltyDog API uses an HTTP bearer JWT obtained by posting a username and password to POST /v2/token; MFA logins finish at POST /v2/token/mfa-verify. Gift card routes also accept X-Eposn-Customer-Token and X-Eposn-Merchant-Token headers, and a few routes such as signup and gift card balance checks need no token. Through Jentic, the token is stored encrypted by your own Jentic One instance and injected at execution time.

Can I add points to a customer with the LoyaltyDog API?

Yes. POST /v2/loyalty/programs/{programId}/customers/{customerId}/points/add takes a required points value and returns the updated customer with the new total. It accepts an Idempotency-Key header, so a retried request after a timeout does not award the points twice.

What are the rate limits for the LoyaltyDog API?

The OpenAPI spec does not publish a general rate limit. It states that the customer gift card balance check is rate limited to 5 requests per minute per IP, and warns that excessive push notifications can lead to rate limiting or blocking of your cards. See https://loyalty.dog/contact-us for current limits.

How do I send a push message to my loyalty customers through Jentic?

Install Jentic One, add the LoyaltyDog API from the Jentic directory, and store your token. Your agent searches for 'send a push message to loyalty customers', receives POST /v2/loyalty/programs/{programId}/customers/push with its message field, and the response reports recipients and members so you can see how many granted marketing consent. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Why did my LoyaltyDog push reach fewer customers than hold the pass?

Marketing consent is opt-in, so recipients counts only customers who answered yes, while members counts everyone holding the pass. The push operation returns HTTP 409 when the program requires consent but has nobody to send to, or when the audience already holds the same message, because wallet passes only notify when the text changes.

Is there a LoyaltyDog MCP server?

LoyaltyDog's spec links to its own MCP integration guide. You can also connect the LoyaltyDog API directly through Jentic: your agent gets the full 257-endpoint surface from the spec without loading another server's tool definitions into its context, your token is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

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

Yes. For a till assistant, allow only the customer lookup and points/add operations under your program's programId, so the agent can find a member and award points but cannot purge customers, push messages, or issue gift cards. The agent's calls are logged for review.

LoyaltyDog

AI ReadinessFoundational (D)43/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer (JWT from POST /v2/token); gift card routes also take X-Eposn-Customer-Token / X-Eposn-Merchant-Token headers257 EndpointsREST

For Agents

Enrol customers in a LoyaltyDog program, add points, publish offers and vouchers, push messages to wallet passes, and issue or redeem gift cards. Authenticates with a JWT bearer token.

Use for: I need to add 50 points to a customer's loyalty card, Enrol a new customer in our coffee shop loyalty program, Send a push message to every pass holder about this weekend's offer, List all customers in a loyalty program by email

Not supported: Does not process card payments, run an online storefront, or send email campaigns. Use for wallet-pass loyalty programs, points, offers, vouchers, and gift cards only.

The LoyaltyDog API runs digital loyalty programs delivered as wallet passes, letting a merchant enrol customers, add reward points, publish offers and vouchers, and push messages to the passes on customers' phones. Beyond loyalty cards it covers pass templates with branding and images, individual passes with save-to-wallet links and status, gift cards with issuance, reloads, redemptions, refunds, and fraud alerts, plus scanners, webhooks, and customer consent records. Calls authenticate with a JWT bearer token obtained from the token endpoint, and app keys can be created, rotated, and revoked for integrations.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

75%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

13%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

21%

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: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

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: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LoyaltyDog to your agent

Capabilities

Start building with LoyaltyDog API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

LoyaltyDog

Jentic AI Readiness Score

LoyaltyDog

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