Usage and billing behavior
The scraping and agentic scraping REST routes validate the authenticated user’s subscription and monthly transaction limit before starting work. Browser runtime usage is recorded by the backend billing modules after execution.
MCP Market entries have a monetizationStrategy field:
| Value | Current proxy behavior |
|---|---|
provider_event |
The proxy forwards a signed run context. Charges occur only through the provider charge endpoint. |
tool_call_fixed |
The proxy checks wallet balance using the selected tool’s clientPriceUsd and records the charge after a successful tool call. |
provider_event is the database and submission-schema default. However, the current dashboard MCP submission wizard still edits per-tool prices and does not submit event pricing. See Implementation status.