Install Jentic One Beta

Connect the Remy Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Remy Public 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%2Fremyrewards.co.uk%2Fremyrewards" | 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%2Fremyrewards.co.uk%2Fremyrewards" | 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 Remy Public API.

Record an order against a customer's email so it counts toward Remy loyalty

Give stamps or points on a customer's loyalty card, optionally tagged with a locationId

Give a reward to a customer and redeem it at the till

Issue a voucher from a template and email it to the recipient

Look up a voucher by its code and redeem an amount against it

GET STARTED

Start building with Remy Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Remy Public API for, with concrete tasks.

★ Agent-run loyalty desk

Your agent answers staff or customer questions about a Remy loyalty programme. It finds the customer by email, reads their loyalty state and cards, and gives stamps or points when a purchase was missed, so routine loyalty fixes happen in chat instead of in the merchant dashboard.

Call GET /v1/public/customers with email set to the customer's address, then POST /v1/public/customers/{customerId}/cards/{cardId}/stamps with quantity set to 1 and a unique Idempotency-Key header

Feed orders into the loyalty programme

When an online or in-store sale completes, the order is posted to Remy with customer_email, order_value, and order_source (plus an optional order_number and coupon_code) and an Idempotency-Key header, so retries never double-count a purchase.

Call POST /v1/public/orders/create with customer_email, order_value set to 24.50, order_source set to 'web', and a unique Idempotency-Key header

Gift voucher issuing and redemption

An agent issues a voucher from a voucher template by voucherTemplateId, optionally setting value, recipientEmail, and send so Remy emails it. At redemption it looks up the voucher by code, redeems an amount, and can adjust the remaining value or cancel the voucher with a reason.

Call GET /v1/public/vouchers/lookup with code set to the voucher code, then POST /v1/public/vouchers/{id}/redeem with amount set to 10 and an Idempotency-Key header

Reward fulfilment at the till

Rewards a customer has earned are listed per customer and redeemed with the customer reward operation, optionally recording the locationId of the branch. Rewards can also be given directly by rewardId for goodwill gestures.

Call GET /v1/public/customers/{customerId}/rewards, then POST /v1/public/customers/{customerId}/rewards/{rewardId}/redeem with the branch locationId and a unique Idempotency-Key header

Key Endpoints

35 endpoints — the remy public api connects a merchant's till, online shop, or booking system to their remy loyalty programme.

METHOD

PATH

DESCRIPTION

POST

/v1/public/orders/create

Process an order

GET

/v1/public/customers/{id}/loyalty

Get customer loyalty

POST

/v1/public/customers/{customerId}/cards/{cardId}/stamps

Give stamps

POST

/v1/public/customers/{customerId}/cards/{cardId}/points

Give points

POST

/v1/public/vouchers

Issue voucher

GET

/v1/public/vouchers/lookup

Look up voucher by code

POST

/v1/public/vouchers/{id}/redeem

Redeem voucher

POST

/v1/public/customers/{customerId}/rewards/{rewardId}/redeem

Redeem customer reward

POST

/v1/public/orders/create

Process an order

GET

/v1/public/customers/{id}/loyalty

Get customer loyalty

POST

/v1/public/customers/{customerId}/cards/{cardId}/stamps

Give stamps

POST

/v1/public/customers/{customerId}/cards/{cardId}/points

Give points

POST

/v1/public/vouchers

Issue voucher

GET

/v1/public/vouchers/lookup

Look up voucher by code

POST

/v1/public/vouchers/{id}/redeem

Redeem voucher

POST

/v1/public/customers/{customerId}/rewards/{rewardId}/redeem

Redeem customer reward

Why Jentic?

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

Setup

Wiring Remy by hand means sending the X-API-Key header, generating Idempotency-Key values for balance-changing calls, and paging customer and voucher lists with cursor and limit. Through Jentic you install once, import Remy from the API Directory, store the key once, and your agent calls it.

Permission scoping

Remy puts the customer id in the URL path (/v1/public/customers/{customerId}/...), so a rule can limit your agent to one customer's cards and rewards, and voucher operations carry the voucher id in the path too. You choose the operations it may call, so balance-changing ones like voucher cancellation or points adjustment are not included unless you add them.

Credential isolation

Your Remy 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 'give loyalty stamps' or 'redeem a gift voucher', and Jentic returns the matching Remy operation with its input schema so the agent sends the right fields and headers.

FAQs

Specific to using Remy Public API through Jentic.

What authentication does the Remy Public API use?

Per its OpenAPI spec, the Remy Public API authenticates with an API key from the merchant's Remy integration settings, sent in the X-API-Key header. GET /v1/public/auth verifies a key. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time.

Why do some Remy calls need an Idempotency-Key header?

Operations that change balances, such as processing an order, issuing or redeeming a voucher, and giving or redeeming rewards, take an Idempotency-Key header. Sending the same key on a retry stops a purchase or redemption from being applied twice.

Can I redeem a gift voucher by its code with the Remy API?

Yes. Call GET /v1/public/vouchers/lookup with the code to find the voucher, then POST /v1/public/vouchers/{id}/redeem with the amount to take off. POST /v1/public/vouchers/{id}/adjust sets a new remainingValue with a reason if a correction is needed.

What are the rate limits for the Remy Public API?

The OpenAPI spec does not state a numeric limit, though its operations declare a TooManyRequests response when you exceed one, and GET /v1/public/usage reports your key's API usage. Check https://developer.remyrewards.co.uk for current limits.

Is there a Remy Rewards MCP server?

You don't need an MCP server to give your agent Remy. Jentic connects it directly from the API Directory: import it, store your X-API-Key once, and your agent calls it. 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 Remy Public API?

Yes. A customer-service agent could be allowed to read customers and give stamps under /v1/public/customers/{customerId}/cards/{cardId}/stamps, while voucher cancel, voucher adjust, and points adjust stay off its list. It can then fix a missed stamp but cannot change balances any other way, and every call is logged.

Remyrewards Remy Public API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingMarketing AutomationapiKey (X-API-Key header)35 EndpointsREST

For Agents

Record orders, give stamps and points, issue and redeem vouchers, and read customer loyalty state in a Remy loyalty programme. Authenticated with the X-API-Key header.

Use for: Give this customer 2 stamps on their coffee card, Look up the voucher with code GIFT-2024, Issue a £20 gift voucher and email it to the recipient, Retrieve the loyalty balance for customer 1234

Not supported: Does not handle card payments, point-of-sale checkout, or email marketing campaigns. Use for running a Remy loyalty programme's orders, stamps, points, rewards, and vouchers only.

The Remy Public API connects a merchant's till, online shop, or booking system to their Remy loyalty programme. Orders posted with a customer_email, order_value, and order_source feed the programme, and you can give stamps or points on a customer's loyalty card, give and redeem rewards, and issue, send, redeem, adjust, or cancel vouchers. Read operations return customers with their loyalty state, the merchant's card, reward, and voucher templates, and the API key's own identity and usage.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

90%

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

13%

Example Density

How richly the API is illustrated with examples.

92%

Example Validity

Percentage of examples that conform to their schemas.

51%

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

50%

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.

51%

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

50%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Remy Public API to your agent

Capabilities

Start building with Remy Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Remyrewards Remy Public API

Jentic AI Readiness Score

Remy Public 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