Install Jentic One Beta

Connect the Slyp POS API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Slyp POS 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%2Fpos.api.slyp.com.au%2Fslyp-pos" | 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%2Fpos.api.slyp.com.au%2Fslyp-pos" | 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 Slyp POS API.

Look up a consumer's loyalty account and available_credit by phone_number, loyalty_id, or oauth_code

Sign a consumer up to a merchant loyalty program with program_id and phone_number

Open a POS transaction to get points earned and loyalty-adjusted basket prices, then update it as items change

Record a points payment against a transaction and cancel it by payment_xref before finalising

GET STARTED

Start building with Slyp POS API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Slyp POS API for, with concrete tasks.

★ Agent-run POS integration testing through Jentic

A developer building a POS integration asks their agent to walk the full loyalty checkout flow against the Slyp sandbox. Through Jentic the agent finds each operation by intent, sends the bearer JWT and the required x-client header that your own instance supplies, and chains account lookup, transaction open, payment, and finalise. The developer gets a working end-to-end trace without hand-wiring the JWT exchange or the call order.

Call GET /account with loyalty_id, POST /transaction/open with the basket and loyalty, POST /transaction/{transaction_id}/payment with currency_value_redeemed 10, then POST /transaction/{transaction_id}/finalise including the payment_xref in other_payments

Points redemption at the register

When a member taps their card, the POS needs their balance and a way to spend it. GET /account returns available_credit for the loyalty_id, the payment operation locks the redeemed points against the open transaction, and finalising debits them and attributes new points. If the customer changes their mind, the payment is cancelled by payment_xref and the points unlock.

Fetch available_credit with GET /account?loyalty_id=L-123, record a redemption with POST /transaction/{transaction_id}/payment, and cancel it with POST /transaction/{transaction_id}/payment/{payment_xref}/cancel if the sale is abandoned

Digital receipts for every sale

A retailer wants every in-store purchase to produce a digital receipt the shopper can find later. POST /receipts accepts the basket, payment_data used to match the receipt to a consumer, the issuing pos_id and terminal tid, and an external_id to prevent duplicates. GET /receipt retrieves the stored receipt by external_id or transaction_id.

Submit a receipt with POST /receipts including pos_id POS_1, tid TERMINAL_1, and external_id RPT-123, then confirm it with GET /receipt?external_id=RPT-123

Refunds and exchanges after the sale

Returns happen days after purchase and must update both the receipt and the loyalty balance. POST /receipts/{receipt_xref}/adjust takes only the delta: refunded items with negative prices, refunded payments with negative amounts, and extra discounts as adjustment basket items, so the original receipt and points stay consistent.

Call POST /receipts/{receipt_xref}/adjust with a basket item priced -10.00 AUD to refund one returned item on receipt R-X-1236

Key Endpoints

12 endpoints — the slyp pos api connects a point-of-sale system to slyp digital receipts and merchant loyalty programs in australia.

METHOD

PATH

DESCRIPTION

POST

/authenticate

Get a bearer JWT

GET

/account

Look up a consumer's loyalty account

POST

/transaction/open

Open a transaction for a basket

POST

/transaction/{transaction_id}/payment

Record a points payment

POST

/transaction/{transaction_id}/finalise

Finalise the transaction

POST

/receipts

Submit a digital receipt

POST

/receipts/{receipt_xref}/adjust

Adjust a receipt for refunds or exchanges

GET

/receipt

Retrieve receipt details

POST

/authenticate

Get a bearer JWT

GET

/account

Look up a consumer's loyalty account

POST

/transaction/open

Open a transaction for a basket

POST

/transaction/{transaction_id}/payment

Record a points payment

POST

/transaction/{transaction_id}/finalise

Finalise the transaction

POST

/receipts

Submit a digital receipt

POST

/receipts/{receipt_xref}/adjust

Adjust a receipt for refunds or exchanges

GET

/receipt

Retrieve receipt details

Why Jentic?

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

