canonical: https://jentic.com/apis/rasa.io/rasa

# rasa.io API

rasa.io API provides programmatic access to developer tools functionality. The API exposes 28 endpoints secured with basic, bearer authentication.

## For AI agents

Programmatically creates a token, deletes all tokens. Covers 28 operations with basic, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- creates a token
- deletes all tokens
- user's available communities
- adds persons
- searches persons

## Use cases

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

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

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

Example prompt: Search Jentic for 'creates a token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/tokens` | creates a token |
| DELETE | `/tokens` | deletes all tokens |
| DELETE | `/tokens/{rasa-token}` | deletes a token |
| GET | `/communities` | user's available communities |
| GET | `/sections/{community_identifier}` | user's available sections |
| POST | `/persons` | adds persons |
| GET | `/persons` | searches persons |
| PUT | `/persons` | update persons |

## Key resources

- **authentication** — Operations related to authentication
- **communities** — Operations related to communities
- **sections** — Operations related to sections
- **contacts** — Operations related to contacts
- **insights** — Operations related to insights

## AI readiness

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.

- **Score:** 44 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 20 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 35 / 100
  - AI Discoverability: 61 / 100
- **View full report:** https://jentic.com/apis/rasa.io/rasa/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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