Install Jentic One Beta

Connect the MemberArea API to your agent

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

Enroll a member in a course, mark individual lessons complete, and read each member's course progress

Build course content by creating lessons in a module, adding pages and typed elements, and turning a meeting recording into a lesson

Grant or revoke a member's bundle access, attach tags, assign roles, and set custom field values

Issue a single-use login link that signs a member in and drops them on a chosen page

GET STARTED

Start building with MemberArea API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MemberArea API for, with concrete tasks.

★ Agent-run member onboarding through Jentic

When a sale lands, an agent onboards the buyer inside MemberArea without a human clicking through the admin. Through Jentic it creates the member, grants the purchased bundle, enrolls them in the starter course, and issues a one-time login link to send in a welcome email. Your API key stays in your own Jentic One instance, and your rules decide which of these member and course operations the agent may run.

Call POST /members to create the member, POST /members/{memberUuid}/bundles/{bundleUuid} to grant the bundle, POST /courses/{courseUuid}/enrollments with the member id, then POST /members/{memberId}/login-link and return the link

Course progress tracking and nudges

Course creators want to know who stalled. The API lists the members enrolled in a course and each member's progress per course, so an agent can find members who have not completed a course and send them a nudge. When a member finishes work offline, the lesson-completion operation marks a specific lesson complete for them, which requires the member id in the body.

Call GET /courses/{courseUuid}/members for the course, then GET /members/{memberUuid}/courses/{courseUuid} for each member, and list members whose progress is not complete

Event registration and check-in

For live workshops and cohort calls, the API registers members for an event, cancels registrations, and checks attendees in. Combined with the event.registered and event.attended hook events, a CRM or spreadsheet stays in step with who signed up and who showed up.

Call GET /events to find the event titled 'Live Q&A', then POST /events/{eventUuid}/registrations for the member and POST /events/{eventUuid}/check-in when they join

Community moderation and recognition

Community managers keep forums healthy and reward contributors. The API lists and creates posts and comments across community areas and forums, and awards or revokes badges on a member, so an agent can welcome new posters, answer common questions, and recognise active members with a badge.

Call GET /community/posts to read recent posts, POST /community/posts/{post}/comments to reply to an unanswered one, and POST /community/badges/{badgeUuid}/members/{memberUuid} to award the 'Helper' badge

Key Endpoints

186 endpoints — the memberarea api runs a memberarea's courses, members, and community over rest, scoped to the memberarea that owns the key.

METHOD

PATH

DESCRIPTION

POST

/members

Create a member

GET

/members/by-email

Look up a member by email

POST

/courses/{courseUuid}/enrollments

Enroll a member in a course

GET

/members/{memberUuid}/courses

List a member's course progress

POST

/members/{memberUuid}/bundles/{bundleUuid}

Grant bundle access

POST

/members/{memberId}/login-link

Issue a one-time login link

POST

/events/{eventUuid}/registrations

POST

/hooks

Subscribe to an event

POST

/members

Create a member

GET

/members/by-email

Look up a member by email

POST

/courses/{courseUuid}/enrollments

Enroll a member in a course

GET

/members/{memberUuid}/courses

List a member's course progress

POST

/members/{memberUuid}/bundles/{bundleUuid}

Grant bundle access

POST

/members/{memberId}/login-link

Issue a one-time login link

POST

/events/{eventUuid}/registrations

POST

/hooks

Subscribe to an event

Why Jentic?

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

Setup

Wiring MemberArea by hand means choosing between a mak_ key in X-Api-Key, the bearer form, or a full OAuth PKCE flow, requesting the right scopes per endpoint, paging with per_page and page, and backing off on per-key read and write buckets. Through Jentic you install once, import MemberArea from the API Directory, store the key once, and your agent calls it.

Permission scoping

MemberArea puts resource ids in the URL path, such as /courses/{courseUuid}/enrollments and /members/{memberUuid}/bundles/{bundleUuid}, so a rule can pin your agent to one course and the operations you pick. You choose the operations it may call, so destructive ones like deleting a member or a lesson are not included unless you add them.

