Install Jentic One Beta

Connect the Annex Cloud Loyalty API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Annex Cloud Loyalty 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%2Fs15socialannex.net%2Fs15socialannex" | 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%2Fs15socialannex.net%2Fs15socialannex" | 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 Annex Cloud Loyalty API.

Create a user and enroll in loyalty program

Retrieve user profile details

Update user information

Fetch user activity history with pagination

Get current and next tier information

GET STARTED

Start building with Annex Cloud Loyalty API

Explore with Jentic One

View OpenAPI Document

Automated Users Management

Automate users operations by combining multiple Annex Cloud Loyalty API endpoints. Agents can retrieve user profile details and then update user information in a single workflow.

Call GET /users/{id} to retrieve user profile details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Annex Cloud Loyalty API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Search Jentic for 'create a user and enroll in loyalty program', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — annex cloud api v3.

METHOD

PATH

DESCRIPTION

POST

/users

Create a user and enroll in loyalty program

GET

/users/{id}

Retrieve user profile details

PATCH

/users/{id}

Update user information

GET

/users/{id}/activity

Fetch user activity history with pagination

GET

/users/{id}/usedreward

Retrieve redeemed rewards list

GET

/users/{id}/tiers

Get current and next tier information

GET

/users/{id}/reward

Retrieve available rewards for user

POST

/orders

Create a new order

POST

/users

Create a user and enroll in loyalty program

GET

/users/{id}

Retrieve user profile details

PATCH

/users/{id}

Update user information

GET

/users/{id}/activity

Fetch user activity history with pagination

GET

/users/{id}/usedreward

Retrieve redeemed rewards list

GET

/users/{id}/tiers

Get current and next tier information

GET

/users/{id}/reward

Retrieve available rewards for user

POST

/orders

Create a new order

Why Jentic?

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

Setup

Wiring the Annex Cloud Loyalty API by hand means managing its API key and bearer token, attaching them to each call against s15.socialannex.net, and handling your own retries. Through Jentic you install once, import the Annex Cloud Loyalty API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Annex Cloud puts the user id in the URL path (/users/{id}/...), so a rule can pin your agent to one user: it can read that user's activity, tiers, and rewards and nothing else. You choose the operations it may call, so updating a user or placing an order is not included unless you add it.

Credential isolation

Your Annex Cloud Loyalty API credentials 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 'enroll a user in the loyalty program' or 'check a user's reward tier', and Jentic returns the matching Annex Cloud Loyalty API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Annex Cloud Loyalty API through Jentic.

What authentication does the Annex Cloud Loyalty API use?

The Annex Cloud Loyalty API uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create a user and enroll in loyalty program with the Annex Cloud Loyalty API?

Yes. Use the POST /users endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Annex Cloud Loyalty API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a user and enroll in loyalty program through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a user and enroll in loyalty program'. Jentic returns the matching Annex Cloud Loyalty API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Annex Cloud Loyalty API have?

The Annex Cloud Loyalty API exposes 14 endpoints covering users, orders, points operations.

Can I limit what my agent is allowed to do with the Annex Cloud Loyalty API?

Yes. Because you run Jentic One yourself, your own rules decide which Annex Cloud operations and credentials the agent may use. Since Annex Cloud puts the user id in the URL path (/users/{id}/...), you can pin the agent to a single user and let it only read that user's activity, tiers, and rewards. Updating a user profile or placing an order stays out of reach unless you explicitly add those operations.

S15socialannex Annex Cloud Loyalty API

Name: Annex Cloud Loyalty API
Brand: Annex Cloud Loyalty API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Community OpenAPI document · agent-readyMarketingSeo SemapiKey, bearer14 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically create a user and enroll in loyalty program, retrieve user profile details. Covers 14 operations with apiKey, bearer authentication.

Use for: I need to a user and enroll in loyalty program, I want to user profile details, Search for user information, Find all fetch user activity history with pagination

Not supported: Does not handle payments, communications, or crm - use for marketing only.

Annex Cloud API v3.0 for loyalty program management including users, orders, points, rewards, segments, and campaigns. The API exposes 14 endpoints secured with apiKey, bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 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).

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

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

62%

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 Annex Cloud Loyalty API to your agent

Capabilities

Start building with Annex Cloud Loyalty API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

S15socialannex Annex Cloud Loyalty API

Jentic AI Readiness Score

Annex Cloud Loyalty 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