Obscurify AI
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSCURIFY_API_KEY | No | Your sk-obs1_... key. Without it only list_models and generate_image list work. | |
| OBSCURIFY_BASE_URL | No | API base URL. | https://obscurify.ai/v1 |
| OBSCURIFY_TIMEOUT_MS | No | Per-request timeout. second_opinion caps each model at 55 s so the answers that do arrive come back. | 180000 |
| OBSCURIFY_DEFAULT_MODEL | No | Model for ask and chat when none is given. | deepseek/deepseek-v4-flash |
| OBSCURIFY_SECOND_OPINION_MODELS | No | Comma-separated models for second_opinion. | deepseek/deepseek-v4-flash,meta-llama/llama-3.3-70b-instruct,qwen/qwen3.8-27b |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Obscurify.ai gives private access to 200+ AI models (Claude, GPT, Gemini, Llama, DeepSeek, Qwen and more) through zero-data-retention routes; prompts and replies are not stored by Obscurify.ai. Use ask for a one-off question to another model, chat to continue a conversation, second_opinion to compare answers from several models, list_models to find model IDs, prices and context sizes, and balance to check spending. Calls cost money from the account balance; the default model is cheap.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| askA | Send one prompt to any Obscurify.ai model and get its reply. Useful for delegating a subtask to a cheaper or specialised model, getting an outside view, or using a model you don't otherwise have. Prompts go through zero-data-retention routes and are not stored by Obscurify.ai. Default model: deepseek/deepseek-v4-flash (fast and cheap). Use list_models to find other model IDs. For follow-ups that need earlier turns use chat; to compare several models use second_opinion. |
| chatA | Continue a multi-turn conversation with an Obscurify.ai model. Pass the whole history in |
| second_opinionA | Send the same prompt to 2-5 different models at once and return every answer side by side, so you can compare them, check a claim, review code or a plan, or break a tie. Default models: deepseek/deepseek-v4-flash, meta-llama/llama-3.3-70b-instruct, qwen/qwen3.8-27b. |
| list_modelsA | List Obscurify.ai chat models with their IDs, context window, price per million input/output tokens (USD), tool-calling support and the plan they need (any = every account with a balance; casual = Casual or Pro; pro = Pro only). Filter by name, plan, price or tool support. Use it to find a model ID for ask, chat or second_opinion, or the cheapest model with what you need. Doesn't need an API key. |
| balanceA | Show the Obscurify.ai account's balance (USD), plan, included credit used this billing period, token usage, and whether it can use frontier and uncensored models. Use it before a large batch of calls, or when a call fails with a balance (402) or plan (403) error. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct mode of interaction: single prompt (ask), multi-turn (chat), multi-model comparison (second_opinion), model discovery (list_models), and account state (balance). The descriptions explicitly route agents between the overlapping prompt-sending tools ("For follow-ups ... use chat; to compare ... use second_opinion"), eliminating misselection risk.
All names are lowercase snake_case and short, which is consistent and readable. The pattern is slightly mixed in form (bare verbs like ask/chat, a noun like balance, a verb_noun like list_models, and a compound noun second_opinion), but each name still signals its action clearly.
Five tools is well-scoped for a model-gateway server: query, converse, compare, discover, and check credit. Every tool maps to a real workflow and none appear redundant or filler.
The core lifecycle (discover models -> send prompts -> converse -> compare -> verify balance/plan) is fully covered with no dead ends. Minor gaps exist: no per-model detail lookup beyond list_models, no usage history or call-log inspection, and no way to surface tool-calling behavior despite models advertising it.