Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Omni Settings · diegosouzapw | DecimalAI

diegosouzapw/omni-settings

SkillScore100Maintained

Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

agent-toolingby diegosouzapw

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

AI Engineer pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/diegosouzapw-omni-settings/SKILL.md

decimalai skills pull diegosouzapw-omni-settings --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/diegosouzapw-omni-settings/SKILL.md https://app.decimal.ai/s/diegosouzapw-omni-settings/SKILL.md

Raw file: /s/diegosouzapw-omni-settings/SKILL.md ↗ · machine-readable summary at /s/diegosouzapw-omni-settings.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

23 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 4d ago

Yes — +87% lift · at higher cost+549% tokens0% turns100% of whole cases pass with skill (23/23)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	303%	0%
case-02	✗→✓	▲ Improved	420%	0%
case-03	✗→✓	▲ Improved	798%	0%
case-04	✗→✓	▲ Improved	329%	0%
case-05	✗→✓	▲ Improved	473%	0%

Showing 5 of 23 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/23/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

diegosouzapw / omniroute

skills/omni-settings/SKILL.md

View on GitHub ↗

License MITImported 9/23/2026Version v5

Skill contents

SKILL.md

Overview

Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

Authentication

All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.

Endpoints

GET /api/settings/memory

Get memory settings

Returns the extended memory settings including 7 new fields added in plan 21 (embeddingSource, embeddingProviderModel, transformersEnabled, staticEnabled, rerankEnabled, rerankProviderModel, vectorStore).

bash
curl https://localhost:20128/api/settings/memory \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/memory

Update memory settings

Update any subset of the extended memory settings. All fields are optional; only provided fields are updated. Schema: MemorySettingsExtendedSchema.

bash
curl -X PUT https://localhost:20128/api/settings/memory \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/qdrant

Get Qdrant settings

Returns current Qdrant configuration. The apiKey field is never returned raw — use hasApiKey / apiKeyMasked instead.

bash
curl https://localhost:20128/api/settings/qdrant \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/qdrant

Update Qdrant settings

Update Qdrant configuration. Pass apiKey: "" to remove the stored key. Schema: QdrantSettingsUpdateSchema.

bash
curl -X PUT https://localhost:20128/api/settings/qdrant \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/qdrant/health

Qdrant health probe

Performs a liveness check against the configured Qdrant instance. Returns latency and any connection error (sanitized — no stack traces).

bash
curl https://localhost:20128/api/settings/qdrant/health \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/qdrant/search

Qdrant semantic search test

Performs a test semantic search against the Qdrant collection. Useful for validating that the integration works end-to-end. Schema: QdrantSearchSchema.

bash
curl -X POST https://localhost:20128/api/settings/qdrant/search \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/qdrant/cleanup

Clean up expired Qdrant points

Removes Qdrant points for memories that have expired or exceeded the configured retention window.

bash
curl -X POST https://localhost:20128/api/settings/qdrant/cleanup \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/qdrant/embedding-models

List Qdrant embedding models

Returns the list of embedding models available for use with Qdrant.

bash
curl https://localhost:20128/api/settings/qdrant/embedding-models \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings

Get application settings

bash
curl https://localhost:20128/api/settings \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PATCH /api/settings

Update settings

bash
curl -X PATCH https://localhost:20128/api/settings \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/purge-request-history

Clear request log history

Deletes call_logs, legacy request_detail_logs, and local request artifact files under DATA_DIR/call_logs.

bash
curl -X POST https://localhost:20128/api/settings/purge-request-history \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/compression

Get global compression settings

bash
curl https://localhost:20128/api/settings/compression \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/compression

Update global compression settings

bash
curl -X PUT https://localhost:20128/api/settings/compression \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/compression/mcp-accessibility

Get the MCP tool-output accessibility (trimming) config

bash
curl https://localhost:20128/api/settings/compression/mcp-accessibility \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/compression/mcp-accessibility

Update the MCP tool-output accessibility (trimming) config

Partial-merge update. Numeric floors (e.g. a maxTextChars below the truncation-tail reserve) are folded back to the safe defaults server-side, so the response reflects the effective config.