Setup

Wiring Slyp by hand means exchanging the merchant apiKey and merchant id for a JWT at /authenticate, sending it as a bearer token with the x-client header on each call, picking the sandbox or production host, and getting the open, payment, finalise order right. Through Jentic you install once, import Slyp from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Slyp carries the consumer, merchant program, and basket in request bodies and query strings, so rules bound which operations your agent may call rather than which customer. You choose the operations it may call, so points-moving ones like recording a payment, finalising a transaction, or adjusting a receipt are not included unless you add them.

Credential isolation

Your Slyp merchant credentials and bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a loyalty member' or 'refund an item on a receipt', and Jentic returns the matching Slyp operation with its input schema, including required fields like program_id and x-client, so the agent calls the right step.

FAQs

Specific to using Slyp POS API through Jentic.

What authentication does the Slyp POS API use?

The Slyp POS API authenticates with a bearer JWT per its OpenAPI spec. The JWT comes from POST /authenticate, which takes the merchant's apiKey and merchant id in the request body, and the spec also declares a required x-client header naming the sending POS system, such as kosmos-pos-v1. Through Jentic the credentials are held by your own instance and attached at call time.

Can I redeem loyalty points with the Slyp POS API?

Yes. GET /account returns the consumer's available_credit, POST /transaction/{transaction_id}/payment records a redemption with currency_value_redeemed and returns a payment_xref, and POST /transaction/{transaction_id}/finalise debits the points once the payment_xref is included in other_payments. A payment can be cancelled first to unlock the points.

What are the rate limits for the Slyp POS API?

The OpenAPI spec does not specify rate limits for the Slyp POS API. Contact Slyp at dev@slyp.com.au, the support address named in the spec, for current limits before load testing against production.

Is there a sandbox for the Slyp POS API?

Yes. The spec lists https://pos.api.sandbox-slyp.com.au/v1 as the sandbox host alongside production at https://pos.api.slyp.com.au/v1, and each has its own /authenticate endpoint for issuing a JWT. Point the integration at the sandbox host while testing the transaction flow.

Is there a Slyp MCP server?

You don't need an MCP server to give your agent Slyp. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the account, transaction, and receipt operations it needs, discovered on demand instead of loaded into its context up front.

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

Yes. For example, allow only GET /account and GET /receipt, and the agent can look up members and read receipts but cannot open transactions, redeem points, or adjust receipts. Each call the agent makes is logged, so a reporting task stays read-only and reviewable.

How do I submit a receipt with Slyp through Jentic?

Search Jentic for 'submit a digital receipt', load the POST /receipts operation, and send the basket items, payment_data, pos_id, tid, and an external_id to prevent duplicates. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Pos Api Slyp Slyp POS API

AI ReadinessFoundational (C)57/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsPos Terminalbearer12 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Look up and enrol loyalty members, open and finalise POS transactions with points redemption, and submit or adjust Slyp digital receipts.

Use for: Look up a loyalty member by their phone number, I need to sign a customer up to the rewards program at checkout, Open a transaction to see how many points this basket earns, Record a points redemption for the current purchase

Not supported: Does not process card payments, settle funds, or manage product inventory. Use for POS loyalty transactions and Slyp digital receipts only.

The Slyp POS API connects a point-of-sale system to Slyp digital receipts and merchant loyalty programs in Australia. A POS looks up a consumer by phone number, loyalty id, or OAuth code, signs them up to a program, and opens a transaction to get the points earned and loyalty-adjusted prices for the basket. It then records points redemptions as payments, finalises or cancels the transaction, and submits the receipt, with a separate adjust operation for refunds, exchanges, and extra discounts after the sale. A sandbox host mirrors production for integration testing.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

30%

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

32%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

75%

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

66%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

52%

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

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Slyp POS API to your agent

Capabilities

Start building with Slyp POS API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Pos Api Slyp Slyp POS API

Jentic AI Readiness Score

Slyp POS 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