API Testing
Run benchmark requests against OpenAI-compatible endpoints and capture TTFT, total latency, output speed, failure causes, and usage-source attribution.
Local-first AI API testing desktop
ShnDock
AI API testing and configuration desktop
API TestingAPI CardsPromptAgent Skill
Windows 1.0.0 is available; macOS and Linux are not yet open for download
LOCAL-FIRST API WORKSTATION
shinning
API testing workspace
Desktop product structure
API testing, API cards, providers, prompts, and Agent Skills are managed in separate desktop layers.
- Local data
- API keys remain on the user's device by default
- Encrypted migration
- .sapi re-encrypts data with a user password
API TestingTTFT / total latency / usage
API CardsKey / Base URL / model
ProviderOfficial / relay / local
PromptBenchmark / user
Agent SkillSkill Pack / documentation Skill
API Cards
Store API Key, Base URL, model, provider, tags, and notes as locally encrypted configuration cards.
Provider Management
Maintain official, relay, local, and custom providers with consistent endpoint, model, and parameter presets.
Prompt Management
Separate benchmark prompts from user prompts so test baselines and day-to-day templates remain distinct.
Agent Skill Management
Organize Skill Packs and documentation Skills so agents can reuse explicit API instructions, input requirements, and operating boundaries.
Time to first token, used to evaluate response start-up latency.
The full duration from request dispatch to completed response.
Generated token speed calculated from output tokens and elapsed time.
Identifies provider-reported usage, local estimates, mixed data, or unknown sources.
Local security
API keys are locally encrypted
Desktop credentials remain on the user device by default. The official website publishes product information, download entry points, release manifests, and legal documents. It does not provide API key cloud sync or hosted proxy requests.
Storage locationUser device
API keys remain on the user's device by default.
Encryption methodsafeStorage
System-level local encryption is used instead of plaintext JSON storage.
Migration method.sapi encrypted export
Read the full documentationAPI card data is re-encrypted with a user-provided password before migration.
Create an API card
Enter API Key, Base URL, model, provider, tags, and notes, then save them as a locally encrypted card.
Run an API test
Use benchmark prompts to measure TTFT, total latency, output speed, failure cause, and usage-source attribution.
Maintain providers and prompts
Keep provider presets, model settings, benchmark prompts, and user prompts in separate layers.
Manage Agent Skills
Organize Skill Packs and documentation Skills so agents read clear interface instructions and operating boundaries.
Does ShnDock upload API keys?
No. The official website does not receive desktop API keys. Keys remain on the user's device by default and are stored through system-level local encryption.
Are benchmark results absolute measurements?
No. ShnDock labels provider usage, local estimates, mixed data, and unknown sources. Results are for diagnosis and comparison, not billing.
Does ShnDock support cloud sync for API keys?
No. The official website does not provide API key cloud sync. Cross-device migration is handled through password-encrypted .sapi export and import.
Does this website contain the ShnDock desktop source code?
No. This repository contains the official website only and does not imply that the ShnDock desktop source code is open source.