Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.verifiedx.me/llms.txt

Use this file to discover all available pages before exploring further.

Most builders initialize VerifiedX once, then use the returned runtime object with the raw runtime or a native adapter.

​
Basic usage

from verifiedx import init_verifiedx

vx = init_verifiedx()

​
What you do next

After initialization, use the returned runtime object with the integration surface you chose. 
vx.install_runtime(node, ...)
If you are using a native adapter such as OpenAI, Anthropic, Claude Agent SDK, LangGraph, Vercel AI SDK, or MCP, initialize VerifiedX once and then pass it into that adapter.

​
Required configuration

For normal SDK usage, VERIFIEDX_API_KEY is the only required environment variable.
.env
VERIFIEDX_API_KEY=your_runtime_key
Both SDKs read VERIFIEDX_API_KEY automatically. Most builders do not need any additional initialization config.

​
Python

Use init_verifiedx() when you are working in Python.
  • Returns a VerifiedX runtime object
  • Synchronous
  • Usually followed by install_runtime(...) or a native Python adapter
from verifiedx import init_verifiedx

vx = init_verifiedx()

​
TypeScript

Use initVerifiedX() when you are working in TypeScript.
  • Returns a Promise resolving to a VerifiedX runtime object
  • Async
  • Usually followed by bindHarness(...) or a native TypeScript adapter
import { initVerifiedX } from "@verifiedx-core/sdk";

const vx = await initVerifiedX();
initVerifiedX() is async. Always await it before using the returned runtime object.

​
Advanced usage

Both SDKs also support advanced initialization in code for custom transports and specialized setups, but most builders should ignore that and use the default environment-variable path. The normal public integration pattern is:
  1. Set VERIFIEDX_API_KEY
  2. Initialize VerifiedX once
  3. Bind the raw runtime or attach the native adapter