bash
curl -X PUT https://localhost:20128/api/settings/compression/mcp-accessibility \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/payload-rules

Get payload rules configuration

Returns the current payload rules used to mutate outgoing request payloads before they are sent upstream.

Requires a dashboard management session cookie when management auth is enabled.

bash
curl https://localhost:20128/api/settings/payload-rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/payload-rules

Update payload rules configuration

Persists and hot reloads payload rules. The legacy input field default-raw is accepted on writes and normalized to defaultRaw in responses/runtime state.

Requires a dashboard management session cookie when management auth is enabled.

bash
curl -X PUT https://localhost:20128/api/settings/payload-rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/combo-defaults

Get combo default settings

bash
curl https://localhost:20128/api/settings/combo-defaults \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/proxy

Get proxy settings

bash
curl https://localhost:20128/api/settings/proxy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PATCH /api/settings/proxy

Update proxy settings

bash
curl -X PATCH https://localhost:20128/api/settings/proxy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/proxy/test

Test proxy connection

bash
curl -X POST https://localhost:20128/api/settings/proxy/test \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/require-login

Toggle login requirement

bash
curl -X POST https://localhost:20128/api/settings/require-login \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/ip-filter

Get IP filter configuration

Returns the current IP filter settings including blacklist, whitelist, and temp bans.

bash
curl https://localhost:20128/api/settings/ip-filter \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/ip-filter

Update IP filter configuration

Configure IP filtering with blacklist/whitelist modes, add/remove individual IPs, and manage temp bans.

bash
curl -X PUT https://localhost:20128/api/settings/ip-filter \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/system-prompt

Get system prompt configuration

Returns the current system prompt injection settings.

bash
curl https://localhost:20128/api/settings/system-prompt \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/system-prompt

Update system prompt configuration

bash
curl -X PUT https://localhost:20128/api/settings/system-prompt \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/thinking-budget

Get thinking budget configuration

Returns the current thinking/reasoning budget settings for AI models.

bash
curl https://localhost:20128/api/settings/thinking-budget \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/thinking-budget

Update thinking budget configuration

bash
curl -X PUT https://localhost:20128/api/settings/thinking-budget \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/tags

List Ollama-compatible model tags

Returns models in Ollama /api/tags format for Ollama client compatibility

bash
curl https://localhost:20128/api/tags \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/quota-store

Get current quota store driver settings

Redis URL is masked in the response (shows only scheme+host).

bash
curl https://localhost:20128/api/settings/quota-store \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/quota-store

Update quota store driver settings

bash
curl -X PUT https://localhost:20128/api/settings/quota-store \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/purge-usage-history

Purge usage history

Dashboard-only. Purges stored usage-history records.

bash
curl -X POST https://localhost:20128/api/settings/purge-usage-history \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/authz-inventory

GET settings › authz inventory

bash
curl https://localhost:20128/api/settings/authz-inventory \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/auto-disable-accounts

GET settings › auto disable accounts

bash
curl https://localhost:20128/api/settings/auto-disable-accounts \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/auto-disable-accounts

PUT settings › auto disable accounts

bash
curl -X PUT https://localhost:20128/api/settings/auto-disable-accounts \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/background-degradation

GET settings › background degradation

bash
curl https://localhost:20128/api/settings/background-degradation \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/background-degradation

POST settings › background degradation

bash
curl -X POST https://localhost:20128/api/settings/background-degradation \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PUT /api/settings/background-degradation

PUT settings › background degradation

bash
curl -X PUT https://localhost:20128/api/settings/background-degradation \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/cache-config

GET settings › cache config

bash
curl https://localhost:20128/api/settings/cache-config \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/cache-config

PUT settings › cache config

bash
curl -X PUT https://localhost:20128/api/settings/cache-config \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/cache-metrics

GET settings › cache metrics

bash
curl https://localhost:20128/api/settings/cache-metrics \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

DELETE /api/settings/cache-metrics

DELETE settings › cache metrics

bash
curl -X DELETE https://localhost:20128/api/settings/cache-metrics \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/cc-discovery-metrics

