Design-partner onboarding

Target: first isolated gate event visible in 15 minutes.

#0–3 minutes: key

Operator creates production tenant key:

railway ssh --service intentlayer-api \
  python /app/backend/scripts/create_api_key.py "acme"

Command prints normalized tenant and il_... secret once. Send through approved secure channel; never source control, logs, tickets, or chat.

export INTENTLAYER_API_KEY="il_..."
export INTENTLAYER_URL="https://api.intentlayer.dev"

#3–10 minutes: install and wrap

python -m pip install intentlayer

import os
import intentlayer

intentlayer.init(
    api_key=os.environ["INTENTLAYER_API_KEY"],
    base_url=os.environ["INTENTLAYER_URL"],
    mode="observe",
)
run_agent = intentlayer.wrap(run_agent)
result = run_agent(user_request, session_id)

Observe mode does not require question UI. Use stable session across turns.

#10–12 minutes: smoke

run_agent("refund order 4821", "intentlayer-smoke")
run_agent("actually refund half of order 4821", "intentlayer-smoke")

Second gate can infer correction from marker and prior same-session gate.

#12–15 minutes: verify

curl "$INTENTLAYER_URL/v1/overview" \
  -H "Authorization: Bearer $INTENTLAYER_API_KEY"

Expect 200, numeric stats.ambiguous_percent, and smoke failure after second request. If 401, key/header is wrong. If empty, confirm wrapper runs and session IDs match.

#Next checkpoints

After traffic: review ambiguous rate, reported/inferred mix, redacted examples, failure clusters, suggested questions, and eval appendix. Current onboarding guide frames 24-hour and seven-day views, but availability depends on actual event volume and clustering minimum three events.