Waxell
Waxell is an AI agent governance and observability platform that provides runtime policy enforcement, auto-instrumented LLM telemetry, MCP governance, cost management, and durable workflow execution for agents built in any Python framework or third-party agentic tool (Claude Code, Cursor, LangChain, CrewAI, OpenAI Agents SDK, and 200+ more).
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Waxell the way a machine reads it — 58 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Waxell scores 66.4/100 (strong), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Waxell
Each block below is one kind of artifact we hold for Waxell. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Waxell Developer MCP Server
Waxell Developer MCP is a hosted Model Context Protocol server that lets coding agents (Claude Code, Cursor, Windsurf, VS Code, Claude Desktop) query a Waxell instance in real t...
Waxell Cost Management API
Model cost catalog and tenant-level overrides
Waxell Governance API
Pre-execution policy checks and audit events
Waxell Prompts API
Managed prompts retrievable by name and version
Waxell Runs API
Lifecycle endpoints for agent execution runs
Waxell Telemetry API
LLM calls, spans, steps, and quality scores recorded against a run
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Waxell Observe API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Waxell Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Waxell Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Waxell Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Auto-Instrumentation
Two-line setup auto-instruments 200+ libraries (OpenAI, Anthropic, LangChain, LlamaIndex, CrewAI, LiteLLM, etc.) without code changes.
Runtime Policy Enforcement
26 policy categories (cost, kill switch, PII, compliance, scope, safety) returning seven decisions (allow, warn, redact, throttle, block, skip, retry).
MCP Governance
Auto-instrumentor, server middleware, and governance proxy for Model Context Protocol traffic with PII scanning and rug-pull detection.
Cost Management
Built-in model pricing for 20+ models, tenant overrides via REST, budget enforcement that warns/throttles/blocks at thresholds.
Prompt Management
Versioned managed prompts retrievable by name and label (e.g. production, staging) directly from the SDK.
Workflow Envelope
Durable execution boundary with checkpoint and resume; Redis-backed in production, in-memory for development.
Human-in-the-Loop Approvals
Custom handlers route policy blocks to Slack, webhooks, or terminal prompts for human review.
Audit Trail
Immutable, timestamped record of all agent actions, decisions, and governance events.
Developer MCP
Hosted SSE MCP server (dev-mcp.waxell.dev/sse) with 15 live tools and 8 docs resources for coding agents.
Field-Level Encryption
PII fields encrypted at the application layer with AES-256-GCM and AWS KMS (FIPS 140-2 Level 3) before database storage.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Waxell Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Waxell API Rules
SPECTRALWaxell API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Waxell LLM Call
JSON SCHEMAWaxell Policy Decision
JSON SCHEMAWaxell Run
JSON SCHEMAWaxell Span
JSON SCHEMAJSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Waxell Policy Decision Structure
JSON STRUCTUREWaxell Run Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Govern Third-Party Coding Agents
Enforce policies on Claude Code, Cursor, Windsurf, VS Code, and Claude Desktop without modifying their code.
Instrument Self-Built Agents
Add full observability to LangChain, CrewAI, OpenAI Agents SDK, or custom Python agents with the @waxell.observe decorator.
Cost-Capped Agent Deployment
Set budgets on token spend per agent, user, or tenant; block runs that exceed configured limits.
PII-Safe MCP Tool Use
Scan MCP tool inputs/outputs for PII, credentials, and secrets with warn/block/redact responses.
Durable Long-Running Workflows
Use the WorkflowEnvelope to checkpoint multi-step agent workflows so they can resume after interruption.
Compliance-Ready AI Operations
Maintain SOC 2 Ready posture with immutable audit trails, encrypted PII, and EU data residency.
Integrations 13
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
OpenAI
Auto-instrumented LLM provider; cost and token tracking out of the box.
Anthropic
Auto-instrumented LLM provider; supports Claude family models.
LangChain / LangGraph
First-class callback handler (WaxellLangChainHandler) for tracing chains and graphs.
CrewAI
Auto-instrumented multi-agent framework support.
LlamaIndex
Tracing for RAG pipelines built with LlamaIndex.
LiteLLM
Unified telemetry across LiteLLM-routed providers.
Claude Code
Governance overlay for Anthropic's Claude Code coding agent via the Developer MCP.
Cursor / Windsurf / VS Code
Coding-agent governance via the SSE MCP server at dev-mcp.waxell.dev.
OpenAI Agents SDK
Auto-instrumentation for OpenAI's Agents SDK runs.
AWS Bedrock / Azure OpenAI / Google Vertex AI
Cloud LLM providers covered by Waxell's auto-instrumentation.
Pinecone / Weaviate / Qdrant / Milvus / Chroma
Vector database call tracing with retrieval span recording.
Slack / Webhooks
Human-in-the-loop approval handlers for policy blocks.
Stripe
Listed subprocessor for billing.
Scroll within the panel for all 13 ·
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Connect
Govern third-party agents (Claude Code, Cursor) without code changes via the MCP governance proxy.
Observe
Instrument self-built agents with auto-instrumentation, policy enforcement, and cost attribution.
Runtime
Governed execution environment for high-risk workflows with the durable WorkflowEnvelope.
Resources
Every other property we hold for Waxell — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/waxell · machine-readable index on apis.io