Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Spiky API V2, 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%2Fspiky.ai%2Fspiky" | 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%2Fspiky.ai%2Fspiky" | 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 Spiky API V2 API.
Get an authorization token
Refresh an authorization token
Create a new analysis
List analyses
Monitor Spiky API V2 operational status and events
GET STARTED
Patterns agents use Spiky API V2 API for, with concrete tasks.
★ Productivity Operations
Use the Spiky API V2 to perform productivity operations programmatically. The API provides 6 endpoints covering core functionality including get an authorization token, refresh an authorization token, create a new analysis.
Call POST /public/token to get an authorization token
Automated authorization Management
Automate authorization operations by combining multiple Spiky API V2 endpoints. Agents can refresh an authorization token and then create a new analysis in a single workflow.
Call POST /public/token/refresh to refresh an authorization token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Spiky API V2 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'get an authorization token', load the operation schema, and execute with Jentic-managed credentials
6 endpoints — spiky api v2 provides programmatic access to spiky's meeting analysis platform.
METHOD
PATH
DESCRIPTION
/public/token
Get an authorization token
/public/token/refresh
Refresh an authorization token
/platform/meeting-reports
Create a new analysis
/platform/meeting-reports
List analyses
/platform/meeting-reports/{analysisId}
Get an analysis by ID
/platform/ml-data/{analysisId}
Get ML data for an analysis
/public/token
Get an authorization token
/public/token/refresh
Refresh an authorization token
/platform/meeting-reports
Create a new analysis
/platform/meeting-reports
List analyses
/platform/meeting-reports/{analysisId}
Get an analysis by ID
/platform/ml-data/{analysisId}
Get ML data for an analysis
What agents get from Jentic-routed access to this vendor.
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Spiky API V2 API through Jentic.
What authentication does the Spiky API V2 use?
The Spiky API V2 uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get an authorization token with the Spiky API V2?
Yes. Use the POST /public/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Spiky API V2?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get an authorization token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get an authorization token'. Jentic returns the matching Spiky API V2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Spiky API V2 have?
The Spiky API V2 exposes 6 endpoints covering authorization, meeting-reports, ml-data operations.
Can I limit what my agent is allowed to do with the Spiky API V2?
Yes. Jentic One runs self-hosted, so your own rules decide which Spiky operations and credentials your agent may use. Because Spiky puts the analysis id in the URL path (/platform/meeting-reports/{analysisId}), you can pin the agent to a single meeting report and its ml-data instead of the whole account. You also choose the exact operations it may call, so read-only access to List analyses and Get an analysis stays separate from Create a new analysis, which is excluded unless you grant it.
For Agents
Programmatically get an authorization token, refresh an authorization token. Covers 6 operations with bearer authentication.
Use for: I need to an authorization token, I want to refresh an authorization token, Search for a new analysis, Find all analyses
Not supported: Does not handle payments, communications, or crm - use for productivity only.
Spiky API V2 provides programmatic access to Spiky's meeting analysis platform. How to use: 1. Open a Spiky account 2. Get authentication tokens 3. Send POST /platform/meeting-reports for fetching upload URLs. The integration name must be given "MANUALTIMELINE" for manual timeline upload flow. 4. Upload timeline file to S3 via given signed URL (if manual timeline flow is selected) 5. Upload a vide. The API exposes 6 endpoints secured with bearer authentication.
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>