GET settings › cc discovery metrics

bash
curl https://localhost:20128/api/settings/cc-discovery-metrics \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/compression/rules

GET settings › compression › rules

bash
curl https://localhost:20128/api/settings/compression/rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/compression/run-telemetry

GET settings › compression › run telemetry

bash
curl https://localhost:20128/api/settings/compression/run-telemetry \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/database

GET settings › database

bash
curl https://localhost:20128/api/settings/database \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/database

PUT settings › database

bash
curl -X PUT https://localhost:20128/api/settings/database \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PATCH /api/settings/database

PATCH settings › database

bash
curl -X PATCH https://localhost:20128/api/settings/database \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/database/refresh-stats

POST settings › database › refresh stats

bash
curl -X POST https://localhost:20128/api/settings/database/refresh-stats \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/database/vacuum

GET settings › database › vacuum

bash
curl https://localhost:20128/api/settings/database/vacuum \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/database/vacuum

POST settings › database › vacuum

bash
curl -X POST https://localhost:20128/api/settings/database/vacuum \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/export-json

GET settings › export json

bash
curl https://localhost:20128/api/settings/export-json \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/favicon

GET settings › favicon

bash
curl https://localhost:20128/api/settings/favicon \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/feature-flags

GET settings › feature flags

bash
curl https://localhost:20128/api/settings/feature-flags \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/feature-flags

PUT settings › feature flags

bash
curl -X PUT https://localhost:20128/api/settings/feature-flags \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/feature-flags

DELETE settings › feature flags

bash
curl -X DELETE https://localhost:20128/api/settings/feature-flags \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/free-proxies

GET settings › free proxies

bash
curl https://localhost:20128/api/settings/free-proxies \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

DELETE /api/settings/free-proxies

DELETE settings › free proxies

bash
curl -X DELETE https://localhost:20128/api/settings/free-proxies \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/free-proxies/{id}/add-to-pool

POST settings › free proxies › <id> › add to pool

bash
curl -X POST https://localhost:20128/api/settings/free-proxies/{id}/add-to-pool \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/free-proxies/bulk-add-to-pool

POST settings › free proxies › bulk add to pool

bash
curl -X POST https://localhost:20128/api/settings/free-proxies/bulk-add-to-pool \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/free-proxies/stats

GET settings › free proxies › stats

bash
curl https://localhost:20128/api/settings/free-proxies/stats \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/free-proxies/sync

POST settings › free proxies › sync

bash
curl -X POST https://localhost:20128/api/settings/free-proxies/sync \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/import-json

POST settings › import json

bash
curl -X POST https://localhost:20128/api/settings/import-json \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/lkgp-cache

DELETE settings › lkgp cache

bash
curl -X DELETE https://localhost:20128/api/settings/lkgp-cache \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/local-corpus

GET settings › local corpus

bash
curl https://localhost:20128/api/settings/local-corpus \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/local-corpus

POST settings › local corpus

bash
curl -X POST https://localhost:20128/api/settings/local-corpus \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/local-corpus

DELETE settings › local corpus

bash
curl -X DELETE https://localhost:20128/api/settings/local-corpus \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/mitm

GET settings › mitm

bash
curl https://localhost:20128/api/settings/mitm \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/mitm

POST settings › mitm

bash
curl -X POST https://localhost:20128/api/settings/mitm \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PUT /api/settings/mitm

PUT settings › mitm

bash
curl -X PUT https://localhost:20128/api/settings/mitm \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/model-aliases

GET settings › model aliases

bash
curl https://localhost:20128/api/settings/model-aliases \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/model-aliases

POST settings › model aliases

bash
curl -X POST https://localhost:20128/api/settings/model-aliases \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PUT /api/settings/model-aliases

PUT settings › model aliases

bash
curl -X PUT https://localhost:20128/api/settings/model-aliases \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/model-aliases

DELETE settings › model aliases

bash
curl -X DELETE https://localhost:20128/api/settings/model-aliases \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/models-dev

GET settings › models dev

bash
curl https://localhost:20128/api/settings/models-dev \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/models-dev