Credential isolation

Your MemberArea 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 'enroll a member in a course' or 'award a badge', and Jentic returns the matching MemberArea operation with its input schema, so the agent finds the right call among the member, course, and community endpoints without browsing the reference docs.

FAQs

Specific to using MemberArea API through Jentic.

What authentication does the MemberArea API use?

Per its OpenAPI spec, the MemberArea API accepts an API key starting with mak_ sent in the X-Api-Key header, the same key as an Authorization bearer token, or an OAuth 2.0 authorization-code token with PKCE starting with mao_ for apps other MemberAreas connect, using a registered client_id at /oauth/authorize. Keys and tokens carry explicit scopes such as courses:write or members:read. A handful of endpoints, including the OAuth flow and the WordPress session checks, are not key-authenticated. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I enroll a member in a course and track their progress with the MemberArea API?

Yes. POST /courses/{courseUuid}/enrollments with the member id enrolls them, GET /members/{memberUuid}/courses/{courseUuid} returns their progress in that course, and POST /courses/{courseUuid}/lessons/{lessonUuid}/completion marks one lesson complete. GET /courses/{courseUuid}/members lists everyone enrolled.

What are the rate limits for the MemberArea API?

The OpenAPI spec states that requests are metered per API key at 600 reads/min, 120 writes/min, and 30 automation triggers/min, with daily caps on top. Exceeding a bucket returns 429 with a Retry-After header and X-RateLimit headers showing the remaining budget and reset time.

Is there a MemberArea MCP server?

You don't need an MCP server to give your agent MemberArea. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the member, course, and community operations it needs on demand, without loading the whole surface into its context.

How do I grant a member bundle access through Jentic?

Search Jentic for 'grant a member access to a bundle', load the POST /members/{memberUuid}/bundles/{bundleUuid} operation, and execute it with the member and bundle ids from GET /members/by-email and GET /bundles. DELETE on the same path revokes access. 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 MemberArea API?

Yes. For example, write a rule that allows only enrollment and lesson-completion calls under /courses/{courseUuid}/ for your onboarding course, plus the course-progress read, so the agent can enroll members and mark lessons done there but cannot touch other courses, delete members, or change orders. Every call it makes is logged for review.

How does pagination work in the MemberArea API?

List endpoints return 25 items by default. Pass per_page (up to 100) and page to page through results, and read page, per_page, total, and last_page from the meta object in each response.

MemberArea API

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyEducationLmsapiKey, bearer, oauth2186 EndpointsREST

For Agents

Enroll MemberArea members in courses, track and mark lesson progress, manage member tags, roles, and bundle access, moderate community posts, register members for events, and subscribe to events like order.paid or course.completed.

Use for: I need to enroll a new customer in the onboarding course, Find all members who have not finished the course yet, Grant this member access to the premium bundle, Look up a member by email and add the VIP tag

Not supported: Does not process card payments, host video streaming, or send bulk marketing email campaigns. Use for running MemberArea courses, members, community, and events only.

The MemberArea API runs a MemberArea's courses, members, and community over REST, scoped to the MemberArea that owns the key. It enrolls members in courses, marks lessons complete, builds lessons page by page from typed elements, and turns meeting recordings into lessons, while member records carry tags, custom field values, roles, bundle access, and one-time login links. The same surface covers community areas, forums, posts, comments, and badges, plus events with registration and check-in, orders and subscriptions, affiliate commissions, inbox tickets, datasets, automations, and REST-hook subscriptions for events such as order.paid and course.completed.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

91%

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

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

11%

Example Density

How richly the API is illustrated with examples.

100%

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

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

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

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D+Signals: 1

50%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: BSignals: 1

67%

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 MemberArea API to your agent

Capabilities

Start building with MemberArea API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MemberArea API

Jentic AI Readiness Score

MemberArea 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