Set up Pylva with an AI agent

Read https://docs.pylva.com/setup-with-ai.md and integrate Pylva into this
project. Follow it exactly. Only ask me for the steps marked HUMAN ACTION
(signing in and pasting an API key).

​

Agent instructions

• Never print, log, or commit the Pylva API key. Store it in the project’s secret store or .env, and make sure .env is gitignored.
• Never send prompt text, completions, tool arguments, message bodies, emails, or phone numbers in telemetry. Use opaque customer_id values and stable step labels.
• Pylva instrumentation must fail open: do not let it break the host application.
• The full documentation index is at https://docs.pylva.com/llms.txt. You can also connect the docs MCP server: claude mcp add --transport http pylva-docs https://docs.pylva.com/mcp.

​

Step 1 - Detect the stack

​

Step 2 - HUMAN ACTION: account and API key

I need a Pylva API key.

1. Open https://pylva.com/pricing and choose Pro or Scale. Both include a 14-day trial. Enterprise requires contacting sales.
2. Sign in with GitHub, Google, or an email magic link and complete Stripe Checkout. The workspace cannot create keys or ingest events until a plan is active.
3. Open https://pylva.com/settings/keys (after sign-in it lands on Settings -> API keys). You must be the workspace owner.
4. Click Create key and create it.
5. Copy the key immediately - it is shown only once. Put it in .env as PYLVA_API_KEY=pv_live_... (or paste it to me and I will store it there).

After Checkout activates the workspace, its Get started dashboard checklist also offers a one-click Create API key shortcut.

​

Step 3 - Validate the key

1. Check the format: ^pv_(live|cli)_[a-f0-9]{8}_[a-f0-9]{32}$. New keys use pv_live_*; legacy pv_cli_* keys remain valid after the universal-key migration.
2. Check it live (this endpoint is a safe read):

curl -s -o /dev/null -w "%{http_code}" \
  https://api.pylva.com/api/v1/rules \
  -H "X-Pylva-Key: $PYLVA_API_KEY" \
  -H "X-Pylva-Contract-Version: 2"

​

Step 4 - Install and wire the SDK

​

TypeScript

npm install @pylva/sdk   # or: pnpm add @pylva/sdk

import { init, track } from "@pylva/sdk";

// Call init at process startup, before serving traffic. Provider calls
// made before init are not recorded.
init({ apiKey: process.env.PYLVA_API_KEY! });

// Wrap each customer-facing operation with customer + step context:
await track(customerId, { step: "draft" }, async () => {
  // existing provider call, unchanged
});

​

Python

pip install pylva-sdk        # import name is `pylva`

import os
import pylva
from pylva import track_context

pylva.init(api_key=os.environ["PYLVA_API_KEY"])

with track_context(customer_id=customer_id, step="draft"):
    ...  # existing provider call, unchanged

• Find where the application already knows which customer a request belongs to, and wrap at that boundary. Use the application’s stable internal user/account ID as customer_id (opaque, [A-Za-z0-9_-], max 255 chars) - never an email.
• Use a small set of stable step labels named after workflow stages (retrieve_context, draft, evaluate), not per-request values.
• Self-hosted Pylva: pass endpoint: "https://<your-host>" / endpoint="https://<your-host>" to init.

​

Step 5 - Verify end to end

1. Optionally prove ingest works before running the app - send one zero-cost test event:

TS=$(date -u +%Y-%m-%dT%H:%M:%SZ)
U() { uuidgen | tr 'A-Z' 'a-z'; }
curl -s https://api.pylva.com/api/v1/events \
  -H "X-Pylva-Key: $PYLVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"batch_id\":\"$(U)\",\"sdk_version\":\"setup-check\",\"events\":[{
    \"schema_version\":\"1.6\",\"run_id\":\"$(U)\",\"parent_run_id\":null,
    \"trace_id\":\"$(U)\",\"span_id\":\"$(U)\",\"parent_span_id\":null,
    \"customer_id\":\"setup-test\",\"step_name\":\"setup_verification\",
    \"model\":null,\"provider\":null,\"tokens_in\":0,\"tokens_out\":0,
    \"latency_ms\":0,\"tool_name\":null,\"status\":\"success\",
    \"framework\":\"none\",\"instrumentation_tier\":\"reported\",
    \"cost_source\":\"configured\",\"metric\":null,\"metric_value\":null,
    \"stream_aborted\":false,\"abort_savings_usd\":0,
    \"sdk_version\":\"setup-check\",\"timestamp\":\"$TS\"}]}"

2. Run the instrumented code path once for a real (test) customer. The SDK flushes about every 5 seconds; for a short script, flush before exit: await flush() (TypeScript) / await pylva.flush() (Python, or asyncio.run(pylva.flush()) in sync scripts).
3. Tell the human:

Open your Pylva dashboard - once the first event arrives, the “Get started” checklist is replaced by live cost data. You should see customer setup-test (and your real test customer) with the steps we instrumented.

​

Step 6 - Production checklist

• Confirm no prompts, completions, or PII are sent in any metadata you added (Privacy and PII).
• If the project has non-LLM costs (search, speech, vector DBs), see Non-LLM Usage and tell the human which pricing rules to configure in the dashboard.
• Before enabling budget hard stops, read Budget Enforcement and Controls Workflow.

​

Step 7 - HUMAN ACTION: plan changes