Vedika developer docs

Start with Getting started for the current harness chat contract. Build on the Vedika agent platform: an SDK for typed agent turns, a drop-in chat widget for any website, embeds for WordPress, Shopify and Wix, a remote MCP server, and two wire-compatible doors (one matching the Chat Completions shape, one matching the Messages shape) onto the same Vedika query pipeline.

Choose a surface

JavaScript SDK

@vedika-io/agent-sdk-js. Streams turns over the UI Message Stream v1 wire. Typed errors and idempotent retries.

Python SDK

vedika-agent-sdk (pip install vedika-agent-sdk). Async client with the same wire, the same chunk allowlist, and a swappable transport.

Chat widget

The harness module loader, a user-owned thread, and an authenticated backend ticket envelope.

WordPress embed

Custom HTML setup and a launcher for your authenticated HTTPS chat host page.

Shopify embed

Liquid setup and a launcher for your authenticated HTTPS chat host page.

Wix embed

Embed a Site setup and a launcher for your authenticated HTTPS chat host page.

Webflow embed

Code Embed setup and a launcher for your authenticated HTTPS chat host page.

Squarespace embed

Code Block setup and a launcher for your authenticated HTTPS chat host page.

Framer embed

Embed component setup and a launcher for your authenticated HTTPS chat host page.

MCP server

Remote MCP server with a consolidated tool catalog. Bearer or OAuth, audience-bound to the MCP path.

Compatible endpoints

Wire-compatible chat completions and messages endpoints. Both are stateless adapters over the same pipeline.

Apps skill pack

Instructions for coding agents building apps on the Vedika API: calculated charts, panchang, matching, reports and embeds.

End-user experience

What your end users actually see and do: answer sources, receipts line, support tickets, family members, memory consent, the crisis-helpline card, kundli charts, the embed mint body.

The wire in one paragraph

Every SDK and embed talks to a harness server over a small wire. The server holds threads (POST /api/v1/agent/threads), streams turns as text/event-stream with the x-vercel-ai-ui-message-stream: v1 header, resumes from a Last-Event-ID cursor, and cancels on POST /turns/{id}/cancel. The browser never sees a long-lived key; embedded chat uses a backend mint and a single-use ticket.

Public surface only

What lives here

The public SDK API, the public wire contract, the widget, the embed bundles, the MCP tool catalog, and the two compatible doors. Only public model ids are listed.

No provider names, no upstream model ids, no internal route names, no hosted-service routes, no prompts, and no live secrets appear anywhere in these pages.

Where to start

Open Quickstart for the authenticated backend and module-loader example.
Skim Models for the public id list.
Read Wire contract for the endpoints and headers you must send.
If you are building a website, jump to Widget or one of the embeds.
If you are wiring an IDE agent, read MCP.
If you build with a coding agent, load the Apps skill pack (download .zip).
For a customer integration, start with Getting started — the full enterprise onboarding pack.

Enterprise onboarding

The onboarding pack walks an enterprise customer from a signed contract to a first answer inside their own app. It assumes the customer already has their own auth (Firebase, Auth0, Cognito, Supabase, custom JWT, sessions) and their own onboarding data (name, birth date / time / place, language).