Vigil

Vigil offers a token‑optimisation and cost‑monitoring proxy for large‑language‑model APIs. It aggregates calls to frontier models, providing per‑call latency, error tracking, and token‑usage analytics, enabling developers to manage expenses and performance across multiple providers.

Vigil publishes 2 API contracts indexed on the APIs.io network: Proxy and Feedback API. Tagged areas include Monitoring, AI Middleware, Security, and Analytics.

Vigil’s developer surface includes authentication, pricing, engineering blog, documentation, changelog, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.9/100 developing ▬ flat Agent 28/100 agent aware Full breakdown ↓
scored 2026-10-23 · rubric v0.25.0 · Show this score on your site →

1 published contract

MonitoringAI MiddlewareSecurity Analytics

Kin Score

Kin Score How this is scored →
scored 2026-10-23 · rubric v0.25.0

Composite quality — 39.9/100 · developing

Contract Quality 8.3 / 19

Developer Ergonomics 3.6 / 15

Access Clarity 9.9 / 15

Operational Transparency 2.6 / 10

Contract Governance 0.0 / 9

Discoverability 5.6 / 8

Regulatory Posture 2.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 28/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/vigil-wtf/"><img src="https://apis.io/badge/vigil-wtf/card.svg" alt="Vigil on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/vigil-wtf: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Vigil Proxy

A pass-through proxy for AI provider APIs. Requests to https://api.vigil.wtf/{user_id}/{provider}/{path} are forwarded to the named provider and the provider's response is retur...

Vigil Feedback API

Send a score from 1 to 5 for one of your proxied calls, keyed by Vigil's request id (POST /v1/feedback); a later score for the same request replaces the earlier one.

Pricing Plans 1

Published pricing tiers and plan structures.

Vigil Wtf Plans Pricing

1 plans

PLANS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Vigil Wtf Authentication

2 schemes

SECURITY

Vigil Wtf Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

SecurityTxt

SecurityTxt

Operate 1

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Plans

TermsOfService

PrivacyPolicy

Pricing

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: vigil-wtf
name: Vigil
image: https://www.vigil.wtf/opengraph-image
description: Vigil offers a token‑optimisation and cost‑monitoring proxy for large‑language‑model APIs. It aggregates calls
  to frontier models, providing per‑call latency, error tracking, and token‑usage analytics, enabling developers to manage
  expenses and performance across multiple providers.
url: https://raw.githubusercontent.com/api-evangelist/vigil-wtf/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-02 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-02'
modified: '2026-10-05'
tags:
- Monitoring
- AI Middleware
- Security
- Analytics
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/vigil-wtf-plans-pricing.yml
- type: Authentication
  url: authentication/vigil-wtf-authentication.yml
- type: Hosts
  url: hosts/vigil-wtf-hosts.yml
- type: Vendors
  url: vendors/vigil-wtf-vendors.yml
- type: TermsOfService
  url: https://www.vigil.wtf/terms
- type: PrivacyPolicy
  url: https://www.vigil.wtf/privacy
- type: Pricing
  url: https://www.vigil.wtf/pricing
- type: Login
  url: https://www.vigil.wtf/auth/login
- type: Blog
  url: https://www.vigil.wtf/blog
- type: DomainSecurity
  url: security/vigil-wtf-domain-security.yml
- type: Website
  url: https://www.vigil.wtf
- type: Documentation
  url: https://www.vigil.wtf/docs
- type: LLMsTxt
  url: https://www.vigil.wtf/llms.txt
- type: ChangeLog
  url: https://www.vigil.wtf/changelog
- type: SecurityTxt
  url: https://www.vigil.wtf/.well-known/security.txt
apis:
- aid: vigil-wtf:vigil-wtf-vigil-proxy-api
  name: Vigil Proxy
  description: A pass-through proxy for AI provider APIs. Requests to https://api.vigil.wtf/{user_id}/{provider}/{path} are
    forwarded to the named provider and the provider's response is returned, with Vigil's request id and optimisation headers
    added. The provider's OpenAPI covers Vigil's own surface only (the route, its path parameters and headers, and Vigil's
    error format); request and response bodies are the upstream provider's own.
  humanURL: https://www.vigil.wtf/docs
  baseURL: https://api.vigil.wtf
  tags:
  - AI Middleware
  - Monitoring
  properties:
  - type: OpenAPI
    url: openapi/vigil-wtf-vigil-proxy-api-openapi.yml
  - type: OpenAPI
    name: OpenAPI (provider-hosted)
    url: https://www.vigil.wtf/openapi.json
  - type: Documentation
    url: https://www.vigil.wtf/docs
  - type: ErrorCatalog
    url: https://www.vigil.wtf/docs#errors
- aid: vigil-wtf:vigil-wtf-feedback-api
  name: Vigil Feedback API
  description: Send a score from 1 to 5 for one of your proxied calls, keyed by Vigil's request id (POST /v1/feedback); a
    later score for the same request replaces the earlier one.
  humanURL: https://www.vigil.wtf/docs#feedback
  baseURL: https://api.vigil.wtf
  tags:
  - Feedback
  properties:
  - type: OpenAPI
    url: openapi/vigil-wtf-feedback-api-openapi.yml
  - type: OpenAPI
    name: OpenAPI (provider-hosted)
    url: https://www.vigil.wtf/openapi.json
  - type: Documentation
    url: https://www.vigil.wtf/docs#feedback
x-submission-notes: 'AI-call monitoring and token-optimisation proxy for LLM providers. | Listed on Kin''s call 2026-10-02
  despite: LLM observability proxy (api.vigil.wtf/ID/anthropic) with no developer docs, OpenAPI or llms.txt; product is a
  pass-through base URL plus dashboard.'
x-submission-probe: root 200; /docs 404; /llms.txt 404; /openapi.json 404; docs.vigil.wtf no DNS; 404 probe 404
x-submitted-by: sam@vigil.wtf (apis.io/add, 2026-09-30)
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: API root returns 400 errors and no OpenAPI or docs are available.
  evidence:
  - url: https://api.vigil.wtf
    status: 400
  checked: '2026-10-02'
x-enrichment:
  date: '2026-10-02'
  status: enriched
  artifacts_added: 8
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local
x-correction-request:
  requested: '2026-10-05'
  source:
  - https://github.com/api-evangelist/vigil-wtf/pull/1
  request: Add Vigil's developer docs (https://www.vigil.wtf/docs), OpenAPI (https://www.vigil.wtf/openapi.json), llms.txt,
    changelog and security.txt, list the proxy as an API, and re-score.
  ledger:
  - vigil-wtf-4828f334
  applied: '2026-10-05'
  applied_note: Applied by hand; all five URLs verified 200 on 2026-10-05 with a 404 soft-404 control. The provider OpenAPI
    (3.1.0, version 2026-10-05, 2 paths / 3 operations, now including POST /v1/feedback which the PR did not mention) saved
    verbatim to openapi/_original/vigil-wtf-openapi.json and split/standardized into the Vigil Proxy and Vigil Feedback API.
    Documentation, LLMsTxt, ChangeLog and SecurityTxt pointers added to common. The PR was not merged.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/vigil-wtf"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/vigil-wtf/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/vigil-wtf/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.