RiteKit Hashtag API

Setup

Wiring the RiteKit Hashtag API by hand means using your RiteKit client id as a bearer token, sending it on every call to the api.ritekit.com host, and handling each hashtag-stats and suggestion request yourself. Through Jentic you install once, import the RiteKit Hashtag API from the API Directory, store the token once, and your agent calls it.

Permission scoping

This API puts the hashtag in the URL path for history (/v1/stats/history/{hashtag}), so a rule can pin your agent to one hashtag's history, while the other stats and suggestion calls take input as query parameters. You choose the operations it may call, so the agent runs only the reads and suggestions you have added to that allowed set.

Credential isolation

Your RiteKit token 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 'get hashtag statistics' or 'suggest hashtags for a post', and Jentic returns the matching RiteKit Hashtag API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.