POST settings › models dev

bash
curl -X POST https://localhost:20128/api/settings/models-dev \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/notion

GET settings › notion

bash
curl https://localhost:20128/api/settings/notion \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/notion

POST settings › notion

bash
curl -X POST https://localhost:20128/api/settings/notion \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/notion

DELETE settings › notion

bash
curl -X DELETE https://localhost:20128/api/settings/notion \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/obsidian

GET settings › obsidian

bash
curl https://localhost:20128/api/settings/obsidian \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/obsidian

POST settings › obsidian

bash
curl -X POST https://localhost:20128/api/settings/obsidian \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/obsidian

DELETE settings › obsidian

bash
curl -X DELETE https://localhost:20128/api/settings/obsidian \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/obsidian/webdav

GET settings › obsidian › webdav

bash
curl https://localhost:20128/api/settings/obsidian/webdav \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/obsidian/webdav

POST settings › obsidian › webdav

bash
curl -X POST https://localhost:20128/api/settings/obsidian/webdav \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/obsidian/webdav

DELETE settings › obsidian › webdav

bash
curl -X DELETE https://localhost:20128/api/settings/obsidian/webdav \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/oneproxy

GET settings › oneproxy

bash
curl https://localhost:20128/api/settings/oneproxy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/oneproxy

POST settings › oneproxy

bash
curl -X POST https://localhost:20128/api/settings/oneproxy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/oneproxy

DELETE settings › oneproxy

bash
curl -X DELETE https://localhost:20128/api/settings/oneproxy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/oneproxy/rotate

POST settings › oneproxy › rotate

bash
curl -X POST https://localhost:20128/api/settings/oneproxy/rotate \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/proxies

GET settings › proxies

bash
curl https://localhost:20128/api/settings/proxies \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/proxies

POST settings › proxies

bash
curl -X POST https://localhost:20128/api/settings/proxies \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PATCH /api/settings/proxies

PATCH settings › proxies

bash
curl -X PATCH https://localhost:20128/api/settings/proxies \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/proxies

DELETE settings › proxies

bash
curl -X DELETE https://localhost:20128/api/settings/proxies \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/proxies/{id}/repair-relay

POST settings › proxies › <id> › repair relay

bash
curl -X POST https://localhost:20128/api/settings/proxies/{id}/repair-relay \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/proxies/assignments

GET settings › proxies › assignments

bash
curl https://localhost:20128/api/settings/proxies/assignments \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/proxies/assignments

PUT settings › proxies › assignments

bash
curl -X PUT https://localhost:20128/api/settings/proxies/assignments \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/proxies/auto-test

POST settings › proxies › auto test

bash
curl -X POST https://localhost:20128/api/settings/proxies/auto-test \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/proxies/batch-activate

POST settings › proxies › batch activate

bash
curl -X POST https://localhost:20128/api/settings/proxies/batch-activate \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/proxies/batch-delete

POST settings › proxies › batch delete

bash
curl -X POST https://localhost:20128/api/settings/proxies/batch-delete \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PUT /api/settings/proxies/bulk-assign

PUT settings › proxies › bulk assign

bash
curl -X PUT https://localhost:20128/api/settings/proxies/bulk-assign \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/proxies/bulk-import

POST settings › proxies › bulk import

bash
curl -X POST https://localhost:20128/api/settings/proxies/bulk-import \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/proxies/egress

GET settings › proxies › egress

bash
curl https://localhost:20128/api/settings/proxies/egress \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/proxies/egress

POST settings › proxies › egress

bash
curl -X POST https://localhost:20128/api/settings/proxies/egress \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/proxies/health

GET settings › proxies › health

bash
curl https://localhost:20128/api/settings/proxies/health \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/proxies/migrate

POST settings › proxies › migrate

bash
curl -X POST https://localhost:20128/api/settings/proxies/migrate \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/proxies/pool

GET settings › proxies › pool

bash
curl https://localhost:20128/api/settings/proxies/pool \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/proxies/pool

PUT settings › proxies › pool

bash
curl -X PUT https://localhost:20128/api/settings/proxies/pool \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PATCH /api/settings/proxies/pool

