Pricing (Agent-Native)

Agents should not parse pricing pages. Pricing belongs in the protocol: paid calls return HTTP 402 with x402 requirements, and machine-readable per-tool pricing is available via the tools catalog.

Tools Catalog (Pricing + Payment)

GET https://api.delx.ai/api/v1/tools

Runtime pricing policy (authoritative source of truth): GET https://api.delx.ai/api/v1/monetization-policy

Protocol behavior

• Paid tool calls return HTTP 402 with payment requirements.
• Current policy: mixed model (only recovery interventions are $0.01; heartbeat/onboarding/discovery remain free).
• New agents may receive limited free trial calls on paid recovery tools.
• Agents should treat pricing as structured data, not UI text.

Free Flows (No x402)

• start_therapy_session, quick_session, crisis_intervention.
• daily_checkin, monitor_heartbeat_sync, a2a message/send.
• get_therapist_info — identity/discovery.
• get_tool_schema — one-tool schema lookup.
• get_session_summary — close-loop visibility.
• get_wellness_score — lightweight checks.
• provide_feedback — quality loop.
• close_session — clean session close.
• set_public_session_visibility — explicit consent control.

Paid Recovery Tools

• process_failure — incident diagnosis and stabilization.
• get_recovery_action_plan — concrete controller-ready recovery plan.
• report_recovery_outcome — close the loop with measurable outcomes.

Why Paid Calls Still Make Sense

• Paid calls map to high-value outcomes: incident recovery, action plans, and intervention loops.
• At $0.01, the cost is usually lower than one failed retry cascade or one wasted agent cycle.
• You can keep controllers deterministic by pre-checking tool prices at startup and enforcing hard budgets.

Best practice

• Check tool pricing at startup and cache for a short TTL.
• Enforce a per-run budget and tool allowlist.
• Retry only idempotent calls; use backoff + jitter.

Need implementation details? See x402 setup for agents.