What authentication does the Tenor GIF API use?

Tenor uses an apiKey scheme passed as the 'key' query parameter on each request. Through Jentic the key is stored encrypted in the vault and appended at execution time, so the raw key never enters the agent's context or appears in logs.

Can I autocomplete GIF queries with Tenor?

Yes. GET /autocomplete returns suggested completions for a partial query, which is what GIF pickers call on each keystroke. Pair with GET /search_suggestions to broaden the result set when the user pauses typing.

What are the rate limits for the Tenor GIF API?

Tenor applies per-API-key rate limits documented at developers.google.com/tenor. The OpenAPI spec does not encode exact numbers, so check the Tenor developer console before fanning out picker requests across many concurrent users.

How do I search GIFs through Jentic?

Search Jentic for 'tenor gif search', load the schema for GET /search, and execute with your query and any locale parameters. Jentic injects the 'key' query parameter at execution so the agent only handles the text query.

Does registershare actually upload a new GIF?

No. GET /registershare records that an existing Tenor GIF was shared so it ranks higher in future search results. To upload original media, use Google's separate creator tools - the public Tenor v2 API does not support GIF upload.

Can I limit what my agent is allowed to do with the Tenor GIF API?

Yes. Because you run Jentic One yourself, your own rules decide which Tenor operations and credentials the agent may use. The Tenor GIF API works through top-level search and browse endpoints rather than a resource id in the path, so you can scope the agent to only the operations it needs, such as GET /search, GET /autocomplete, or GET /trending_terms, while leaving out GET /registershare unless you add it. Your Tenor API key is held by your own instance and attached as the 'key' query parameter at execution, so the agent never sees it.