canonical: https://jentic.com/apis/ritekit.com/ritekit-api

# RiteKit API

RiteKit API is based on REST principles. Authentication uses standard OAuth 2.0 process ##Getting started 1. Sign up for [RiteKit](https://ritekit.com/) 1. Go to [developer dashboard](https://ritekit.com/developer/dashboard/) 1. Click "Create a token" button to get your **Client ID** and **Client secret** 1. When you reach your free limit of calls per month, [upgrade to paid tiers](https://ritekit. The API exposes 13 endpoints.

## For AI agents

Programmatically auto-emojify, emoji suggestions. Covers 13 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Auto-Emojify
- Emoji Suggestions
- Animate Image
- Company Logo
- Text to Image
- List of CTAs
- Shorten Link

## Use cases

### Identity and Authentication Operations

Use the RiteKit API to perform identity auth operations programmatically. The API provides 13 endpoints covering core functionality including auto-emojify, emoji suggestions, animate image.

Example prompt: Call GET `/v1/emoji/auto-emojify` to auto-emojify

### Automated Emoji Management

Automate emoji operations by combining multiple RiteKit API endpoints. Agents can emoji suggestions and then animate image in a single workflow.

Example prompt: Call GET `/v1/emoji/suggestions` to emoji suggestions, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RiteKit 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 none tokens manually.

Example prompt: Search Jentic for 'auto-emojify', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/emoji/auto-emojify` | Auto-Emojify |
| GET | `/v1/emoji/suggestions` | Emoji Suggestions |
| GET | `/v1/images/animate` | Animate Image |
| GET | `/v1/images/logo` | Company Logo |
| GET | `/v1/images/quote` | Text to Image |
| GET | `/v1/link/cta` | List of CTAs |
| GET | `/v1/link/short-link` | Shorten Link |
| GET | `/v1/search/trending` | Trending Hashtags |

## Key resources

- **Emoji** — Operations for emoji
- **Images** — Operations for images
- **Instagram** — Operations for instagram
- **Link** — Operations for link
- **Search** — Operations for search

## 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:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 48 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 20 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/ritekit.com/ritekit-api/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 RiteKit API by hand means calling the api.ritekit.com host directly for emoji, image, link, and trending-search endpoints and handling each GET yourself. Through Jentic you install once, import the RiteKit API from the API Directory, and your agent calls it without extra setup since these endpoints need no credential.
- **Permission scoping:** These endpoints take their input as query parameters rather than a resource id in the path, so scope the agent to the operations it needs, such as auto-emojify or short-link generation: you decide which of these read operations the agent may call. Every operation the agent can run is one you have added to that allowed set.
- **Credential handling:** This RiteKit API needs no credential, so there is nothing for the agent to hold. Any keys you do configure in Jentic One are stored encrypted and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'auto-emojify a post' or 'generate a short link', and Jentic returns the matching RiteKit API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the RiteKit API use?

The RiteKit API uses no 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 auto-emojify with the RiteKit API?

Yes. Use the GET `/v1/emoji/auto-emojify` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the RiteKit 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 auto-emojify through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'auto-emojify'. Jentic returns the matching RiteKit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the RiteKit API have?

The RiteKit API exposes 13 endpoints covering emoji, images, instagram operations.

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

Yes. Because you run Jentic One yourself, you decide which RiteKit API operations your agent may call, and it can use only the ones you add to its allowed set. These are all query-parameter GET reads, so you can grant just the operations you need, such as auto-emojify or short-link generation, while leaving out emoji suggestions, image quotes, or trending hashtags. Any operation you do not add stays off limits to the agent.
