Tools
Your AI picks the tool from what you ask. You don’t have to name them, but knowing what exists helps you ask better. Dates go as YYYY-MM-DD; ids are Sentir’s.
Always available. They spend no tokens.
| Tool | What it does | Arguments |
|---|---|---|
whoami |
Says the name of the account the AI is connected to, your role in it, what it may do and its token cap | None |
list_searches |
Your searches, newest first, with status and sentiment | status (queued, running, done, failed, cancelled), limit (1 to 50, default 20) |
get_search |
One search: status, progress, platforms, tokens and its link | id |
get_report |
The finished report as text, in the report’s language | id, section (summary or full) |
get_posts |
The posts read, most liked first | id, platform, sentiment (pos, neu, neg), limit (1 to 100, default 25) |
list_series |
Your daily trackings with days read, latest reading and trend | None |
get_series |
One tracking: the day-by-day trend and its link | id |
list_comparisons |
Your comparisons and head-to-heads, with each side’s state | None |
get_comparison |
One comparison: measures, the AI’s reading and its link | id |
get_tokens |
Your balance, cap per search, the plan’s tokens and the pack price | None |
The server also offers the full report as a resource: sentir://searches/{id}/report.
Tools marked Spends tokens need the “Start searches” permission and the connection’s token cap. A viewer in the account can’t use them: their AI only reads.
| Tool | What it does | Arguments | Tokens |
|---|---|---|---|
estimate_search |
What a search would hold, whether you have enough and which platforms your plan allows. Starts nothing | keyword, focus, platforms, dateFrom, dateTo, maxTokens |
None |
start_search |
Starts a new search | The above plus acceptCut, confirm |
Spends tokens: holds the cap and charges what it read |
start_daily_tracking |
Starts a daily tracking, on plans that include it | keyword, focus, platforms, startDate, endDate, maxTokens, confirm |
Spends tokens: each day pays its own |
compare_searches |
Compares two finished searches | a, b, confirm |
Spends tokens: a flat 5; a pair already compared costs nothing |
share_search |
Creates a link to share a finished report | id, days (1, 7, 30, 90 or 0 for never), allowExport |
None |
The confirm rule
Section titled “The confirm rule”Every tool that spends tokens takes confirm. Until it is true, the server answers “Not started: confirm is not true” and nothing happens. That is why the AI asks you before starting. If the AI asks for a maxTokens above the connection’s cap, the server refuses and names the cap. If it asks for none, it uses the lower of your account’s cap and the connection’s.
Limits
Section titled “Limits”get_reportand the report resource need a finished search. Before that, they answer with the status.get_postsfails if you ask for a platform the search didn’t read.compare_searchesneeds two finished searches of your account.share_searchdoesn’t work on a running search.