PATCH settings › proxies › pool

bash
curl -X PATCH https://localhost:20128/api/settings/proxies/pool \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/proxies/pool

DELETE settings › proxies › pool

bash
curl -X DELETE https://localhost:20128/api/settings/proxies/pool \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/settings/proxies/pool/egress-observation

GET settings › proxies › pool › egress observation

Read-only observation of how many distinct egress IPs actually served the members of a proxy pool over the last 24 h, read from the proxy log (numbers only, never used for routing). Opt-in through the PROXY_POOL_EGRESS_OBSERVATION feature flag: while it is off, or when the read fails, the body is JSON null. Results are cached for 30 seconds per normalized scope (key is read as account, global as the stored global pool).

bash
curl https://localhost:20128/api/settings/proxies/pool/egress-observation \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/proxy/cloudflare-deploy

POST settings › proxy › cloudflare deploy

bash
curl -X POST https://localhost:20128/api/settings/proxy/cloudflare-deploy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/proxy/deno-deploy

POST settings › proxy › deno deploy

bash
curl -X POST https://localhost:20128/api/settings/proxy/deno-deploy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/proxy/vercel-deploy

POST settings › proxy › vercel deploy

bash
curl -X POST https://localhost:20128/api/settings/proxy/vercel-deploy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/purge-call-logs

POST settings › purge call logs

bash
curl -X POST https://localhost:20128/api/settings/purge-call-logs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/purge-detailed-logs

POST settings › purge detailed logs

bash
curl -X POST https://localhost:20128/api/settings/purge-detailed-logs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/purge-logs

POST settings › purge logs

bash
curl -X POST https://localhost:20128/api/settings/purge-logs \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/settings/purge-quota-snapshots

POST settings › purge quota snapshots

bash
curl -X POST https://localhost:20128/api/settings/purge-quota-snapshots \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/quota/state

GET settings › quota › state

bash
curl https://localhost:20128/api/settings/quota/state \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/quota/state

POST settings › quota › state

bash
curl -X POST https://localhost:20128/api/settings/quota/state \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/reasoning-routing-rules

GET settings › reasoning routing rules

bash
curl https://localhost:20128/api/settings/reasoning-routing-rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/reasoning-routing-rules

POST settings › reasoning routing rules

bash
curl -X POST https://localhost:20128/api/settings/reasoning-routing-rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/reasoning-routing-rules/{id}

GET settings › reasoning routing rules › <id>

bash
curl https://localhost:20128/api/settings/reasoning-routing-rules/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PATCH /api/settings/reasoning-routing-rules/{id}

PATCH settings › reasoning routing rules › <id>

bash
curl -X PATCH https://localhost:20128/api/settings/reasoning-routing-rules/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/settings/reasoning-routing-rules/{id}

DELETE settings › reasoning routing rules › <id>

bash
curl -X DELETE https://localhost:20128/api/settings/reasoning-routing-rules/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/reasoning-routing-rules/simulate

POST settings › reasoning routing rules › simulate

bash
curl -X POST https://localhost:20128/api/settings/reasoning-routing-rules/simulate \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/task-routing

GET settings › task routing

bash
curl https://localhost:20128/api/settings/task-routing \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/settings/task-routing

POST settings › task routing

bash
curl -X POST https://localhost:20128/api/settings/task-routing \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

PUT /api/settings/task-routing

PUT settings › task routing

bash
curl -X PUT https://localhost:20128/api/settings/task-routing \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/settings/tier-config

GET settings › tier config

bash
curl https://localhost:20128/api/settings/tier-config \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/settings/tier-config

PUT settings › tier config

bash
curl -X PUT https://localhost:20128/api/settings/tier-config \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

Payloads

See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.

GET /api/settings/thinking-budget — behavior

Returns proxy-level thinking/reasoning request rewrite settings:

| Field | Meaning | |-------|---------| | mode | passthrough (leave client reasoning alone — required for Codex visible thinking), auto (strips all client thinking fields), custom, adaptive | | customBudget | Fixed budget when mode=custom | | effortLevel | Base effort when mode=adaptive |

