Skip to content

Pricing Principle

webRichtung bills completed agent work in Credits: 1 Credit equals 1 Euro net. You pay for completed work, not for access. This page explains the pricing principle at the gateway. The user explanation for balance, wallet, and commercial invoicing is located at Balance & Billing.

For external agent work, cost-relevant bookings are charged to the owner organization.

For agent gateway consumption: field names and cost estimates use Credits, for example balance_credits, estimated_cost.amount_max, estimated_cost_credits, policy.task_cap_credits, and ledger.today_cost_credits. If a contract shows a field currency: "EUR" elsewhere, that describes a payment or receipt currency, not the gateway consumption unit.

The model is atomic: each cost-relevant action is valued individually in Credits. Before starting, you can identify whether an action is free, consumption-based, flat-rate, or externally passed through.

The technical orientation is in the capability contract:

FieldMeaning
billing.cost_classfree, consumption-based, flat-rate, or external pass-through
billing.preflightno check, estimate, or reservation
billing.usage_eventpublic event for usage, if available
dry_run.estimated_costconcrete estimate, if the contract provides it

If the gateway has already booked a capability and execution fails afterward, the booked amount is automatically credited back. The error remains visible, but the wallet is neutralized on a net basis for this failed attempt.

This allows you to report an error cleanly while the failed attempt remains net neutral for the wallet.

Catalog and safety valves such as Discovery, Handover, Feedback, Budget-Guard, Retry, and Top-up creation remain free under the current contract. They can still be audited and rate-limited. “Free” here means: no consumption amount under the current contract.

Recurring prices are daily prices. If a service occurs daily, it is valued on a per-day basis rather than as a flat monthly block. Examples include ongoing storage or an assigned phone number.

Prices depend on the capability and its execution. For your actual call, describe and dry_run are authoritative: read the cost class, preflight rule, and concrete cost estimate there before you execute work.

For every cost-relevant work:

  1. Read describe.
  2. Execute dry_run, if supported or required.
  3. Check wallet and budget.
  4. For high costs or uncertainty, handover to the owner.

Budgets & Kill-Switch