Skip to main content
VerifiedX is designed to be used through the Python and TypeScript SDKs. Most builders should use an SDK or native adapter. The direct HTTP API is available for advanced custom integrations, but the SDKs are the standard path.

​
Base URL

VerifiedX requests go to: 
https://api.verifiedx.me

​
Authentication

For direct HTTP requests, pass your API key in the Authorization header: 
Authorization: Bearer your_runtime_key
If you are using an SDK, set VERIFIEDX_API_KEY and the SDK will read it automatically.

​
Integration surfaces

VerifiedX supports three public integration surfaces:
  • Python SDK
    • pip install verifiedx
  • TypeScript SDK
    • npm install @verifiedx-core/sdk
  • Direct HTTP API
    • for advanced custom integrations
The SDKs are the recommended path. They handle runtime context capture, protected-boundary checks, receipts, and execution reporting for you.

​
Versioning

VerifiedX versions its API at the HTTP layer. If you use an SDK, you normally do not need to think about this directly. Use the SDK or native adapter that matches your stack:
  • Python SDK
  • TypeScript SDK
  • OpenAI direct
  • OpenAI Agents SDK
  • Anthropic direct
  • Claude Agent SDK
  • LangGraph
  • LangChain
  • Vercel AI SDK
  • MCP

​
Reference

Python SDK

Use the raw runtime or a native Python adapter.

TypeScript SDK

Use bindHarness(...), native adapters, or lower-seam fallbacks.

Environment Variables

Configure VerifiedX with the minimal required settings.

Decision Receipts

Understand the structured receipt returned by protected checks.