Spiky API V2

Setup

Wiring Spiky API V2 by hand means implementing its bearer auth, calling its /public/token and refresh endpoints to keep a live token, and pointing every request at the apiv2.spiky.ai host yourself. Through Jentic you install once, import Spiky API V2 from the API Directory, store the token once, and your agent calls it.

Permission scoping

Spiky puts the analysis id in the URL path (/platform/meeting-reports/{analysisId}), so a rule can pin your agent to one meeting report and its ml-data. You choose the operations it may call, so creating new meeting reports is not included unless you add it.

Credential isolation

Your Spiky bearer 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 'list meeting reports' or 'get analysis data for a meeting', and Jentic returns the matching Spiky API V2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.