Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the rasa.io 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%2Frasa.io%2Frasa" | shStep 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%2Frasa.io%2Frasa" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with rasa.io API.
creates a token
deletes all tokens
user's available communities
adds persons
searches persons
Patterns agents use rasa.io API for, with concrete tasks.
GET STARTED
★ Developer Tools Operations
Use the rasa.io API to perform developer tools operations programmatically. The API provides 28 endpoints covering core functionality including creates a token, deletes all tokens, deletes a token.
Call POST /tokens to creates a token
Automated authentication Management
Automate authentication operations by combining multiple rasa.io API endpoints. Agents can deletes all tokens and then deletes a token in a single workflow.
Call DELETE /tokens to deletes all tokens, then verify the result
AI Agent Integration via Jentic
AI agents discover and call rasa.io 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 basic, bearer tokens manually.
Search Jentic for 'creates a token', load the operation schema, and execute with Jentic-managed credentials
28 endpoints — rasa.
METHOD
PATH
DESCRIPTION
/tokens
creates a token
/tokens
deletes all tokens
/tokens/{rasa-token}
deletes a token
/communities
user's available communities
/sections/{community_identifier}
user's available sections
/persons
adds persons
/persons
searches persons
/persons
update persons
/tokens
creates a token
/tokens
deletes all tokens
/tokens/{rasa-token}
deletes a token
/communities
user's available communities
/sections/{community_identifier}
user's available sections
/persons
adds persons
/persons
searches persons
/persons
update persons
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the rasa.io API by hand means learning both its basic and bearer auth and hand-coding requests across its token, community, and person endpoints. Through Jentic you install once, import the rasa.io API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
rasa.io puts resource ids in the URL path (/sections/{community_identifier}, /tokens/{rasa-token}), so a rule can pin your agent to one community: it can read that community's sections and people and nothing else. You choose the operations it may call, so destructive ones like deleting a token are not included unless you add them.
Credential isolation
Your rasa.io 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 'list community members' or 'create an access token', and Jentic returns the matching rasa.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using rasa.io API through Jentic.
What authentication does the rasa.io API use?
The rasa.io API uses basic, 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 creates a token with the rasa.io API?
Yes. Use the POST /tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the rasa.io 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 creates a token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a token'. Jentic returns the matching rasa.io API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the rasa.io API have?
The rasa.io API exposes 28 endpoints covering authentication, communities, sections operations.
Can I limit what my agent is allowed to do with the rasa.io API?
Yes. Because you self-host Jentic One, your own rules decide which rasa.io operations and credentials your agent may use. Since rasa.io puts resource ids in the URL path, such as /sections/{community_identifier} and /tokens/{rasa-token}, you can pin the agent to a single community so it only reads that community's sections and people. You also choose the exact operations it may call, so destructive ones like DELETE /tokens are excluded unless you explicitly add them.
For Agents
Programmatically creates a token, deletes all tokens. Covers 28 operations with basic, bearer authentication.
Use for: I need to creates a token, I want to deletes all tokens, Search for deletes a token, Find all user's available communities
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
rasa.io API provides programmatic access to developer tools functionality. The API exposes 28 endpoints secured with basic, bearer authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>