Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RiteKit 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%2Fritekit.com%2Fritekit-main" | 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%2Fritekit.com%2Fritekit-main" | 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 RiteKit API.
Pull real-time stats for up to 100 hashtags in one call via the tags parameter
Read a hashtag's historical stats for the last 30 days
List hashtags currently trending on Twitter, optionally limited to green or latin-character tags
Auto-hashtag a post with maxHashtags and an end or auto hashtagPosition
Remove banned hashtags from an Instagram post before publishing
GET STARTED
Add emoji to post text or return emoji suggestions for it
Render a quote and author as a styled image with font, color, and gradient options
Patterns agents use RiteKit API for, with concrete tasks.
★ AI social copywriter with hashtag checks
An agent drafting social posts needs evidence for which hashtags to use instead of guessing. Through Jentic it searches for 'hashtag stats', loads RiteKit's GET /v1/stats/multiple-hashtags, and passes the candidate tags to get real-time stats for each, then calls GET /v1/stats/auto-hashtag to insert the chosen ones into the draft. The developer reviews the finished post before it goes out.
Call GET /v1/stats/multiple-hashtags with tags 'ai,machinelearning,python', then call GET /v1/stats/auto-hashtag with the draft as post, maxHashtags 2, and hashtagPosition 'end'
Trend monitoring for a content calendar
A social media manager checks what is rising before planning the week. GET /v1/search/trending returns hashtags currently trending on Twitter, with green to restrict results to hashtags that are not overused and latin to keep only latin-character tags. GET /v1/stats/history/{hashtag} then shows the last 30 days for any tag worth tracking.
Call GET /v1/search/trending with green 1 and latin 1, then call GET /v1/stats/history/{hashtag} for the top three results
Instagram caption cleanup
Posting with a banned hashtag can limit an Instagram post's reach. GET /v2/instagram/hashtags-cleaner takes the post text and returns it with banned hashtags removed, so a scheduling tool can clean every caption just before it is queued.
Call GET /v2/instagram/hashtags-cleaner with the caption as post and use the returned text as the final caption
Visual assets for posts
Text posts perform better with an image. GET /v1/images/quote renders a quote and author into an image using parameters such as quoteFont, fontSize, bgType, gradientColor1, and brandLogo, and GET /v1/images/logo returns a company logo for a domain, extracting it from the site on the fly when it is not yet stored.
Call GET /v1/images/quote with quote 'Ship small, ship often', author 'Team Lead', and bgType 'gradient', then attach the returned image URL to the post
13 endpoints — the ritekit api scores hashtags and prepares social posts: it returns real-time stats for up to 100 hashtags at once, the last 30 days of history for a single hashtag, and the hashtags currently trending on twitter.
METHOD
PATH
DESCRIPTION
/v1/stats/multiple-hashtags
Real-time stats for up to 100 hashtags
/v1/stats/history/{hashtag}
30-day history for a hashtag
/v1/search/trending
Hashtags trending on Twitter
/v1/stats/auto-hashtag
Add hashtags to post text
/v1/stats/hashtag-suggestions
Hashtag suggestions for a topic
/v2/instagram/hashtags-cleaner
Remove banned Instagram hashtags
/v1/emoji/auto-emojify
Add emoji to post text
/v1/images/quote
Render a quote as an image
/v1/stats/multiple-hashtags
Real-time stats for up to 100 hashtags
/v1/stats/history/{hashtag}
30-day history for a hashtag
/v1/search/trending
Hashtags trending on Twitter
/v1/stats/auto-hashtag
Add hashtags to post text
/v1/stats/hashtag-suggestions
Hashtag suggestions for a topic
/v2/instagram/hashtags-cleaner
Remove banned Instagram hashtags
/v1/emoji/auto-emojify
Add emoji to post text
/v1/images/quote
Render a quote as an image
What agents get from Jentic-routed access to this vendor.
Setup
Wiring RiteKit by hand means reading its spec description to learn that a Client ID can ride as a query parameter even though the spec declares no scheme, then mapping 13 GET tools spread across stats, emoji, image, and link paths. Through Jentic you install once, import RiteKit from the API Directory, and your agent calls it.
Permission scoping
RiteKit takes nearly all of its input as query parameters, with only the hashtag history route carrying a value in the path, so limit the agent to the operations it needs, such as hashtag stats and trending search. You choose the operations it may call, so ones like GET /v1/link/short-link or image generation are not included unless you add them.
Credential isolation
The RiteKit spec declares no credential, so the agent holds no secret for these calls. If you add a RiteKit Client ID to your own Jentic One instance, it is kept encrypted and injected at execution time, outside the agent's prompt, logs, and context.
Intent-based discovery
Agents search Jentic by intent such as 'hashtag stats' or 'clean Instagram hashtags', and Jentic returns the matching RiteKit operation with its input schema, including parameters like maxHashtags and hashtagPosition.
Alternatives and complements available in the Jentic catalogue.
Specific to using RiteKit API through Jentic.
What authentication does the RiteKit API use?
This OpenAPI spec declares no security scheme and no credential parameter on its 13 operations. The spec's own description says RiteKit issues a Client ID and Client secret from its developer dashboard, accepts the Client ID as a client_id query parameter, and also supports OAuth 2.0, and it notes that GET /v1/link/cta requires each user to authenticate with RiteKit. Check the RiteKit developer dashboard for the current authorization options.
Can I check several hashtags in one request with the RiteKit API?
Yes. GET /v1/stats/multiple-hashtags takes a tags parameter with hashtags written without the # mark and returns real-time stats for up to 100 of them, updated hourly. For a single tag's trend over time, GET /v1/stats/history/{hashtag} returns the last 30 days.
What are the rate limits for the RiteKit API?
The OpenAPI spec does not specify rate limits. Its description mentions a free monthly call allowance with paid tiers above it; see https://ritekit.com/developer/ for the current limits.
Is there a RiteKit MCP server?
You do not need an MCP server to give your agent RiteKit. Jentic connects it directly from the API Directory: import it and your agent finds hashtag, emoji, and image operations by intent, without a separate server's tool list sitting in its context.
How do I auto-hashtag a post through Jentic?
Search Jentic for 'add hashtags to a post', load the GET /v1/stats/auto-hashtag operation, and pass the text as post, plus maxHashtags and hashtagPosition set to end or auto. The response is the post with hashtags inserted. 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 RiteKit API?
Yes. For a research assistant, write a rule that allows only GET /v1/stats/multiple-hashtags, GET /v1/stats/history/{hashtag}, and GET /v1/search/trending. The agent can then read hashtag data but cannot shorten links or generate images, and every call it makes is logged.
Know of an official OpenAPI document? Contribute it →
For Agents
Check hashtag stats and 30-day history, find trending Twitter hashtags, and auto-hashtag or emojify post text before an agent publishes it.
Use for: Get the stats for #ai, #ml, and #python, Find all hashtags trending on Twitter right now, Retrieve the 30-day history for the hashtag marketing, Add three relevant hashtags to the end of this post
Not supported: Does not publish or schedule posts, read social account inboxes, or track brand mentions. Use for hashtag research and preparing post text and images only.
The RiteKit API scores hashtags and prepares social posts: it returns real-time stats for up to 100 hashtags at once, the last 30 days of history for a single hashtag, and the hashtags currently trending on Twitter. It also rewrites post text by adding relevant hashtags or emoji, strips banned hashtags before an Instagram post, and suggests hashtags for a topic. Supporting tools shorten links with a call to action, fetch a company logo from its domain, and render a quote as a styled image.
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>