Install Jentic One Beta

Connect the Raklet API to your agent

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

Search an organisation's contacts with a base64-encoded q filter and page through them with pageSize and offset

Create a contact with firstName, lastName, and language, then add addresses, emails, phones, and work history

Add or remove members from a tag in one call using a list of organisationMembershipIds

Record membership payments with amount, currency, and paymentMethod, and log debts and donations per member

GET STARTED

Start building with Raklet API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Raklet API for, with concrete tasks.

★ Membership admin agent through Jentic

An AI agent can take routine membership admin off a small association's volunteers. Through Jentic the agent searches for 'add a member to a membership organisation', receives the Contact_Post operation with its input schema, and creates the contact under the organisation, with the bearer token from Raklet's password grant injected at execution time. It can then tag the new member and record their first membership payment.

Create a contact with POST /organisations/{organisationId}/contacts using firstName 'Aoife', lastName 'Byrne', and language 'en', then add them to a tag with POST /admin/organisations/{organisationId}/tags/{id}/AddMembers

Dues and donation reconciliation

Treasurers of clubs and associations need membership dues and donations recorded against the right person. Raklet records payments through POST /organisations/{organisationId}/payments, which requires amount, currency, and paymentMethod and accepts an organisationMembershipId and isRecurringPayment, while donations link to a donationCampaignId and debts track what a member still owes.

List debts with GET /organisations/{organisationId}/debts, then record a matching payment with POST /organisations/{organisationId}/payments using amount 50, currency 'EUR', and paymentMethod for the member's organisationMembershipId

Member segmentation with tags

Associations send targeted communications to committees, volunteers, or event attendees. Raklet tags are created per organisation and updated in bulk with AddMembers and RemoveMembers, which take a list of organisationMembershipIds, and GET /admin/organisations/{organisationId}/tags/{id}/members pages through who carries a tag.

Create a tag 'Volunteers 2026' with POST /admin/organisations/{organisationId}/tags and add three members to it with the AddMembers operation

Community news and events

Membership organisations keep members engaged with news and events. Raklet publishes posts with POST /organisations/{organisationId}/posts, posts to discussion boards, and lists events with their ticket options through the app routes, so an agent can draft a weekly digest of upcoming events and recent news.

Call GET /app/organisations/{organisationId}/events and GET /organisations/{organisationId}/posts, then draft a digest of upcoming events and recent posts

Key Endpoints

140 endpoints — the raklet api manages the member and contact records of associations, nonprofits, clubs, chambers, and alumni organizations on raklet's membership platform.

METHOD

PATH

DESCRIPTION

POST

/token

Get an access token

GET

/organisations/{organisationId}/contacts

Search contacts

POST

/organisations/{organisationId}/contacts

Create a contact

POST

/admin/organisations/{organisationId}/tags/{id}/AddMembers

Add members to a tag

POST

/organisations/{organisationId}/payments

Record a payment

GET

/organisations/{organisationId}/donations

List donations

GET

/app/organisations/{organisationId}/events

List events

GET

/public/account/me

Get the current account

POST

/token

Get an access token

GET

/organisations/{organisationId}/contacts

Search contacts

POST

/organisations/{organisationId}/contacts

Create a contact

POST

/admin/organisations/{organisationId}/tags/{id}/AddMembers

Add members to a tag

POST

/organisations/{organisationId}/payments

Record a payment

GET

/organisations/{organisationId}/donations

List donations

GET

/app/organisations/{organisationId}/events

List events

GET

/public/account/me

Get the current account

Why Jentic?

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

Setup

Wiring Raklet by hand means running the OAuth 2.0 password grant against POST /token with an admin's email and password, refreshing the bearer token roughly hourly, and threading organisationId through nearly every path. Through Jentic you install once, import Raklet from the API Directory, store the credential once, and your agent calls it.

Permission scoping

A Raklet token carries the admin user's full permissions with no narrower scopes, but Raklet puts the organisation id in the URL path (/organisations/{organisationId}/...), so a rule can pin your agent to one organisation and the operations you pick. You choose what it may call, so destructive ones like contact deletion or payment deletion are not included unless you add them.

Credential isolation

Your Raklet credential 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 a member to a membership organisation' or 'record a membership payment', and Jentic returns the matching Raklet operation with its input schema so the agent calls the right endpoint without browsing the reference.

FAQs

Specific to using Raklet API through Jentic.

What authentication does the Raklet API use?

Per its OpenAPI spec, the Raklet API uses a bearer access token obtained from POST /token with the OAuth 2.0 password grant, using a Raklet admin user's email and password. Every other operation expects the token in the Authorization header. Raklet defines no narrower scopes, so a token carries the full permissions of the admin user it was issued to, and it expires after about an hour.

How do I find my organisationId for the Raklet API?

Most Raklet paths take an organisationId. Find it in the Raklet admin panel under Settings, or call GET /public/account/me with your access token.

What are the rate limits for the Raklet API?

The OpenAPI spec does not specify rate limits. Check the Raklet developer portal at https://www.raklet.com/developers/ for current limits. API access is included in Raklet's Premium plan.

Is there a Raklet MCP server?

You don't need an MCP server to give your agent Raklet. Jentic connects it directly from the API Directory: import it, store your admin credential once, and your agent calls the contact, tag, and payment operations it needs, discovered on demand.

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

Yes, and it matters here because a Raklet token has no scopes. For example, write a rule that allows only the contact search, contact details, and tag-membership operations under your organisationId, so the agent can find and tag members but cannot delete contacts or record payments. Every call it makes is logged.

How do I add a member to Raklet through Jentic?

Search Jentic for 'add a member to a membership organisation', load the POST /organisations/{organisationId}/contacts operation, and execute it with firstName, lastName, and language. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Raklet API

AI ReadinessNon-Ready (F)38/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbearer, oauth2140 EndpointsREST

For Agents

Create and update Raklet member contacts, tag members, record payments and donations, and read events, posts, and directory data for a membership organisation.

Use for: Add a new member to our association in Raklet, Find all contacts tagged as board members, Record a 50 EUR membership payment for a member, List upcoming events for our alumni organisation

Not supported: Does not handle email campaign delivery, accounting ledgers, or public event marketplaces. Use for Raklet membership contacts, tags, dues, donations, events, and community posts only.

The Raklet API manages the member and contact records of associations, nonprofits, clubs, chambers, and alumni organizations on Raklet's membership platform. It creates and updates contacts with their addresses, emails, phones, education, and work history, groups members with tags, and records membership payments, debts, donations, and subscriptions against an organisation. It also lists events and ticket options, posts to boards and news feeds, and reads directory data such as corporate members, job postings, and organisation settings, with most routes scoped by organisationId.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

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

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

71%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: DSignals: 1

45%

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

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Raklet API to your agent

Capabilities

Start building with Raklet API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Raklet API

Jentic AI Readiness Score

Raklet 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