Not compression and not "decrypt encrypted reasoning". Full guide: docs/guides/THINKING_BUDGET.md.

Example — keep client-controlled reasoning (Codex/Desktop):

bash
curl -X PUT https://localhost:20128/api/settings/thinking-budget \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"passthrough","customBudget":10240,"effortLevel":"medium"}'

Warning: mode=auto deletes reasoning / reasoning_effort / Claude thinking from the outbound body before upstream. That can empty thinking panels even when the client requested Ultra + summary.

Illustrative Want to see what diegosouzapw/omni-settings would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

9/23/2026, 08:19 UTC · 23 cases

Lift

+87%

100% vs 13%

Agent turns

1.0 vs 1.0

Tokens

+549%

11,104.74 vs 1,710.52

fail → pass · 20pass → pass · 3

Per-case results (23)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 I noticed my desktop AI client's reasoning trace is disappearing because the proxy appears to be clearing out thinking parameters before sending requests upstream. Could you provide the cURL commands to view my server's reasoning budget configuration and update it so client-specified thinking parameters remain intact?	fail→pass	20,297	10,967	-46%	1	1	0%	2,810	11,312	+303%	0	0	—
case-02 We are integrating a Qdrant vector database with OmniRoute and want to verify that everything is working end-to-end. Can you show me the cURL calls to check instance connectivity and run a sample semantic search query using our authorization bearer token?	fail→pass	36,122	12,133	-66%	1	1	0%	2,219	11,535	+420%	0	0	—
case-03 I need to wipe old request logs and local call artifact files from our deployment to reclaim disk space. Please provide the cURL command for the appropriate settings API endpoint to purge this call history, including the required auth header format.	fail→pass	9,109	8,894	-2%	1	1	0%	1,252	11,245	+798%	0	0	—
case-04 We are seeing truncated tool outputs when using Model Context Protocol (MCP) tool calls on our OmniRoute gateway. I want to check and tweak the MCP tool-output accessibility truncation limits using cURL. Which specific API routes should I query and update?	fail→pass	20,413	9,592	-53%	1	1	0%	2,596	11,141	+329%	0	0	—
case-05 We are configuring outbound payload mutation rules on our OmniRoute proxy. Some legacy documentation mentions a parameter named default-raw when setting payload rules. What endpoint should we HTTP PUT to, and what field name does OmniRoute normalize default-raw to in its response?	fail→pass	12,354	3,216	-74%	1	1	0%	1,902	10,898	+473%	0	0	—
case-06 I need to verify our OmniRoute proxy's active quota store backend settings via API to confirm our Redis connection details. What cURL command should I run, and how does OmniRoute treat sensitive Redis URLs in the returned JSON?	fail→pass	18,636	5,392	-71%	1	1	0%	1,982	11,107	+460%	0	0	—
case-07 Our security team requested that we clear the stored API key from our OmniRoute Qdrant vector database configuration. How can we remove the key using a cURL request against the Qdrant settings route?	fail→pass	15,487	10,466	-32%	1	1	0%	1,458	11,128	+663%	0	0	—
case-08 We need to check our OmniRoute extended memory configuration, which includes fields like embeddingSource and vectorStore. Which endpoint provides this information, and what HTTP method is used to modify these memory parameters?	fail→pass	19,453	29,446	+51%	1	1	0%	1,504	11,133	+640%	0	0	—
case-09 We want to monitor how many distinct egress IP addresses actually served our OmniRoute proxy pool members over the last 24 hours without changing any routing. What specific settings endpoint provides this 24-hour egress observation metrics?	fail→pass	25,778	9,623	-63%	1	1	0%	1,887	11,142	+490%	0	0	—
case-10 We need to block several malicious client IPs on our OmniRoute instance and inspect our active whitelist and blacklist. What endpoints allow us to view and update our IP filter rules?	fail→pass	38,164	5,255	-86%	1	1	0%	2,126	11,202	+427%	0	0	—
case-11 Database storage on our OmniRoute installation is bloated. What API endpoint and HTTP method should we call to trigger a database vacuum maintenance operation?	fail→pass	29,430	10,008	-66%	1	1	0%	1,319	10,980	+732%	0	0	—
case-12 We need to clean up expired memory points that have passed their retention window in our Qdrant vector collection connected to OmniRoute. Which endpoint handles this cleanup task?	fail→pass	12,680	4,013	-68%	1	1	0%	1,699	10,832	+538%	0	0	—
case-13 Our administrative dashboard needs to execute a purge of stored usage history records in OmniRoute. What request method and endpoint should be called?	fail→pass	10,917	10,741	-2%	1	1	0%	1,304	10,984	+742%	0	0	—
case-14 Before enabling a new reasoning routing rule in OmniRoute, we want to test its behavior against sample inputs without saving it. What endpoint allows us to simulate reasoning routing rules?	fail→pass	14,022	9,498	-32%	1	1	0%	1,374	11,021	+702%	0	0	—
case-15 We use OneProxy integration in OmniRoute and need to force an immediate proxy credentials/IP rotation call via cURL. What endpoint accepts this trigger?	fail→pass	46,862	9,149	-80%	1	1	0%	1,926	10,996	+471%	0	0	—
case-16 During local deployment testing of OmniRoute, we want to toggle the user login requirement via API. Which cURL call toggles the require-login setting?	fail→pass	14,515	9,246	-36%	1	1	0%	1,216	10,974	+802%	0	0	—
case-17 We need to inspect and update the system prompt injection settings across our OmniRoute proxy setup. What cURL commands handle reading and writing these system prompt settings?	fail→pass	21,277	12,240	-42%	1	1	0%	2,313	11,193	+384%	0	0	—
case-18 We are migrating configuration from a staging OmniRoute environment to production. What API routes allow us to export all settings as JSON and import them back into the target server?	fail→pass	34,411	12,731	-63%	1	1	0%	1,936	11,217	+479%	0	0	—
case-19 We want our monitoring script to trigger an immediate refresh of database statistics in OmniRoute. What cURL command should be issued?	fail→pass	9,583	8,903	-7%	1	1	0%	1,593	10,998	+590%	0	0	—
case-20 Our client application expects model listing formatted in Ollama /api/tags style from the OmniRoute server. What endpoint provides this Ollama-compatible list?	pass→pass	31,598	9,572	-70%	1	1	0%	1,353	10,897	+705%	0	0	—
case-21 I want to send a user prompt "Explain quantum computing in three sentences" to GPT-4o through our OmniRoute gateway using cURL. What endpoint and JSON payload format should I send for this inference request?	pass→pass	13,330	6,770	-49%	1	1	0%	1,190	11,475	+864%	0	0	—
case-22 Our script needs to obtain an initial Bearer authentication token from OmniRoute using administrative credentials before calling management endpoints. What HTTP method and route are used for logging in?	fail→pass	20,051	7,137	-64%	1	1	0%	1,246	10,858	+771%	0	0	—
case-23 We want to pull the latest llama3 model weights directly into our local Ollama backend instance running on the host machine using its native CLI or API, outside of OmniRoute settings. What native command or endpoint is used?	pass→pass	11,882	10,956	-8%	1	1	0%	1,137	11,141	+880%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +87 percentage points is the difference between those two pass rates over the 23 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 13%
Pass rate with the skill: 100%
Cases attempted: 23
Cases counted toward lift: 23
Cases that regressed: 0
Skill version measured: v5
Run completed: 9/23/2026, 08:19 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

I noticed my desktop AI client's reasoning trace is disappearing because the proxy appears to be clearing out thinking parameters before sending requests upstream. Could you provide the cURL commands to view my server's reasoning budget configuration and update it so client-specified thinking parameters remain intact?

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run100

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+811% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 3 days ago

Model	Method	Date	Lift
gemini-3.6-flash	verified	9/8/2026	+78%
gemini-3.6-flash	verified	8/24/2026	+86%
gemini-3.6-flash	verified	8/17/2026	+77%
gemini-3.6-flash	verified	8/7/2026	+74%

Other measured skills in the registry, with their headline benchmark lift.